Your network contains an on-premises Active Directory domain named corp.contoso.com. You have an Azure subscription named Sub1 that is associated to an Azure Active Directory (Azure AD) tenant named…

Question

Options

• ASynchronization Rules Editor
• BWeb Service Configuration Tool
• Cthe Azure AD Connect wizard
• DActive Directory Users and Computers

• A
  79% (15)
• B
  5% (1)
• C
  11% (2)
• D
  5% (1)

Explanation

Explanation

Synchronization Rules Editor is correct because it allows administrators to create custom inbound synchronization rules with scoping filters directly in Azure AD Connect - specifically, you can define attribute-based filters (e.g., givenName STARTSWITH "TEST") to exclude specific objects from syncing to Azure AD, which is precisely the requirement here with minimal administrative effort.

Option B (Web Service Configuration Tool) is incorrect because this tool is used to configure the Generic Web Service connector for non-standard LDAP/HR systems, not for filtering Azure AD Connect sync rules.

Option C (Azure AD Connect wizard) is incorrect because while the wizard handles domain/OU-level filtering, it does not support granular attribute-based filtering like filtering by a specific value of givenName - that level of customization requires the Synchronization Rules Editor.

Option D (Active Directory Users and Computers) is incorrect because this is simply an AD management tool for managing user objects and OUs on-premises; it has no functionality related to controlling Azure AD Connect synchronization behavior.

Memory Tip: Think of the Synchronization Rules Editor as the "fine-tuned filter" tool - whenever a question mentions filtering by a specific attribute value during sync, that's your signal to choose it over the basic Azure AD Connect wizard.

No community discussion yet for this question.