Question 600
A platform security assessment reveals this issue: An unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events. What technical cause best accounts for the described behavior?
Explanation
Correct Answer
The described technical condition is: Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. The appropriate corrective action is: Inspect service principal sign-in logs and correlated credential or conditional policy results. Confirm with: The failing app identity, time and error reason are identified in the service principal log stream.
Incorrect Answers
The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. “Have an authorized administrator evaluate and grant only the required application permission after review” would address that alternative cause, not the condition in this question: non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.
“Select approved application permissions with administrator consent and configure client-credentials access” responds to this separate finding: delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. This question instead needs “Inspect service principal sign-in logs and correlated credential or conditional policy results”, so the alternative does not meet the stated condition.
Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. “Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles” applies to that separate problem. The observed case is an unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events; choosing this alternative would address the wrong failure mode.