Giving Cloud Sync the traits of Connect Sync
The wrong answers lend Microsoft Entra Cloud Sync features that belong to Microsoft Entra Connect Sync: a 30-minute scheduler, staging mode, device writeback and an external SQL Server. Cloud Sync runs on a cloud-managed scheduler that synchronises every two minutes, and its configuration is managed in the Microsoft Entra admin center. It gets high availability from additional active provisioning agents on different servers, which fail over automatically.
See it in a sample questionMisreading how Conditional Access policies apply
The wrong answers misjudge how Conditional Access policies apply. Options pick one policy by creation order or a numeric priority, have a report-only policy prompt or warn users, or let a Disabled per-user MFA state exempt a user. Conditional Access has no priority field: when one policy requires MFA and another requires a compliant device, the user must satisfy both. Report-only policies run Phase 1 and log the outcome, but Phase 2 enforcement does not affect the user. Policies are enforced after first-factor authentication, so per-user MFA state does not gate them.
See it in a sample questionConfiguring an authentication method in the wrong place
The wrong answers move a method's settings to a control that does not own them: Conditional Access, the legacy MFA service settings or per-user MFA. In the Authentication methods policy, each method has an Enable and Target tab that can include a specific group, and each target can pick its own authentication mode, such as Any for a passwordless group and Push for All users. Microsoft Authenticator OTP has its own control, not the hardware or third-party OATH sections.
See it in a sample questionBlurring pass-through authentication and hash sync
The wrong answers merge pass-through authentication (PTA) with password hash synchronisation (PHS). One has PHS silently rescue a sign-in when every PTA agent is offline; others have PTA store hashes in the cloud, need a paid edition or purge existing hashes. PTA does not fail over to PHS automatically. It forwards validation to on-premises domain controllers, needs no paid Microsoft Entra ID edition and leaves synced hashes in place.
See it in a sample questionMisplacing Password Protection components
The wrong answers misplace Microsoft Entra Password Protection components and misstate what happens when no policy is available. Options install the DC Agent on the Microsoft Entra Connect server, have domain controllers contact the internet, require schema changes, or have the agent reject password changes or shut itself down. The DC Agent runs on every domain controller and the Proxy service on any domain-joined server, forwarding policy downloads so domain controllers never reach the internet. With no policy available, the agent accepts the password and logs an event.
See it in a sample question