Question 690
A company prepares to synchronize legacy AD DS accounts with cloud identities while userPrincipalName values contain invalid characters. The team believes no other action is necessary. Which failure mechanism best matches the observed facts?
Explanation
Correct Answer
The actual failure mechanism is Directory synchronization can fail or create duplicate identities when legacy attributes violate cloud requirements. Its relevance follows from the stated tenant facts, not just a generic security recommendation. Correct it by run IdFix and correct incompatible directory attributes at their on-premises authoritative source. Then verify: The pre-sync validation finds no blocking UPN or proxy-address defects in the approved user subset.
Incorrect Answers
Raw directory counts can differ by design because not every on-premises object should synchronize. The stated symptoms instead indicate that directory synchronization can fail or create duplicate identities when legacy attributes violate cloud requirements.
Ambiguous source anchor or account matching can create duplicates during hybrid identity onboarding. The stated symptoms instead indicate that directory synchronization can fail or create duplicate identities when legacy attributes violate cloud requirements.
Export cannot safely assign one proxy address to multiple different recipients. The stated symptoms instead indicate that directory synchronization can fail or create duplicate identities when legacy attributes violate cloud requirements.