Given a scenario, determine the appropriate deployment plan.
Deployment plans help to ensure quality and consistency across Salesforce orgs during the application lifecycle. They establish a governance model when deploying changes between connected sandboxes and the production orgs.
A client uses separate Salesforce sandboxes for development, SIT, UAT, and staging. The client has implemented the following changes in the development sandbox, and requests for a suitable plan to deploy those changes to the production org:
Deploying changes from the developer sandbox to the production org requires several deployments across connected sandboxes, and automated as well as manual steps.
Most components changes can be packaged into a single change set to reduce manual deployment work. The change set can then be deployed across sandboxes until the final production deployment.
However, some changes cannot be deployed with change sets. To ensure consistency, those and all other deployment steps need to be documented in the deployment plan. The deployment steps can be categorized into pre-deployment, deployment, and post-deployment steps.
For the first deployment from the developer sandbox to the SIT sandbox, the deployment plan could like like this, and similarly for the consecutive deployments: