Skip to main content
  1. Public practice questions
  2. AZ-104 Practice Exams | Azure Administrator Associate
  3. AZ-104 Practice Exam 3

Question 18 — AZ-104 Practice Exam 3

A platform team assigns multiple Azure Policy definitions across scopes. At the management group, a built-in “Allowed locations” policy is assigned with effect = deny. At the subscription, a custom “Tag: application required” policy is assigned with effect = audit. At one resource group, the same “Allowed locations” policy is assigned but with effect = disabled. A developer attempts to create a storage account in a disallowed location within that resource group. (Select two answers)

  1. The create request is rejected because the management group assignment with deny blocks noncompliant deployments.

  2. The disabled resource group assignment prevents the management group assignment from evaluating.

  3. The tag policy logs noncompliance but doesn’t stop the deployment.

  4. The deny can be bypassed because another assignment only audits.

Correct answers

  1. The create request is rejected because the management group assignment with deny blocks noncompliant deployments.

  2. The tag policy logs noncompliance but doesn’t stop the deployment.

Explanations

Correct:
The create request is rejected because the management group assignment with deny blocks noncompliant deployments. The deny effect is synchronous and independently evaluated; higher-scope assignments still apply, and the net result is the most restrictive.
The tag policy logs noncompliance but doesn’t stop the deployment. The audit effect is asynchronous and only records a noncompliant event; it never permits a deployment that another policy denies.

Wrong:
The disabled resource group assignment prevents the management group assignment from evaluating. Disabled turns off only that specific assignment; other assignments at other scopes still evaluate independently.
The deny can be bypassed because another assignment only audits. An audit assignment doesn’t override a deny; Azure Policy layering results in the cumulative most restrictive outcome.