Development-Lifecycle-and-Deployment-Architect Practice Test

Explanation:

Two options that should be considered when making production changes in a highly regulated and audited environment are: all changes including hotfixes should be reviewed against security principles, and any production change should have explicit stakeholder approval. These options can help ensure that the changes are compliant with the regulations and have the necessary authorization and documentation. No manual steps should be carried out is not a valid option, as some changes may require manual steps, such as data migration or post-deployment verification. After deployment, the development team should test and verify functionality in production is also not a valid option, as testing and verification should be done in a lower environment before deploying to production, and the responsibility of testing and verifying functionality in production should be assigned to a different team than the development team. See Application Lifecycle and Deployment for more details.

Explanation:

Program team and executive sponsors are two user groups that an architect should recommend to join the COE. A program team is a group of people who are responsible for managing and delivering the Salesforce projects and initiatives. They can provide the COE with the technical expertise, best practices, and project management skills. An executive sponsor is a senior leader who supports and advocates for the Salesforce program. They can provide the COE with the strategic direction, business alignment, and funding support.

Explanation:

A single org strategy has the benefits of increased ability to collaborate, centralized data location, and consistent processes across the business. These factors can improve efficiency, data quality, and user adoption. A single org strategy may not allow for tailored implementation or fewer inter-dependencies, as different business units may have different requirements and dependencies.

Explanation:

Two software development methodologies that an architect should suggest to solve the issue of visibility are Scrum and Kanban. Scrum is based on the value of openness, which means that the team members and stakeholders share information and feedback regularly and transparently. Kanban is based on the principle of making everything visible, which means that the team uses a visual board to track the progress and status of the work items. Waterfall is not a good methodology for visibility, as it does not allow for frequent communication and feedback. DevOps is not a methodology, but a culture and practice that aims to improve collaboration and delivery across the software development lifecycle.

Explanation:

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.