Question 650
A Microsoft Azure administrator receives this requirement: A Conditional Access policy requiring strong auth is assigned only to a test application, leaving a production administration application outside its scope. Which operating control most directly reduces this recurring risk?
Explanation
Correct Answer
This guardrail addresses conditional access cloud app targeting: The target cloud application selection is wrong and policy enforcement does not cover the actual resource. The prevention measure is: Review policy application scopes after new cloud apps are registered or renamed. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. “Monitor legacy sign-in activity and resolve legitimate dependencies before enforcing global legacy blocking” would address that alternative cause, not the condition in this question: the target cloud application selection is wrong and policy enforcement does not cover the actual resource.
“Audit authenticator registration changes and enforce identity-proofing during account recovery” responds to this separate finding: strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. This question instead needs “Review policy application scopes after new cloud apps are registered or renamed”, so the alternative does not meet the stated condition.
The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. “Test permitted authentication methods against the actual role threat model after policy changes” applies to that separate problem. The observed case is a Conditional Access policy requiring strong auth is assigned only to a test application, leaving a production administration application outside its scope; choosing this alternative would address the wrong failure mode.