MS-102 · Question #40
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 B. No. When specific accounts in an OU fail to sync while others succeed, and Azure AD Connect Health shows no errors, the root cause is typically an attribute-level issue (such as duplicate or invalid attributes like proxyAddresses, userPrincipalName, or mail) on those specific user…
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: You run idfix.exe and export the 10 user accounts. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(24 responses)- A29% (7)
- B71% (17)
Explanation
When specific accounts in an OU fail to sync while others succeed, and Azure AD Connect Health shows no errors, the root cause is typically an attribute-level issue (such as duplicate or invalid attributes like proxyAddresses, userPrincipalName, or mail) on those specific user objects - not an OU filtering or service health problem. The proposed solution in this question (likely modifying the synchronization schedule, restarting the sync service, or adjusting an unrelated setting) does not address the per-object attribute conflict that is causing the selective sync failure. To resolve this, you would use the IdFix tool to identify and fix invalid attributes on the 10 affected accounts.
Topics
Community Discussion
No community discussion yet for this question.