The first thing that the consultant should do to assess the situation is to document solution requirements from the groups involved. This will help the consultant understand the current state, pain points, goals, and needs of each group that uses or will use Salesforce, and how they relate to each other. This will also help the consultant determine whether EDA is a suitable solution for all groups, or whether some customization or integrationis needed. Submitting a Salesforce Support case to merge orgs, installing EDA into one of the production environments, and creating a new Salesforce org using EDA as the foundation are not good first steps, because they do not involve gathering requirements from the stakeholders, and they may cause data loss or disruption. References:
https://trailhead.salesforce.com/en/content/learn/modules/education-cloud-basics/education-cloud-basics-discovery
https://powerofus.force.com/s/article/EDA-Migrate
QUESTIONNO: 4
A CRM committee for a university has asked a consultant about the major release cadence of Salesforce.org and Salesforce.com platform enhancements.
When are Salesforce.org releases?
A. Approximately two weeks after Salesforce.com releases
B. Approximately one month before Salesforce.com releases
C. Approximately two weeks before Salesforce.com releases
D. Approximately one month after Safesforce.com releases
Answer: A
Salesforce.org releases are approximately two weeks after Salesforce.com releases.This means that Salesforce.org customers can benefit from both platform enhancements and industry-specific solutions in a timely manner. The other options are incorrect because they do not reflect the actual release cadence of Salesforce.org. References:
https://powerofus.force.com/s/article/SFDO-Release-Schedule
https://www.salesforce.org/blog/salesforce-org-release-schedule/
