Salesforce Updated Development-Lifecycle-and-Deployment-Architect Exam Questions and Answers by ari

This is the correct answer because having developers work in separate branches and merge their changes in a common branch for testing can reduce the risk of overwriting others’ changes and ensure code quality and consistency. Having all developers work in the same branch or in the HEAD may cause conflicts and errors. Not using source control is not a good practice and may result in data loss and lack of version control.

The best way to stop the rollbacks from happening is to ensure report metadata is exported daily and that it is merged into the developer branches before the next release. This way, the reports and dashboards will be up to date and consistent across all environments. Using a third-party data warehouse is not a solution, as it does not address the root cause of the rollbacks. Removing the executive’s ability to change reports is not a good practice, as it limits their flexibility and autonomy. Backing up and reimporting the reports before and after the release is not a reliable or scalable solution, as it can introduce errors and inconsistencies.

Develop, Build Release, and Test are three steps that apply to any Salesforce development project, regardless of the size, complexity, or methodology. Develop is the step where the developers create the code and configuration components that meet the requirements and specifications. Build Release is the step where the components are packaged and deployed to different environments for testing and validation. Test is the step where the components are verified and validated against the requirements and specifications, as well as the quality and performance standards. Continuous Integration and Change Sets are not steps, but tools or techniques that can be used to facilitate the development project. Continuous Integration is a technique that involves merging the code from different developers frequently and automatically, to ensure consistency and avoid conflicts. Change Sets are a tool that allows the developers to move the components from one org to another org.

The best option is to send a package.xml file with associated metadata in a .zip file to the Release Management team, as this will allow them to use the Metadata API to deploy the components to the production org. Option A is not feasible, as change sets cannot be downloaded from sandboxes. Option B is not sufficient, as the readMetadata call only retrieves the metadata information, not the actual components. Option C is not reliable, as the audit trail may not capture all the changes made in the sandbox.