Question 900
On-premises accounts use UPN suffixes that are not verified in the target Entra tenant. Select the acceptance test result that proves the intended behavior.
Explanation
Correct Answer
This result proves the intended change: synced users receive the approved verified UPN domain. The technical reason is Nonverified sign-in suffixes can cause unintended cloud sign-in identifiers.
Incorrect Answers
“The preflight reports no blocking name collisions” verifies the separate situation “An old directory contains accounts with corrupt duplicate mailNickname assignments”. The technical basis is: Bad source attributes can produce export errors or misrouted addresses. Here the required result is “Synced users receive the approved verified UPN domain”; the alternate check alone cannot establish it.
That outcome relates to a hybrid identity project finds two users with the same proxyAddresses attribute before directory synchronization., where Attribute uniqueness is required for reliable synchronization into Entra ID. The current requirement is only established by synced users receive the approved verified UPN domain.
“Users sign in with expected routable cloud identifiers” verifies the separate situation “An organization discovers that some accounts have no routable UPN suffix for cloud sign-in”. The technical basis is: Appropriate sign-in names reduce identity mismatches during hybrid enrollment. Here the required result is “Synced users receive the approved verified UPN domain”; the alternate check alone cannot establish it.