Your organization is designing an Azure governance strategy to enforce resource compliance. You need to map the operational requirements to the appropriate Azure Policy effects. Match each operational requirement on the left to its corresponding Azure Policy effect on the right.
- Automatically deploy a dependency resource, such as diagnostic settings, when a resource is created or updated.DeployIfNotExists
- Prevent resource creation or update requests that violate configuration standards.Deny
- Add or update specific properties or tags on a resource during creation or update.Modify
- Log a non-compliance warning event in the activity log without blocking resource deployment.Audit
Answer
DeployIfNotExists matches deploying diagnostic settings; Deny matches blocking resource creation; Modify matches adding or updating tags; Audit matches logging compliance warnings without blocking.
Each requirement is mapped to its correct Azure Policy effect based on their evaluation behavior: DeployIfNotExists handles nested deployment templates; Deny blocks the resource creation; Modify alters resource tags or properties during creation/update; Audit logs compliance warnings without altering the deployment flow.
Step-by-Step Solution
Key Concept
Azure Policy effects define the behavior of resource compliance evaluation and enforcement.