Salesforce Education-Cloud-Consultant Exam Dumps

The consultant can meet the business requirement by setting View Dashboard As to the dashboard viewer and sharing it with program directors. This will allow the program directors to see the same reports as the Dean, but filtered by their own program, based on the sharing settings. Checking the Let Dashboard Viewers Choose Whom They View the Dashboard As on the Dean's dashboard, setting View Dashboard As to the Dean and sharing it with program directors, and adding a dashboard filter to the Dean's dashboard and saving it to All Folders are not options that can meet the business requirement. Reference:

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

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

The consultant should review the Relationships object first when noticing that there are more than 10,000 child records associated to a single parent record for the institution that is experiencing record locking and sharing performance issues in a Salesforce org with EDA. The Relationships object is an object in EDA that allows users to store information about how two Contacts are related to each other, such as parent-child, sibling, or spouse. The Relationships object can cause record locking and sharing performance issues in a Salesforce org with EDA if there are too many child records associated to a single parent record, such as a Contact with many Relationships or Affiliations. The consultant should review the Relationships object first when noticing that there are more than 10,000 child records associated to a single parent record for the institution that is experiencing record locking and sharing performance issues in a Salesforce org with EDA by checking if there are any data skew or ownership skew issues and applying best practices to resolve them. Accounts or Affiliations are not objects that the consultant should review first when noticing that there are more than 10,000 child records associated to a single parent record for the institution that is experiencing record locking and sharing performance issues in a Salesforce org with EDA. Reference:

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

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

The action that the consultant should take when loading a large volume of alumni Contact records into a new Salesforce environment is B. Set the Account and Contact's sharing to Private before the data load1. This is because setting the sharing to Private can improve the performance and speed of the data load, as it reduces the number of sharing calculations and recalculations that Salesforce has to perform during the process. Setting the sharing to Private can also prevent unauthorized access and visibility of the data by other users until the data load is complete and verified2.

A . Set the Account and Contact's sharing to Public Read/Write before the data load and C. Load record owners after the Account and Contact data load is complete are not valid actions for this scenario. Setting the sharing to Public Read/Write can degrade the performance and speed of the data load, as it increases the number of sharing calculations and recalculations that Salesforce has to perform during the process. Setting the sharing to Public Read/Write can also expose the data to other users who may not have the appropriate permissions or roles to view or edit the data2. Loading record owners after the Account and Contact data load is complete can cause errors and inconsistencies in the data, as the record owners are required fields for the Account and Contact objects. Loading record owners after the data load can also trigger unnecessary workflows and validations that can affect the data quality and integrity3.

Data skew is the likely cause for all of these issues, such as record locking, long search times, and long record save times. Data skew is a condition that occurs when a large number of child records are associated with a single parent record, or when a large number of records are owned by a single user. Data skew can affect performance and functionality, such as locking records, slowing down queries, and increasing save times. TDTM, insufficient code coverage, and insufficient data storage are not likely causes for all of these issues. Reference:

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

https://developer.salesforce.com/blogs/engineering/2012/04/avoid-account-data-skew-for-peak-performance.html

After installing EDA, the consultant needs to make the EDA record types available to profiles that need to access them. This is because EDA comes with several custom record types for standard objects, such as Account, Contact, Course, and Program Enrollment. These record types enable different views and fields for different types of records, such as Household, Student, Faculty, Course Offering, and Program Enrollment. By default, these record types are not assigned to any profiles, so the consultant needs to manually assign them to the appropriate profiles based on the business requirements and user roles of the university. This will ensure that the users can see and use the EDA record types and fields correctly and efficiently.Reference:Education Data Architecture Basics,Assign Record Types to Profiles