MS-102 · Question #42
MS-102 Question #42: Real Exam Question with Answer & Explanation
The correct answer is B: No. A third proposed fix for the same scenario - 10 accounts in an OU not syncing despite Connect Health reporting no errors. The consistent pattern across questions 6, 7, and 8 (all answering No) indicates that the three proposed solutions all fail to address the actual cause. The c
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 the Synchronization Rules Editor, you create a new outbound synchronization rule. Does this meet the goal?
Options
- AYes
- BNo
Explanation
A third proposed fix for the same scenario - 10 accounts in an OU not syncing despite Connect Health reporting no errors. The consistent pattern across questions 6, 7, and 8 (all answering No) indicates that the three proposed solutions all fail to address the actual cause. The correct approach is to use the Microsoft IdFix DirSync Error Remediation Tool to scan the on-premises AD and identify specific attribute errors (such as duplicate UPNs, duplicate or invalid proxyAddresses, or illegal characters) on the 10 affected user objects. None of the three proposed solutions in this series correctly implements this fix.
Topics
Community Discussion
No community discussion yet for this question.