Salesforce Updated Education-Cloud-Consultant Exam Questions and Answers by willow-rose

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 correct order of operations to ensure customer success in an Education Cloud implementation is:

Conduct Discovery Workshops: This is the first step where the consultant gathers information and requirements from the customer and stakeholders through interviews, surveys, or observations.

Document Current State: This is the second step where the consultant analyzes and documents the current processes and systems that the customer uses and identifies gaps and opportunities for improvement.

Generate Solution Design: This is the third step where the consultant creates and presents a solution design document that outlines how Salesforce will meet the customer’s requirements and expectations, and defines the scope, timeline, and budget of the project.

Write Test Scripts & Plans: This is the fourth step where the consultant writes test scripts and plans that describe how to test the functionality and usability of the solution in different scenarios and conditions, and defines the success criteria and exit criteria for testing.

Build Solution & Test: This is the fifth step where the consultant builds the solution in a sandbox environment using declarative or programmatic tools, and tests the solution using the test scripts and plans to ensure quality and accuracy.

Deploy: This is the sixth and final step where the consultant deploys the solution into the production environment using change sets or other deployment tools, and provides training and support to the customer and end users.

Documenting Current State, Conducting Discovery Workshops, Writing Test Scripts & Plans, Building Solution & Test, Generating Solution Design, or Deploying are not correct orders of operations to ensure customer success in an Education Cloud implementation. References:

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

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

The consultant should use a custom index to resolve the issue of taking a long time to search and generate list views for the large online university’s Salesforce environment that has a large volume of records and uses EDA. A custom index is a feature that allows users to create an index on a field that is not indexed by default, such as a customfield, a long text area field, or a multi-select picklist field. A custom index can help improve the performance and speed of queries and list views that use the indexed field as a filter. The consultant should identify the fields that are frequently used in searches and list views, and request Salesforce Support to create a custom index on them. MuleSoft Anypoint Platform, Data Loader error logs, and Table-Driven Trigger Management are not features that can resolve the issue of taking a long time to search and generate list views for the large online university’s Salesforce environment that has a large volume of records and uses EDA. References:

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

https://developer.salesforce.com/docs/atlas.en-us.salesforce_large_data_volumes_bp.meta/salesforce_large_data_volumes_bp/ldv_deployments_infrastructure_indexes.htm

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 anAccount, 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