Question 1180
An on-premises user is deleted unexpectedly and the sync engine schedules deletion in Entra ID. Choose the most appropriate next action for this tenant scenario.
Explanation
Correct Answer
The stated constraint is addressed by investigate the source deletion and use available deletion-protection safeguards. This is appropriate because Sync exports can propagate unintended mass deletions. A successful test will show: the mistaken deletion is stopped and the identity remains recoverable.
Incorrect Answers
Although relevant to a cloud account is unexpectedly duplicated after changing its on-premises UPN., it does not establish the requested outcome. Persistent matching identifiers are distinct from mutable sign-in names. Here the measurable requirement is the mistaken deletion is stopped and the identity remains recoverable.
This would focus on a large OU filtering change would remove hundreds of already-synchronized users. rather than the present constraint. Accidental scope removals can deprovision cloud identities. The required success state remains the mistaken deletion is stopped and the identity remains recoverable.
The alternative belongs to the scenario a synchronized user's object anchor changes after an unplanned source migration. That scenario is governed by Source anchor continuity avoids cloud identity replacement. It does not directly prove the mistaken deletion is stopped and the identity remains recoverable.