Free Salesforce Education Cloud Consultant Exam Dumps

The consultant should recommend to develop a performance testing strategy, identify areas that may impact governor limits, and log a case with Salesforce Support to increase limits as three steps to prepare for the large increase in users accessing the system at any one time. Developing a performance testing strategy means creating and executing tests that measure how the system performs under different scenarios and conditions, such as load testing or stress testing. Developing a performance testing strategy can help evaluate the system's reliability, scalability, and responsiveness when faced with high user demand. Identifying areas that may impact governor limits means finding and analyzing the code or processes that may consume excessive system resources or exceed the predefined limits set by Salesforce, such as CPU time limit or SOQL query.

The consultant should disable unnecessary code using TDTM and disable sharing rules using TDTM as two temporary actions before importing the data into the university's Salesforce production environment that has EDA. TDTM stands for Table Driven Trigger Management, which is a feature that allows users to customize the behavior of EDA triggers and disable or enable them as needed. Disabling unnecessary code using TDTM can help prevent unwanted automation and validation from running and affecting the data import. Disabling sharing rules using TDTM can help prevent sharing recalculation and improve performance. Changing the sharing model to Public Read/Write or changing the account model to Household are not temporary actions that the consultant should take before importing the data into the university's Salesforce production environment that has EDA. Reference:

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

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

The consultant should discuss with the institution how they can use EDA record types for student contacts and lead management, and how a support ticket is required to disable Person Accounts, as two considerations for installing EDA in their existing Salesforce environment that has Person Accounts enabled. EDA record types are predefined record types that are available for the Contact and Lead objects in EDA. EDA record types can be used to categorize and manage different types of contacts and leads, such as students, faculty, staff, alumni, or applicants. The institution can use EDA record types for student contacts and lead management instead of using Person Accounts. A support ticket is a request that users can submit to Salesforce Support to get assistance or guidance on various issues or tasks. A support ticket is required to disable Person Accounts, because this is a permanent and irreversible action that can affect data and functionality. The institution should submit a support ticket to disable Person Accounts before installing EDA, because Person Accounts are unsupported in EDA. Person Accounts being unsupported in EDA, or Person Accounts being able to only merge with Administrative Accounts, are not considerations for installing EDA in their existing Salesforce environment that has Person Accounts enabled. Reference:

https://powerofus.force.com/s/article/EDA-Record-Types

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

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

The consultant should recommend to populate the employer Affiliation record in the Primary Business Organization field, and select Organization as the Default Account Model in EDA Settings instead of mapping prospects and students' employers to the standard Account field in Salesforce. Affiliation is an object that represents a relationship between a Contact and an Account or another Contact. Affiliation can be used to track various types of relationships, such as student, faculty, staff, alumni, donor, or employer. The Primary Business Organization field on the Contact object indicates which Affiliation record is marked as primary for a Contact's business organization. The consultant should use Affiliation to track prospects and students' employers instead of using the standard Account field in Salesforce. Organization is an account model that allows users to store information about organizations that are not educational institutions, such as businesses or nonprofits. Organization can be used to track various information about an organization, such as name, industry, revenue, or employees. The consultant should select Organization as the Default Account Model in EDA Settings instead of using Standard Account or other account models in EDA. Reference:

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

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

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

User contest and post go-live recap are two communication examples that the consultant can recommend to send after implementation. User contest is a type of communication that encourages users to participate in a competition or a challenge related to using Salesforce, such as completing a certain number of tasks, earning badges on Trailhead, or submitting feedback or ideas. User contest can help increase user engagement, adoption, and satisfaction with Salesforce. Post go-live recap is a type of communication that summarizes the results and outcomes of the implementation project, such as key achievements, lessons learned, success stories, or next steps. Post go-live recap can help celebrate the project completion, acknowledge the project team and stakeholders, and provide guidance for future improvements. Teaser email and project sponsor profile are two communication examples that the consultant can recommend to send before implementation. Reference:

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

https://trailhead.salesforce.com/en/content/learn/modules/change_management/change_management_communicate

The consultant should recommend the Advancement office to define organizational objectives and prioritize the organization's initiatives as two steps to build a CRM strategy. Defining organizational objectives means identifying the goals and outcomes that the Advancement office wants to achieve with Salesforce, such as increasing donor retention, improving donor engagement, or streamlining fundraising processes. Prioritizing the organization's initiatives means ranking the projects and tasks that the Advancement office needs to complete to achieve their objectives, based on factors such as urgency, impact, feasibility, or alignment. Starting solution design during a discovery session or implementing Nonprofit Success Pack are not steps to build a CRM strategy. Reference:

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

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

The consultant should set Account and Contact's sharing to private before the data load, and disable all TDTM trigger Handlers before the data load, to load a large volume of alumni contact records into a new Salesforce environment. Setting Account and Contact's sharing to private before the data load can prevent sharing recalculation and improve performance. Disabling all TDTM trigger Handlers before the data load can prevent unwanted automation and validation from running and affecting the data load. Setting Account and Contact's sharing to public Read/Write before the data load, or loading record owners after the Account and Contact data load is complete, are not actions that the consultant should take. Reference:

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

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

The consultant should create an Affiliation mapping to the Primary Chapter field in EDA Settings, and create a custom picklist value for Alumni Chapter on the Affiliation object, to meet this requirement. An Affiliation mapping allows the consultant to specify which field on Contact should be populated with a value from an Affiliation record when that Affiliation is marked as primary. A custom picklist value for Alumni Chapter on the Affiliation object allows the consultant to indicate which type of Affiliation is related to an alumni chapter membership. Creating an Affiliation record type for Alumni Chapter and a custom field for Primary Chapter on Contact, or creating an Account record type for Alumni Chapter and a custom field for Primary Chapter on Contact are not steps that use standard features available with EDA. Reference:

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

https://powerofus.force.com/s/article/EDA-Affiliations-Mappings

A one-way integration between Salesforce and Marketing Cloud and a two-way integration between the event system and Salesforce are two integration directions that the consultant should recommend to meet the requirement. A one-way integration between Salesforce and Marketing Cloud allows Career Services to use student data in Salesforce to segment and target prospects for email campaigns in Marketing Cloud. A two-way integration between the event system and Salesforce allows Career Services to sync event attendance data from the event system to Salesforce, and update student records in Salesforce with career interest and credit completion data. A one-way integration between Marketing Cloud and the event system, and a two-way integration between the event system and Marketing Cloud are not integration directions that can meet the requirement. Reference:

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

https://trailhead.salesforce.com/en/content/learn/modules/marketing-cloud-connect

Case and Case Comment are two objects that the consultant should use to migrate student Incident and Incident Resolution data from the old system to EDA. Case is an object that represents a student issue or problem that needs to be resolved. Case Comment is an object that stores comments related to a case. Attribute and Behavior Response are not objects that can store Incident and Incident Resolution data in EDA. Reference:

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

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

https://powerofus.force.com/s/article/EDA-Data-Dictionary