Salesforce Updated Education-Cloud-Consultant Exam Questions and Answers by subhan

Pathways and Plan Requirements are two components that the consultant can recommend to meet the requirement of providing a way for students and advisors to picture academic options more clearly and visualize degree requirements. Pathways is a component that allows users to create and manage academic plans for students, such as majors, minors, or certificates. Pathways can help students and advisors picture academic options more clearly by showing the courses and requirements needed to complete an academic plan. Plan Requirements is a component that allows users to define and group the requirements for an academic plan, such as credits, courses, or electives. Plan Requirements can help students and advisors visualize degree requirements by showing the progress and status of each requirement for an academic plan. Success Plans and Path are not components that can meet the requirement of providing a way for students and advisors to picture academic options more clearly and visualize degree requirements. References:

• https://www.salesforce.org/products/student-success-hub/overview/
• https://powerofus.force.com/s/article/SSHub-Pathways
• https://powerofus.force.com/s/article/SSHub-Plan-Requirements

The consultant should recommend to disable address-related Trigger Handler records for the university that uses EDA to manage its prospective and current students and has the student Contact Mailing Address fields and records populated in Salesforce through an integration with an external system. Trigger Handler records are records that control the behavior of EDA triggers and can be disabled or enabled as needed. Disabling address-related Trigger Handler records can help prevent duplicate or conflicting address records from being created or updated by EDA when the student Contact Mailing Address fields and records are populated in Salesforce through an integration with an external system. Disabling all EDA and custom Trigger Handler records, setting record-level trigger firing based on the Account record type, or setting the Default Account Model to Administrative are not recommendations for the university that uses EDA to manage its prospective and current students and has the student Contact Mailing Address fields and records populated in Salesforce through an integration with an external system. References:

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

Einstein Prediction Builder is a Salesforce solution that the consultant can recommend to automatically create a supporters’ score based on their donation amount, giving capacity, giving history, and relationship type to the university. Einstein Prediction Builder allows the consultant to create custom predictive models without code, using fields from any object as inputs and outputs. Tableau CRM, Nonprofit Success Pack, and Insights Platform Data Integrity are not Salesforce solutions that can create a supporters’ score based on the given criteria. References:

• https://help.salesforce.com/s/articleView?id=sf.bi_prediction_builder_overview.htm&type=5
• https://trailhead.salesforce.com/en/content/learn/modules/prediction_builder_basics

The consultant should clone the EDA Compact Layout as a step to accomplish making changes to compact layouts in EDA and having those changes persist when a new release is pushed to the Salesforce environment. A compact layout is a layout that shows key fields of a record in a summary view, such as in a list view or a record highlight panel. Cloning the EDA Compact Layout means creating a copy of the default compact layout provided by EDA and making changes to it, such as adding or removing fields. Cloning the EDA Compact Layout can help the consultant accomplish making changes to compact layouts in EDA and having those changes persist when a new release is pushed to the Salesforce environment by ensuring that the custom compact layout will not be overwritten by EDA updates. Editing the Mini Page Layout, assigning the Mini Page Layout to all users, or creating a custom Record Type are not steps that the consultant should take to accomplish making changes to compact layouts in EDA and having those changes persist when a new release is pushed to the Salesforce environment. References:

• https://help.salesforce.com/s/articleView?id=sf.compact_layouts_overview.htm&type=5
• https://powerofus.force.com/s/article/EDA-Compact-Layouts