Question 350
A proposed fix must be validated: An employee's cloud display name changes back after every directory synchronization run. Which acceptance check best demonstrates the outcome?
Explanation
Correct Answer
The new display name persists in Entra after the next successful sync. The case concerns correct a synced employee's display name at source: An employee's cloud display name changes back after every directory synchronization run. Hybrid identity attribute ownership determines where durable changes must be made. This answers the acceptance evidence for this change because it addresses the explicit constraint. The action being validated is: change the employee's displayName in the authoritative AD record and allow synchronization. The check must use the affected users, data, or devices.
Incorrect Answers
Directory normalization precedes reliable hybrid identity synchronization and reduces matching conflicts. The reason this does not settle the present case is the actual condition: Synced source-authoritative attributes should be updated in their on-premises directory source.
Synchronization filtering requires governance of the attributes used to decide inclusion. The current corrective requirement is: Change the employee's displayName in the authoritative AD record and allow synchronization.
Hybrid directory synchronization must enforce unique routable recipient identifiers. The appropriate acceptance check is: The new display name persists in Entra after the next successful sync.