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: Perform a Subscription Health scan when packages are created.
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.
Note: The Subscription Security health check features in AzSK contains a set of scripts that examines a subscription and flags off security issues, misconfigurations or obsolete artifacts/settings which can put your subscription at higher risk.
https://azsk.azurewebsites.net/04-Continous-Assurance/Readme.htmlThe solution provided in the question, i.e., performing a Subscription Health scan when packages are created, does not seem to meet the stated goal of preventing the configuration of the project from changing over time.
Subscription Health scan is a feature provided by Azure DevOps to check the overall health of your subscriptions, including the usage and costs of resources, and to identify any potential issues. However, it is not directly related to preventing the configuration of a project from changing over time.
To prevent the configuration of a project from changing over time, you can use the following methods:
Version Control: Use version control for your project files, such as Git or Azure Repos, to keep track of changes and maintain a history of all changes made to the project configuration.
Access Control: Use Azure DevOps access control to restrict access to the project configuration to only authorized personnel. This will prevent unauthorized changes to the project configuration.
Change Management: Implement a change management process that includes a review and approval process for any changes to the project configuration. This will help ensure that all changes are documented, reviewed, and approved before being implemented.
Automation: Use automation to enforce configuration policies, such as Azure Policy or Azure Resource Manager templates, to prevent configuration changes that violate your organization's policies.
Therefore, the given solution does not meet the goal of preventing the configuration of the project from changing over time. The correct answer would be B. No.