Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft Certified: Identity and Access Administrator Associate · Microsoft
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Why Option C is Correct Synchronization rules in Azure AD Connect define how objects and attributes flow between directories. There are two main types relevant here: Inbound synchronization rules: Apply to data flowing into the metaverse from a source connector. Outbound synchronization rules: Apply to data flowing out of the metaverse to a target connector (e.g., Azure AD). Since extensionAttribute15 is an on-premises Active Directory attribute, filtering must occur as early as possible—at the source. You achieve this by creating a higher-precedence inbound synchronization rule scoped to the Active Directory Domain Services (AD DS) connector.
signing in to the server running Microsoft Entra Connect Sync using an account that is a member of the ADSyncAdmins security group. Launch the Synchronization Rules Editor from the Start menu. In the editor, create an inbound synchronization rule to filter out (not synchronize) all users where extensionAttribute15 has the value NoSync. Apply the necessary filter conditions to exclude these users during synchronization 1.
C. Create an inbound synchronization rule for the Active Directory Domain Services connector. https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-configure-filtering#negative-filtering-do-not-sync-these