Exam AZ-400 topic 3 question 22 discussion

IMPORTANT: DevOps Kit (AzSK) is being sunset by end of FY21

Agree to suggested answer

you can combine Continuous Assurance with access controls to help prevent the configuration of an Azure DevOps project from changing over time. By using access controls and other security best practices, you can limit the ability of users to make unauthorized changes to the project configuration. Continuous Assurance, on the other hand, will monitor for any drift from the desired or secure state and alert you if any changes occur.

According to chatGPT, B. No. Continuous Assurance is a real feature, but it is not related to preventing configuration changes over time. Instead, it is a security feature that continuously monitors your Azure DevOps organization for vulnerabilities, configuration issues, and potential security threats. To prevent configuration changes over time, you may consider implementing some of the following: Implement a code review process for any changes made to the project configuration. Use version control to manage changes to the project configuration. Implement policies in Azure DevOps that prevent changes to critical configuration settings. Use Azure DevOps audit logs to monitor changes to the project configuration.

https://www.microsoft.com/en-us/insidetrack/building-cloud-apps-using-the-secure-devops-kit-for-azure: "Continuous assurance prevents security state drift, helps to stay current with Azure security feature improvements" Answer is Yes

Correct, continuous assurance

The closest answer to this is azure app configuration. App configuration supports - Microservices based on Azure Kubernetes Service, Azure Service Fabric, or other containerized apps deployed in one or more geographies - Serverless apps, which include Azure Functions or other event-driven stateless compute apps - Continuous deployment pipeline

Dont think this question is relevant anaymore

correct explanation

Biggest Correct Here.

CA correct