Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You manage a project in Azure DevOps.
You need to prevent the configuration of the project from changing over time.
Solution: Add a code coverage step to the build pipelines.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.B
Instead implement Continuous Assurance for the project.
https://azsk.azurewebsites.net/04-Continous-Assurance/Readme.htmlNo, adding a code coverage step to the build pipeline does not meet the goal of preventing the configuration of the project from changing over time.
Code coverage is a metric that measures the proportion of code in an application that is tested by automated tests. It does not have any impact on the configuration of the project.
To prevent the configuration of the project from changing over time, you would need to use version control to manage changes to the project's configuration files. You can use Azure Repos or GitHub as the version control system in Azure DevOps, and use branching and merging strategies to manage changes to the project configuration.
You may also consider using Azure Pipelines to enforce a release gate policy that blocks deployments if the configuration has changed. This ensures that the configuration remains consistent across different environments and reduces the risk of configuration-related issues in production.
Therefore, the correct answer is B. No, adding a code coverage step to the build pipeline does not meet the goal.