Question 170
In this retired AZ-500 educational case, An API publishes only one all-powerful delegated scope for all clients, making least-privileged integration impossible. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: OAuth delegated permission granularity is controlled by the resource API's published scopes. That is why the action is: Define separate appropriate exposed API scopes for read and write capabilities. The directly relevant confirmation is: A read-only client obtains its limited scope and fails the API's write authorization test.
Incorrect Answers
“Resource roles can include operations that expose credentials outside the immediate work requirement” reflects the mechanism: Resource roles can include operations that expose credentials outside the immediate work requirement. The actual reported symptoms are better explained by: OAuth delegated permission granularity is controlled by the resource API's published scopes.
The offered principle describes: Microsoft Entra directory roles and Azure resource roles govern different permission planes. The situation in this question instead depends on: OAuth delegated permission granularity is controlled by the resource API's published scopes. These are different technical conditions.
This alternative is valid when pIM eligibility separates just-in-time activation from long-lived active privileges. The facts here establish a different controlling reason: OAuth delegated permission granularity is controlled by the resource API's published scopes.