Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft Certified: DevOps Engineer Expert · Microsoft
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Subscription Health scans (like Azure Secure Score or Advisor recommendations) are designed to check for issues in Azure resources, such as VMs, networks, or storage accounts — not Azure DevOps project configurations.
Performing a Subscription Health scan when packages are created does not directly prevent the configuration of the project from changing over time. A Subscription Health scan primarily helps identify potential issues related to subscription-level resources and their compliance with best practices, but it does not specifically enforce configuration immutability within a project. To prevent changes to a project’s configuration, you would typically use other mechanisms, such as: Azure DevOps policies: These can be used to enforce rules around code changes, including branch policies and approval requirements, to prevent unwanted configuration changes. Infrastructure as Code (IaC): Using tools like ARM templates, Terraform, or Azure DevOps pipelines to manage and enforce configurations programmatically. Role-Based Access Control (RBAC): Limiting permissions for users who can make changes to the project's configuration.
Correct is B