MS-102 · Question #98
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is A. Yes. Modifying the filtering settings in Azure AD Connect is the correct fix because the clue is in the contradiction: Azure AD Connect Health reports all synchronizations completed successfully, yet 10 accounts are missing. This means the accounts aren't failing to sync - they're…
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. Your network contains an Active Directory domain. You deploy an Azure AD tenant. Another administrator configures the domain to synchronize to Azure AD. You discover that 10 user accounts in an organizational unit (OU) are NOT synchronized to Azure AD. All the other user accounts synchronized successfully. You review Azure AD Connect Health and discover that all the user account synchronizations completed successfully. You need to ensure that the 10 user accounts are synchronized to Azure AD. Solution: From Azure AD Connect, you modify the filtering settings. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(36 responses)- A78% (28)
- B22% (8)
Explanation
Modifying the filtering settings in Azure AD Connect is the correct fix because the clue is in the contradiction: Azure AD Connect Health reports all synchronizations completed successfully, yet 10 accounts are missing. This means the accounts aren't failing to sync - they're being excluded from sync scope entirely, which produces no error. Azure AD Connect's OU-based (or attribute-based) filtering controls which objects are in scope; if the OU containing those 10 accounts was excluded from the filter, they would silently never sync.
Why "No" is wrong: Some might think resetting/reinstalling Azure AD Connect or modifying the accounts themselves is needed, but those approaches address errors - not scope exclusions. Since Health reports success, there is no error to fix; the scope just needs to be widened.
Memory tip: Use the phrase "No error + missing objects = filtering problem." Whenever sync reports clean health but objects are absent, your first stop is always the filtering configuration in Azure AD Connect (accessible via the Azure AD Connect wizard → Customize synchronization options → Filter by domain and OU).
Topics
Community Discussion
No community discussion yet for this question.