Question 70
In this retired AZ-500 educational case, An identity team treats the per-user MFA setting as equivalent to every Conditional Access policy configuration. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. That is why the action is: Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone. The directly relevant confirmation is: Sign-in logs show the intended CA policy applied with its required MFA grant control.
Incorrect Answers
This alternative is valid when oAuth token issuance differs between interactive delegated sign-in and confidential client credentials. The facts here establish a different controlling reason: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.
“OAuth delegated permission granularity is controlled by the resource API's published scopes” reflects the mechanism: OAuth delegated permission granularity is controlled by the resource API's published scopes. The actual reported symptoms are better explained by: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.
This alternative is valid when credential expiration prevents a service principal from proving its identity at token issuance. The facts here establish a different controlling reason: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.