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

A, C, and E are the correct answers, as Force.com Migration Tool, Source Control Tool, and Continuous Integration Build Tool are the tools that should be used to enable a continuous integration process to help manage code quality. A continuous integration process is a practice that involves merging code changes from multiple developers into a common repository, and then testing and validating them automatically, before deploying them to the target environment. Force.com Migration Tool is a tool that uses the Metadata API to retrieve and deploy metadata components, such as code, from one org to another. Source Control Tool is a tool that manages the versions and changes of the code, and allows for collaboration and integration among the developers. Continuous Integration Build Tool is a tool that automates the testing and deployment of the code, and ensures that the code meets the quality and functionality standards. B is incorrect, as Full Sandbox Environment is not a tool that should be used to enable a continuous integration process, as it is a copy of a production org that is used for development and testing purposes, but not for merging, testing, or deploying code changes. D is incorrect, as Project Management Tool is not a tool that should be used to enable a continuous integration process, as it is a tool that helps to plan, organize, and track the progress of the project, but not to manage, test, or deploy code changes. You can learn more about these tools in the Continuous Integration and Continuous Delivery module on Trailhead.

A change to a multi-org strategy can be justified by two reasons: launching a new line of business with independent processes and acquiring a company that has its own Salesforce org and operates in a different business with its own set of regulatory requirements. These reasons indicate that the single-org strategy is no longer feasible or optimal, as it would require too much customization, complexity, and compliance. Using Chatter for collaboration among different business units is not a reason to change to a multi-org strategy, as Chatter can work across multiple orgs. Following a unification enterprise architecture operating model is also not a reason to change to a multi-org strategy, as this model implies having orgs with the same processes implemented for each business unit, which is more suitable for a single-org strategy.

Utilizing a dedicated developer pro sandbox to address critical bugs and release to production is the recommended release management strategy, as it allows the development team to work on the new project without being interrupted by the bug fixes, and also ensures that the bug fixes are deployed to production as soon as possible. Including fixes for critical bugs in the ongoing development sandboxes is not recommended, as it may delay the release of the bug fixes and also introduce conflicts with the new code. Keeping teams separate until the end of the project and creating a full copy sandbox to merge their work then is not recommended, as it may create a lot of merge conflicts and integration issues. Addressing critical bugs in the development sandboxes and pushing those changes to production separately is not recommended, as it may create inconsistencies between the development and production environments.

The responsibility of the Technical Architect within a Change Control Board meeting is to approve the upcoming release for deployment into production, as they are the ones who have the authority and expertise to evaluate the quality and readiness of the release2. Option A is not correct, as prioritizing the Salesforce product roadmap with business stakeholders is not a task that is done in a Change Control Board meeting, but rather in a strategic planning session. Option B is not correct, as conducting code reviews for projects in the development phase is not a task that is done in a Change Control Board meeting, but rather in a code review session. Option C is not correct, as troubleshooting deployment errors that occurred during the last release is not a task that is done in a Change Control Board meeting, but rather in a post-deployment review session.