Your organization is implementing Azure Policy to enforce governance standards across multiple subscriptions. You need to match the specific operational compliance requirements with the correct Azure Policy effects. Match each operational requirement on the left to its corresponding Azure Policy effect on the right.
- Block the creation or update of any resource that does not contain a required 'CostCenter' tag.Deny
- Generate a compliance warning in the Azure Policy dashboard when a virtual machine is created without disaster recovery configured, without preventing the deployment.Audit
- Automatically insert a default 'Environment' tag with the value 'Production' during resource creation if the tag is missing.Modify
- Provision a diagnostic settings resource automatically if a newly deployed Key Vault does not have diagnostic logging enabled.DeployIfNotExists
Answer
To enforce the requirements, block resource creation with Deny, log non-compliance without blocking with Audit, insert default tags during creation with Modify, and automatically provision missing dependent resources with DeployIfNotExists.
Each requirement correctly maps to the corresponding Azure Policy effect: Deny blocks non-compliant requests; Audit logs non-compliant configurations; Modify adjusts tags or properties on the fly; and DeployIfNotExists deploys a template when a dependent resource is missing.
Step-by-Step Solution
Key Concept
Azure Policy effects determine what action is taken when a policy definition is evaluated against resources.
Estimated Time:1m 30s