Learn the two crucial pieces of information needed to troubleshoot failing user object synchronization with Azure AD Connect’s built-in troubleshooting task. Ensure successful AD DS and Azure AD integration.
Table of Contents
Question
A company has an Azure Active Directory (Azure AD) tenant. The company deploys Azure AD Connect to synchronize users from an Active Directory Domain Services (AD DS).
The synchronization of a user object is failing.
You need to troubleshoot the failing synchronization by using a built-in Azure AD Connect troubleshooting task.
Which two pieces of information should you collect before you start troubleshooting? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Object common name
B. Object distinguished name
C. Azure AD connector name
D. AD connector name
E. Object globally unique identifier
Answer
B. Object distinguished name
E. Object globally unique identifier
Explanation
To troubleshoot a failing user object synchronization using Azure AD Connect’s built-in troubleshooting task, collect the object’s distinguished name (DN) and globally unique identifier (GUID). The DN uniquely identifies the object within the AD DS hierarchy, while the GUID is a unique identifier that remains constant across directory instances. These identifiers allow you to precisely locate the problematic object and investigate synchronization issues between AD DS and Azure AD. The other options, such as connector names and common name, are less specific and may not provide sufficient information for targeted troubleshooting.
Troubleshooting Microsoft Azure Connectivity AZ-720 certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Troubleshooting Microsoft Azure Connectivity AZ-720 exam and earn Troubleshooting Microsoft Azure Connectivity AZ-720 certification.