Free Practice Questions for Salesforce Education-Cloud-Consultant Exam

Address Management is a standard feature of EDA that the consultant can mention as part of the analysis of standard functionality in EDA. Address Management is a feature that allows the consultant to store multiple addresses for a Contact or an Account, and specify which address is current, seasonal, or preferred. Address Management also provides reports and dashboards that show address verification status and address changes. Student Advising, Event Management, and Degree Auditing are not standard features of EDA, but rather additional solutions or apps that may need to be purchased. References:

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

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

TDTM is a feature of EDA that allows you to manage the automation and custom logic that runs when data is inserted, updated, or deleted. By disabling unnecessary code, such as trigger handlers or validation rules, you canimprove the performance and speed of the data import, avoid errors or unwanted data creation, and reduce the risk of hitting governor limits12.

Disabling sharing rules using TDTM is not a recommended action, because sharing rules are not controlled by TDTM,but by the Salesforce security model. Sharing rules are used to grant additional access to records based on criteria or ownership. Disabling them mayaffect the visibility and accessibility of the imported data for the users34.

Changing the account model to Household is not a necessary action, because the account model is a preference that depends on how the university wants to organize its contacts and accounts. EDA supports both the Administrative and Household account models, and the import file already defines the Account information. Changing the account model may cause data loss or duplication, and require additional configuration and mapping5 .

Using OmniStudio FlexCard:

OmniStudio FlexCardcan be used to create a dynamicuser interface that displays the application data in a structured format. This can include conditional logic to show or hide fields based on the submission status of the application.

Applying Validation Rule:

Avalidation rulecan be used to enforce that applications cannot be edited after the submission deadline. This ensures data integrity by preventing changes to the application record once the deadline has passed.

Steps to Implement:

Create a FlexCard:

Navigate toOmniStudio>FlexCards.

Create a new FlexCard that displays application details and includes logic to disable editing past the deadline.

Set Up Validation Rule:

Go toSetup>Object Manager>Application Object.

Create a validation rule to check if the current date is past the submissiondeadline and prevent edits.

Example validation rule:AND(ISCHANGED([Application].Status), [Application].Status = 'Submitted', TODAY() > [Application].Submission_Deadline__c)

Testing:

Test the FlexCard and validation rule to ensure that students cannot edittheir applications after the submission deadline.

Ensure the user interface and validation rule work seamlessly together to provide a smooth user experience.

Program Enrollment is an object in EDA that indicates a student’s primary course of study or major. Program Enrollment is an object that represents a junction between a Contact and a Program Plan. Program Enrollment can be used to track various information about a student’s course of study, such as status, start date, end date, or level. The consultant can create a Program Enrollment record for each student and associate it with their primary courseof study or major. Education History, Relationship, and Program Plan Requirement are not objects in EDA that indicate a student’s primary course of study or major. References:

https://powerofus.force.com/s/article/EDA-Program-Enrollments

https://powerofus.force.com/s/article/EDA-Program-Enrollments-Create

Tracking Engagement and Hobbies:

Interest Tagsin Education Cloud allow thetracking of specific interests and hobbies of alumni.

This feature helps in understanding what engages alumni and can be used to tailor communications and activities.

Setting Up Interest Tags:

Define Interest Tags: Create tags that represent different interests and hobbies.

Assign Tags: Assign these tags to alumni based on their interests and engagement history.

Utilizing Interest Tags:

Segmentation: Use Interest Tags to segment alumni for targeted communications and events.

Personalized Outreach: Tailor outreach efforts based on the specific interests and hobbies tracked by the tags.

Implementation Steps:

Configure Tags: Set up and define the tags in the system.

Data Entry: Tag alumni with the appropriate interests.

Analyze Engagement: Use reports and analytics to understand the impact of interest-based engagement.

The consultant should create a Student Case record and an Administrative Account record to set up a student in Student Success Hub. Student Case is an object that represents a student’s request for assistance or support from an advisor or a counselor. Student Case can be used to track various information about a student’s issue, such as status, priority, category, or resolution. The consultant should create a Student Case record for each student who needs assistance or support from Student Success Hub. Administrative Account is an account model that allows users to store information about individuals who are related toan educational institution, such as students, faculty, staff, or alumni. Administrative Account can be used to track various information about an individual, such as name, email, phone, or address. The consultant should create an Administrative Account record for each student who is enrolled in the educational institution. Creating a User record or a Household Account record are not steps to set up a student in Student Success Hub. References:

https://www.salesforce.org/products/student-success-hub/overview/

https://powerofus.force.com/s/article/SSHub-Student-Cases

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

The data should be imported in the order of Account, Term, Program Enrollment, and Course records for the career center that plans to use Student Success Hub and is preparing to import student data. The order of data import is important to ensure that the data is consistent and accurate in Salesforce and that the relationships between the objects are maintained. The data should be imported in the order of Account, Term, Program Enrollment, andCourse records because these objects have dependencies or lookups to each other. For example, a Program Enrollment record has a lookup to an Account record and a Term record, and a Course record has a lookup to a Term record. Importing the data in this order can help avoid errors or missing data. Course, Course Offering, Program Plan, and Affiliation records or Account, Term, Course, and Course Offering records are not correct orders of data import for the career center that plans to use Student Success Hub and is preparing to import student data. References:

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

https://powerofus.force.com/s/article/EDA-Program-Enrollments

Marketing Cloud Business Unit is a solution that the consultant can recommend to meet the requirement of centralizing email communications for alumni and allowing departments across the university to only view their team’s content. Marketing Cloud Business Unit is a feature that allows users to segment their Marketing Cloud account into separate units based on different criteria, such as brands, regions, products, or teams. Marketing Cloud Business Unit can be used to control access to data, content, subscribers, reports, and settings for each unit. Marketing Cloud Business Unit can help the university create a centralized email communication strategy for alumni while maintaining data security and visibility for each department. Salesforce Data Management Platform, Einstein Account-Based Marketing, and Pardot Business Unit are not solutions that can meet the requirement of centralizing email communications for alumni and allowing departments across the university to only view their team’s content. References:

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

https://trailhead.salesforce.com/en/content/learn/modules/marketing-cloud-basics/marketing-cloud-basics-business-units

The consultant should retain sharing rules during the data import because they control the access and visibility of records based on criteria such as record ownership, role hierarchy, or field values. Disabling sharing rules may cause data security or privacy issues. Workflow rules and role hierarchy are configurations that can be disabled during the data import to improve performance and avoid errors or conflicts. References:

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

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

The consultant should discuss with the client that the business user case requires a full Salesforce license, not other license types. Afull Salesforce license allows users to access standard CRM functionality, such as Accounts, Contacts, Opportunities, and Campaigns. This is what the recruitment staff need to access Opportunity and Campaign Member information about students. Other licensetypes, such as Lightning Platform or Community licenses, have limited access to CRM functionality and may not meet the business user case. References:

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

https://trailhead.salesforce.com/en/content/learn/modules/identity_basics/identity_basics_licenses