Question 320
An Azure security engineer investigates the following incident: A calendar integration with no directory management duties has been granted broad Directory.ReadWrite.All application permission. Which outcome most clearly verifies that the issue is resolved?
Explanation
Correct Answer
This validates the specific control for overprivileged oauth permission grant: The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. The associated corrective action is: Revoke the excessive permission and grant only the narrowly required API scopes or app roles. Testing a different component would not establish this result.
Incorrect Answers
The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. “Configure a certificate credential or supported workload federation and remove the leaked text secret” would address that alternative cause, not the condition in this question: the OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact.
“Have an authorized administrator evaluate and grant only the required application permission after review” responds to this separate finding: the requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. This question instead needs “Revoke the excessive permission and grant only the narrowly required API scopes or app roles”, so the alternative does not meet the stated condition.
Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. “Select approved application permissions with administrator consent and configure client-credentials access” applies to that separate problem. The observed case is a calendar integration with no directory management duties has been granted broad Directory.ReadWrite.All application permission; choosing this alternative would address the wrong failure mode.