Question 100
A synced employee's surname is correct in on-premises AD but repeatedly reverts after a cloud portal edit. What explains the behavior?
- Verify and configure the required domain suffix in Microsoft Entra ID
- Federated authentication
- The synchronized attribute is mastered in on-premises Active Directory
- Correct duplicate proxyAddresses in the source directory
Explanation
Correct Answer
C:Attributes synchronized from an authoritative on-premises source should generally be updated at that source. Direct cloud edits to managed attributes may be blocked or overwritten on subsequent synchronization.
Incorrect Answers
A:Although the option establishes an accepted sign-in domain namespace in the tenant, the actual requirement is making persistent changes to synchronized user attributes. The appropriate control keeps selected account attributes under on-premises source authority.
B:This delegates authentication to an external trusted identity provider, but it does not provide making persistent changes to synchronized user attributes; the necessary control instead keeps selected account attributes under on-premises source authority.
D:This choice resolves duplicate mail alias attributes in the authoritative directory. The scenario concerns making persistent changes to synchronized user attributes; the relevant function keeps selected account attributes under on-premises source authority.
Question 101
A hybrid identity administrator wants diagnostic information about whether the scheduled Connect Sync cycles are running successfully. Which operational source is appropriate?
- Connect Sync synchronization service operations and run history
- Cloud Sync provisioning agents using outbound connections
- Cloud Sync provisioning-agent service and connectivity
- Source object scope and filtering rules
Explanation
Correct Answer
A:The synchronization engine records connector activity, import and export runs, and resulting errors. Reviewing this history helps distinguish connector failures from a user-level sign-in policy problem.
Incorrect Answers
B:This setting communicates outward to cloud provisioning rather than accepting public inbound sync requests. The missing piece for investigating scheduled synchronization failures is a capability that records on-premises sync-engine operations and connector run results.
C:This feature brokers synchronization requests between Cloud Sync and local Active Directory. To handle investigating scheduled synchronization failures, use a feature that records on-premises sync-engine operations and connector run results.
D:That choice selects which directory objects are eligible for synchronization; it does not implement investigating scheduled synchronization failures. The relevant feature records on-premises sync-engine operations and connector run results.
Question 102
Cloud Sync stopped provisioning users after a server maintenance window. Which component should IT validate first?
- Verify and configure the required domain suffix in Microsoft Entra ID
- Accidental delete prevention threshold in Connect Sync
- Source object scope and filtering rules
- Cloud Sync provisioning-agent service and connectivity
Explanation
Correct Answer
D:Provisioning agents must be healthy and able to communicate with Microsoft's cloud orchestration service and the target directory. A stopped agent can interrupt sync even when the tenant's user licenses remain unchanged.
Incorrect Answers
A:It establishes an accepted sign-in domain namespace in the tenant; this does not accomplish diagnosing interrupted Cloud Sync agent processing. The relevant functionality brokers synchronization requests between Cloud Sync and local Active Directory.
B:The option blocks unusually large synchronized deletion exports, not the action specified. For diagnosing interrupted Cloud Sync agent processing, the needed service brokers synchronization requests between Cloud Sync and local Active Directory.
C:The alternative selects which directory objects are eligible for synchronization. By contrast, the requested outcome of diagnosing interrupted Cloud Sync agent processing needs a control that brokers synchronization requests between Cloud Sync and local Active Directory.
Question 103
A synchronized account is not appearing in Entra ID even though other accounts synchronize. What setting should the administrator examine?
- Cloud Sync provisioning-agent service and connectivity
- Source object scope and filtering rules
- Connect Sync synchronization service operations and run history
- Separate Cloud Sync agent deployments for disconnected forests
- Cloud Sync provisioning agents using outbound connections
Explanation
Correct Answer
B:Object and attribute filtering determine which source identities enter the provisioning pipeline. A single missing object can be excluded by OU, attribute, or group scope rather than indicating a general tenant outage.
Incorrect Answers
A:This feature brokers synchronization requests between Cloud Sync and local Active Directory. The distinct requirement—troubleshooting a selectively missing user—is met by a control that selects which directory objects are eligible for synchronization.
C:This records on-premises sync-engine operations and connector run results, but it does not provide troubleshooting a selectively missing user; the necessary control instead selects which directory objects are eligible for synchronization.
D:The described operation permits provisioning from independent forests through multiple agents. In contrast, troubleshooting a selectively missing user needs an approach that selects which directory objects are eligible for synchronization.
E:This operation communicates outward to cloud provisioning rather than accepting public inbound sync requests; the present scenario instead involves troubleshooting a selectively missing user. The fitting solution selects which directory objects are eligible for synchronization.
Question 104
Unexpected deletion operations are detected in Connect Sync after an OU is reorganized. Which guardrail should be checked before accepting the large delete export?
- Accidental delete prevention threshold in Connect Sync
- Source object scope and filtering rules
- Cloud Sync provisioning-agent service and connectivity
- The synchronized attribute is mastered in on-premises Active Directory
Explanation
Correct Answer
A:Accidental deletion protection can stop exports when pending deletions exceed a configured threshold. The administrator should diagnose scope changes rather than automatically increasing the threshold and allowing unintended deletes.
Incorrect Answers
B:That option selects which directory objects are eligible for synchronization, which serves a different purpose. The specified task, preventing an accidental mass cloud deletion, calls for functionality that blocks unusually large synchronized deletion exports.
C:The choice brokers synchronization requests between Cloud Sync and local Active Directory, but it is not enough for preventing an accidental mass cloud deletion. The correct type of configuration blocks unusually large synchronized deletion exports.
D:Although the option keeps selected account attributes under on-premises source authority, the actual requirement is preventing an accidental mass cloud deletion. The appropriate control blocks unusually large synchronized deletion exports.
Question 105
A company has no inbound firewall openings to its domain controllers but wants a lightweight hybrid provisioning service. Which design feature is particularly helpful?
- Cloud Sync provisioning logs
- Cloud Sync provisioning agents using outbound connections
- Separate Cloud Sync agent deployments for disconnected forests
- Cloud Sync attribute mappings and transformations
Explanation
Correct Answer
B:The Cloud Sync agent initiates outbound connections to Microsoft services, avoiding the need for inbound internet access to on-premises AD. Agents still require directory access and supported network connectivity.
Incorrect Answers
A:The feature records Cloud Sync object-provisioning decisions and errors, a separate task from avoiding inbound firewall exposure for directory sync; the appropriate configuration communicates outward to cloud provisioning rather than accepting public inbound sync requests.
C:This choice permits provisioning from independent forests through multiple agents. The scenario concerns avoiding inbound firewall exposure for directory sync; the relevant function communicates outward to cloud provisioning rather than accepting public inbound sync requests.
D:This setting defines cloud-side attribute provisioning behavior for Cloud Sync. The missing piece for avoiding inbound firewall exposure for directory sync is a capability that communicates outward to cloud provisioning rather than accepting public inbound sync requests.
Question 106
An administrator needs to fine-tune attribute mapping for Cloud Sync under the supported cloud configuration model. Where should those mappings be managed?
- Separate Cloud Sync agent deployments for disconnected forests
- Source object scope and filtering rules
- Compare the official Cloud Sync and Connect Sync feature matrix
- Cloud Sync attribute mappings and transformations
Explanation
Correct Answer
D:Cloud Sync provisioning configuration includes supported attribute mappings and transformations managed through Entra administration. It is a different editing model from changing Connect Sync's synchronization-rule editor.
Incorrect Answers
A:The alternative permits provisioning from independent forests through multiple agents. For the scenario’s editing supported Cloud Sync attribute mappings goal, use a mechanism that defines cloud-side attribute provisioning behavior for Cloud Sync.
B:This feature selects which directory objects are eligible for synchronization. To handle editing supported Cloud Sync attribute mappings, use a feature that defines cloud-side attribute provisioning behavior for Cloud Sync.
C:That choice documents differences between the two hybrid sync architectures; it does not implement editing supported Cloud Sync attribute mappings. The relevant feature defines cloud-side attribute provisioning behavior for Cloud Sync.
Question 107
Before enabling a changed Microsoft Entra Cloud Sync configuration across its scoped directory population, an administrator wants to test how that configuration provisions one selected on-premises user. Which capability provides a targeted test?
- Cloud Sync Provision on demand for the selected user
- Activate the Connect Sync staging server to export every object
- Move the entire on-premises OU into the synchronization scope
- Clear all previous synchronization logs to trigger a full export
Explanation
Correct Answer
A:Cloud Sync offers Provision on demand, which tests a selected user's provisioning path under the chosen cloud synchronization configuration. It helps validate mapping and provisioning behavior before broad rollout.
Incorrect Answers
B:A staging-mode Connect Sync server is not the same engine as Cloud Sync and is intended for standby or validation of a different synchronization configuration. Activating it can initiate wider exports.
C:Changing the OU scope could add many identities to provisioning. It increases production impact instead of testing one account safely against the current configuration.
D:Deleting historical log records does not run a targeted provisioning request. It would remove troubleshooting evidence without confirming whether the new Cloud Sync mapping works.
Question 108
A deployment is migrating from Connect Sync to Cloud Sync; IT must verify that specialized synchronization requirements will still be supported. What should be done before switching engines?
- Separate Cloud Sync agent deployments for disconnected forests
- Cloud Sync attribute mappings and transformations
- Compare the official Cloud Sync and Connect Sync feature matrix
- Connect Sync synchronization service operations and run history
Explanation
Correct Answer
C:The official comparison identifies supported and unsupported scenarios and migration considerations. Choosing based solely on lighter agent footprint could remove a capability on which existing identity flows depend.
Incorrect Answers
A:This operation permits provisioning from independent forests through multiple agents; the present scenario instead involves validating feature parity before a migration. The fitting solution documents differences between the two hybrid sync architectures.
B:The feature defines cloud-side attribute provisioning behavior for Cloud Sync, a separate task from validating feature parity before a migration; the appropriate configuration documents differences between the two hybrid sync architectures.
D:That option records on-premises sync-engine operations and connector run results, which serves a different purpose. The specified task, validating feature parity before a migration, calls for functionality that documents differences between the two hybrid sync architectures.
Question 109
A new HR attribute is mapped from AD DS to Entra ID, but the exported value stays stale even though the object's password works. Which pipeline component should be inspected?
- Microsoft Entra Cloud Sync
- Supported directory synchronization for mail contacts
- Attribute mapping and export behavior
- Cloud Sync provisioning logs
Explanation
Correct Answer
C:Password authentication and directory attribute synchronization are separate concerns. The mappings and export state determine whether the changed attribute reaches the cloud object as intended.
Incorrect Answers
A:This synchronizes identities using lightweight agents and cloud orchestration, but it does not provide diagnosing a missing non-password attribute update; the necessary control instead moves supported source attribute values to their target cloud fields.
B:This option provisions supported mail contact objects from on-premises directory data; the task is diagnosing a missing non-password attribute update, which instead needs functionality that moves supported source attribute values to their target cloud fields.
D:The choice records Cloud Sync object-provisioning decisions and errors, but it is not enough for diagnosing a missing non-password attribute update. The correct type of configuration moves supported source attribute values to their target cloud fields.
Question 110
A synchronization engineer wants to separate directory connector errors from Cloud Sync sign-in authorization problems. Which diagnostic view should be used?
- Keep identity populations and sync responsibilities explicitly scoped
- Compare the official Cloud Sync and Connect Sync feature matrix
- Supported directory synchronization for mail contacts
- Cloud Sync provisioning logs
Explanation
Correct Answer
D:Provisioning logs record cloud-orchestrated identity provisioning activity and failures. They help identify per-object synchronization issues instead of simply reporting whether a user can sign in.
Incorrect Answers
A:Although the option assigns each source population to a clearly managed provisioning path, the actual requirement is tracing failed cloud provisioning operations. The appropriate control records Cloud Sync object-provisioning decisions and errors.
B:This choice documents differences between the two hybrid sync architectures. The scenario concerns tracing failed cloud provisioning operations; the relevant function records Cloud Sync object-provisioning decisions and errors.
C:This setting provisions supported mail contact objects from on-premises directory data. The missing piece for tracing failed cloud provisioning operations is a capability that records Cloud Sync object-provisioning decisions and errors.