Question 90
In this retired AZ-500 educational case, An Azure policy denies creation of a resource despite a user holding the necessary Azure RBAC write permission. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. That is why the action is: Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block. The directly relevant confirmation is: A policy evaluation identifies the denied condition while a compliant resource deployment succeeds.
Incorrect Answers
The offered principle describes: Application identifiers and tenant-specific service principal object identifiers serve different purposes. The situation in this question instead depends on: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. These are different technical conditions.
This alternative is valid when enterprise application assignment policy can control which users are eligible to sign into the service. The facts here establish a different controlling reason: Permission to invoke a management action does not guarantee governance policy allows the resulting resource.
“Application permissions represent an app's independent identity whereas delegated permissions act for a user” reflects the mechanism: Application permissions represent an app's independent identity whereas delegated permissions act for a user. The actual reported symptoms are better explained by: Permission to invoke a management action does not guarantee governance policy allows the resulting resource.