Development-Lifecycle-and-Deployment-Architect Practice Test

Explanation:

Change sets provide an easy way to deploy related components, as they allow the user to select the components from a list and add them to the change set. They also provide a simple and declarative method for deployment, as they do not require any coding or scripting. Change sets do not provide the ability to deploy a very large number of components easily, as they have a limit of 10,000 components per change set. They also do not provide the ability to track changes to components, as they do not have any version control or history features.

Explanation:

A and C are the correct answers, as they are the project situations that favor an agile methodology. An agile methodology is a flexible and iterative approach that can accommodate changing requirements, deliver value quickly, and enable frequent feedback and collaboration. A is correct, as a digitization project to update an existing customer-facing process and enable quick adjustments is a situation that requires an agile methodology, as it involves transforming a legacy system, adapting to customer needs, and delivering incremental improvements. C is correct, as an environment with a heavy investment in DevOps capabilities for rapid testing and deployment is a situation that requires an agile methodology, as it enables continuous integration and delivery, as well as quality assurance and automation. B is incorrect, as a project to be executed by a third party, with a fixed and formal scope, budget, and timeline is a situation that favors a waterfall methodology, as it involves clear and stable requirements, contractual obligations, and sequential phases. D is incorrect, as a project with well-defined requirements and complex interactions between front- and back-end systems is a situation that favors a waterfall methodology, as it involves detailed planning, design, and testing, as well as minimal changes and dependencies. You can learn more about this topic in the Agile Basics module on Trailhead.

Explanation:

Integrating an agile issue tracker with software testing and continuous integration tools can provide the following benefits:

Developers can see automated test statuses that commit on a specific user story, which can help them identify and fix any errors or failures quickly.

Developers can use the committed code’s build status directly on the user story record, which can help them track the progress and quality of their work.

Explanation:

The package development model relies on source tracking to automatically track the metadata changes in the package project. However, not all metadata components are supported by source tracking, and some changes may need to be tracked manually. For example, changes to profiles, permission sets, custom metadata types, and custom settings are not supported by source tracking. You can find the list of unsupported components here1. No manual tracking is required for the changes that are supported by source tracking, nor for the changes made via the Setup UI, as they are automatically captured by the package development model.

Explanation:

Facilitating the design of a prioritization model with the stakeholders is the best way to overcome the problem of having many backlog items and competing stakeholders who cannot agree on priority. A prioritization model is a framework that helps the stakeholders evaluate and rank the backlog items based on various criteria, such as value, urgency, effort, risk, etc. By using a prioritization model, the stakeholders can have a clear and objective way of deciding which items are more important and should be done first. Organizing a sprint planning meeting, taking over prioritization, or allowing the delivery teams to pick the work are not effective solutions, as they do not address the root cause of the problem or involve the stakeholders in the decision-making process.