Education-Cloud-Consultant Exam Questions & Answers

The student number is the external ID that the consultant should recommend to match spreadsheet information with the Salesforce Contact record. The external ID is a field that uniquely identifies a record and can be used to match records from different data sources. The student number is a unique identifier for each student that can be used to match the spreadsheet information with the Contact record in Salesforce. The email address, company name, and company phone are not unique identifiers for each student and cannot be used as external IDs. Reference:

https://help.salesforce.com/s/articleView?id=sf.data_loader_match_record.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.customize_externalid.htm&type=5

The consultant should discuss with the Recruitment office that EDA requires custom automation for lead conversion as a compatibility consideration for using Pardot and Salesforce with EDA. Lead conversion is a process that converts a Lead record into an Account, a Contact, and an Opportunity record in Salesforce. EDA does not support the standard lead conversion process in Salesforce, because it uses different account models and objects to store information about individuals and organizations. The consultant should create custom automation for lead conversion, such as using Process Builder, Flow, or Apex, to map the Lead fields to the appropriate EDA fields and objects. Pardot being incompatible with the Household account model, the Do Not Contact TDTM record needing to be disabled, or Pardot being able to create only Leads and Contacts are not compatibility considerations for using Pardot and Salesforce with EDA. Reference:

https://powerofus.force.com/s/article/EDA-Lead-Conversion

https://trailhead.salesforce.com/en/content/learn/modules/pardot-basics

Education History is an EDA functionality that the consultant can recommend to track school historical data for tagged outreach and donation opportunities. Education History is a feature that allows the consultant to store information about a Contact's previous or current education at an educational institution. Education History can be used to track various types of information, such as school name, degree, major, minor, class year, or sports team. The consultant can use Education History to segment and target alumni based on their school historical data. Program Plan, Attribute, and Relationship are not EDA functionalities that can track school historical data for tagged outreach and donation opportunities. Reference:

https://powerofus.force.com/s/article/EDA-Education-History

https://powerofus.force.com/s/article/EDA-Education-History-Create

The consultant should explain that one of the reasons why key stakeholders might participate in a Center of Excellence is that it standardizes the data definitions for the university. A Center of Excellence is a group of people who provide leadership, guidance, and best practices for a specific area or domain. A Center of Excellence can help standardize the data definitions for the university by creating and maintaining a common vocabulary and understanding of what data means, how it is used, or how it is measured across different departments or units. Standardizing the data definitions can help improve data quality, consistency, and accuracy for the university. It ensures data is owned by one group or it ensures feature requests will be implemented are not reasons why key stakeholders might participate in a Center of Excellence for the university. Reference:

https://www.salesforce.org/wp-content/uploads/2019/03/Education_Cloud_COE_Guide.pdf

https://trailhead.salesforce.com/en/content/learn/modules/org-change-management

The consultant should discuss with the university that EDA picklist values for reciprocal Relationships need to be translated manually as a consideration about translating EDA into Spanish when using EDA. Translating EDA into Spanish means changing the language of EDA objects, fields, labels, or values into Spanish. EDA picklist values for reciprocal Relationships need to be translated manually as a consideration about translating EDA into Spanish when using EDA because these picklist values are not automatically translated by Salesforce's Translation Workbench tool and require manual intervention. The consultant should discuss with the university that EDA picklist values for reciprocal Relationships need to be translated manually as a consideration about translating EDA into Spanish when using EDA by explaining how to use custom labels or formula fields to translate these picklist values into Spanish. EDA picklist values are restricted to the organization's default language or Spanish is a platform-only language in EDA are not considerations about translating EDA into Spanish when using EDA. Reference:

https://powerofus.force.com/s/article/EDA-Relationships

https://powerofus.force.com/s/article/EDA-Translate-Picklists