An organization is configuring governance controls across their Azure subscriptions. Match each Azure Policy effect to the correct operational behavior that occurs during resource creation or update.
- DenyBlocks the resource deployment request immediately and records a failed evaluation in the activity log.
- AuditAllows the resource deployment request to succeed but generates a non-compliance event in the policy history.
- ModifyApplies defined tag or property updates to the resource before the request is processed by the resource provider.
- DeployIfNotExistsExecutes a nested Resource Manager template to perform remediation only after the resource is successfully deployed.
Cevap
Deny matches blocking resource deployment requests; Audit matches allowing resource deployment but generating a non-compliance event; Modify matches applying defined tag or property updates before processing; DeployIfNotExists matches executing a nested Resource Manager template for remediation after successful deployment.
The correct pairings align each policy effect with its exact evaluation phase and system behavior: Deny blocks the request; Audit creates a compliance log without blocking; Modify alters properties before creation; and DeployIfNotExists deploys a template to remediate after creation.
Adım Adım Çözüm
Anahtar Kavram
Azure Policy effects define the actions taken when resource properties match the rule conditions of a policy definition.