A large company is about to undertake its initial Sales Cloud implementation. Different people will create features in multiple sandboxes. The consultant has recommended using change sets to move customizations to the full copy sandbox for testing and then move them to production for release.
Which two approaches should the consultant recommend to help migrate the customizations from the full copy sandbox to production? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D.BC
To migrate customizations from the full copy sandbox to production in a Sales Cloud implementation, the consultant should recommend the following two approaches:
C. Utilize change set tool dependency management: Change sets are a built-in feature in Salesforce that allow administrators and developers to bundle and migrate customizations between environments. Change sets provide a straightforward and user-friendly way to move metadata components, such as custom objects, fields, workflows, reports, and more, from one organization to another. By utilizing change set tool dependency management, the consultant can ensure that all dependencies associated with the customizations are included and deployed correctly. This helps maintain the integrity of the implementation and ensures that all required components are moved together.
D. Leverage cloud-based Git version control to deploy changes: Git is a popular distributed version control system widely used for managing source code and collaborating on software development projects. Leveraging a cloud-based Git version control system allows the consultant to have a centralized repository to manage and track changes made in the full copy sandbox. This approach provides benefits such as version history, branching, merging, and collaboration among multiple developers. By using Git, the consultant can commit changes made in the full copy sandbox to a repository and then deploy those changes to the production environment when ready, ensuring better control and visibility over the migration process.
Explanations for the other options:
A. Track manual changes in a spreadsheet: Tracking manual changes in a spreadsheet is a manual and error-prone approach. It lacks the automation and reliability necessary for a seamless migration process. Relying solely on a spreadsheet can lead to missed changes, human errors, and difficulties in tracking the status of customizations. Therefore, this option is not the best approach for migrating customizations between sandboxes and production.
B. Use Salesforce DX with Visual Studio to deploy changes: Salesforce DX (Developer Experience) is a set of tools and features that enhance the development and deployment process in Salesforce. Visual Studio Code is a popular code editor used by developers for various programming languages. While Salesforce DX with Visual Studio Code is a powerful development combination, it is not specifically designed for migrating customizations between environments. Salesforce DX is more focused on source-driven development and continuous integration, providing capabilities like scratch orgs, source control integration, and CLI commands. While Salesforce DX can be used to deploy changes, it is not the most recommended approach for migrating customizations from the full copy sandbox to production compared to the options mentioned above.
In summary, the consultant should recommend utilizing change set tool dependency management and leveraging cloud-based Git version control to migrate customizations from the full copy sandbox to production in a Sales Cloud implementation. These approaches offer better control, automation, and reliability in the migration process.