Question 100
A platform security assessment reveals this issue: A deployment account has Contributor on a resource group but receives an explicit deny through a managed deployment, and an administrator keeps adding more Allow role assignments. What technical cause best accounts for the described behavior?
Explanation
Correct Answer
The described technical condition is: Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. The appropriate corrective action is: Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures. Confirm with: A test write succeeds only after the legitimate deny condition is resolved without adding unnecessary privilege.
Incorrect Answers
NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. “Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment” would address that alternative cause, not the condition in this question: azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope.
“Configure the PIM role activation requirements to demand the approved strong authentication method” responds to this separate finding: pIM role settings have not required the intended multifactor or authentication-strength control at activation. This question instead needs “Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures”, so the alternative does not meet the stated condition.
A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations” applies to that separate problem. The observed case is a deployment account has Contributor on a resource group but receives an explicit deny through a managed deployment, and an administrator keeps adding more Allow role assignments; choosing this alternative would address the wrong failure mode.