Pass Education-Cloud-Consultant Exam Guide

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. References:

• https://powerofus.force.com/s/article/EDA-Lead-Conversion
• https://trailhead.salesforce.com/en/content/learn/modules/pardot-basics

The consultant should outline data element as an integration consideration when building a Salesforce integration strategy for the IT department at a university. Data element is an integration consideration that refers to the type, format, quality, or volume of data that will be exchanged between systems. The consultant should outline data element as an integration consideration when building a Salesforce integration strategy for the IT department at a university by identifying what data needs to be integrated, how it will be transformed or mapped, how it will be validated or cleansed, or how it will be stored or archived. Salesforce license type, sandbox environment, or security model are not integration considerations that the consultant should outline when building a Salesforce integration strategy for the IT department at a university. References:

• https://trailhead.salesforce.com/en/content/learn/modules/api_basics/api_basics_data
• https://www.salesforce.org/wp-content/uploads/2019/03/Education_Cloud_COE_Guide.pdf

A third-party app is a solution that the consultant can recommend to meet the requirement of electronically sending, and also printing and mailing scholarship and program admission decisions on a preformatted letter template. A third-party app is an application that provides additional features and solutions for Salesforce. There are many third-party apps on the AppExchange that offer document generation and delivery capabilities, such as creating letters, invoices, contracts, or proposals, and sending them via email or postal mail. The consultant can help the International Studies office choose an app that meets their needs and budget. Salesforce reports, Salesforce Files, and Extended Mail Merge are not solutions that can electronically send, and also print and mail scholarship and program admission decisions on a preformatted letter template. References:

• https://appexchange.salesforce.com/appxStore?type=App&keyword=document%20generation
• https://trailhead.salesforce.com/en/content/learn/modules/appexchange_basics

Affiliation Mappings are used to automatically create and populate the Primary Affiliation field on the Contact record based on the Account record type of the related Affiliation. For example, if a Contact has an Affiliation with an Account of record type “Academic Program”, the Primary Affiliation field on the Contact record will be populated with that Account name. The consultant can go to Affiliation Mappings in EDA Settings to configure which Account record types should trigger this behavior and which fields should be used to store the Primary Affiliation. References:

• Education Data Architecture Basics - Unit 3: Affiliations and Relationships
• EDA Documentation - Affiliation Mappings