Question 750
A helpdesk gets calls about missing users but checks only whether the synchronization server's Windows service is running. The team believes no other action is necessary. Which failure mechanism best matches the observed facts?
Explanation
Correct Answer
The actual failure mechanism is A running local service is not proof that scheduled sync and identity exports succeed. Its relevance follows from the stated tenant facts, not just a generic security recommendation. Correct it by use Microsoft Entra Connect Health and sync monitoring to identify degraded synchronization pipelines. Then verify: The dashboard shows the actual connector or sync failure associated with the affected objects.
Incorrect Answers
Directory synchronization can fail or create duplicate identities when legacy attributes violate cloud requirements. The stated symptoms instead indicate that a running local service is not proof that scheduled sync and identity exports succeed.
Overlapping synchronization engines can apply incompatible attribute rules to the same cloud objects. The stated symptoms instead indicate that a running local service is not proof that scheduled sync and identity exports succeed.
An unverified or invalid sign-in suffix can prevent desired cloud UPN alignment. The stated symptoms instead indicate that a running local service is not proof that scheduled sync and identity exports succeed.