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: Implement Continuous Integration for the project.
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, implementing Continuous Integration for the project does not meet the goal of preventing the configuration of the project from changing over time.
Continuous Integration (CI) is a DevOps practice that involves integrating code changes into a shared repository frequently. It involves automated building and testing of code changes. While CI can help catch issues early in the development process, it does not address the goal of preventing the configuration of the project from changing over time.
To prevent the configuration of the project from changing over time, you need to implement a Configuration Management process. Configuration Management is the practice of identifying, organizing, and controlling changes to configuration items. Configuration items include hardware, software, documentation, and processes.
In Azure DevOps, you can implement Configuration Management using features such as version control, build policies, and release pipelines. Version control enables you to track changes to source code, while build policies enable you to control who can make changes to the source code. Release pipelines enable you to deploy changes in a controlled manner.
In summary, to prevent the configuration of the project from changing over time, you need to implement Configuration Management practices such as version control, build policies, and release pipelines. Implementing Continuous Integration alone does not meet this goal. Therefore, the correct answer is B. No.