Question 60
A change appears correct at a glance, but the requirement is still unmet: A security team needs to disable a compromised cloud account immediately without deleting historical audit records. The key observed symptom is: The compromised user can still complete a new interactive sign-in. Which cause should be investigated first?
Explanation
Correct Answer
Correct diagnosis. The account's display name was changed without blocking sign-in or invalidating sessions. This fault explains the observed failure: The compromised user can still complete a new interactive sign-in. The intended configuration would instead be: Block the compromised user from new sign-in, revoke the available refresh sessions, and validate active resource access with CAE-aware clients without assuming all old access tokens instantly expire.
Incorrect Answers
The sign-in UPN was edited without the associated domain being verified or mail routing checked. The reported symptom instead has this cause: The account's display name was changed without blocking sign-in or invalidating sessions. The corrective action is: Block the compromised user from new sign-in, revoke the available refresh sessions, and validate active resource access with CAE-aware clients without assuming all old access tokens instantly expire.
The assigned SKU has no available licenses or a conflicting service-plan prerequisite. The reported symptom instead has this cause: The account's display name was changed without blocking sign-in or invalidating sessions. The corrective action is: Block the compromised user from new sign-in, revoke the available refresh sessions, and validate active resource access with CAE-aware clients without assuming all old access tokens instantly expire.
The membership rule references department rather than the maintained employeeType field. The reported symptom instead has this cause: The account's display name was changed without blocking sign-in or invalidating sessions. The corrective action is: Block the compromised user from new sign-in, revoke the available refresh sessions, and validate active resource access with CAE-aware clients without assuming all old access tokens instantly expire.