Question 200
An Azure security engineer investigates the following incident: A leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation. Which outcome most clearly verifies that the issue is resolved?
Explanation
Correct Answer
This validates the specific control for identity protection user risk response: No effective user-risk-based identity protection response has been configured for the relevant identities. The associated corrective action is: Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate. Testing a different component would not establish this result.
Incorrect Answers
Creating a managed identity alone does not grant the target resource's required data-plane role. “Grant the appropriate storage blob data role to the VM identity at the least necessary scope” would address that alternative cause, not the condition in this question: no effective user-risk-based identity protection response has been configured for the relevant identities.
“Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation” responds to this separate finding: the app registration client credential has expired and the workload has no safe rotation mechanism. This question instead needs “Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate”, so the alternative does not meet the stated condition.
The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. “Provision or consent the enterprise application service principal and configure appropriate access and controls” applies to that separate problem. The observed case is a leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation; choosing this alternative would address the wrong failure mode.