Question 550
A proposed fix must be validated: Identity Protection flags a user with high user risk after leaked credentials, even though the user's current device is healthy. How should the team validate that its change solved the stated problem?
Explanation
Correct Answer
The affected account is remediated, monitored, and has the appropriate risk state afterward. The case concerns respond to a risky user account: Identity Protection flags a user with high user risk after leaked credentials, even though the user's current device is healthy. User risk and device compliance describe different dimensions of an access decision. This answers the acceptance evidence for this change because it addresses the explicit constraint. The action being validated is: follow approved user-risk remediation such as securing credentials and investigating the account. The check must use the affected users, data, or devices.
Incorrect Answers
Device compliance conditions rely on evaluated device posture, not just successful user authentication. The records needed for this specific case concern: Inspect risky-user detections, sign-in evidence, and prior remediation history.
Risk triage requires distinguishing actual remediation from administrative disposition changes. The current corrective requirement is: Follow approved user-risk remediation such as securing credentials and investigating the account.
Sign-in risk differs from user risk and must be addressed at the relevant policy scope. The appropriate acceptance check is: The affected account is remediated, monitored, and has the appropriate risk state afterward.