AZ-500 · Question #64
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. Why B (No) is Correct: Deploying Azure AD DS alone does not meet the goal because Azure AD DS is a managed domain service that creates a new, separate domain in Azure - it does not extend or integrate directly with your on-premises Active Directory identities in a way that…
Question
Options
- AYes
- BNo
How the community answered
(58 responses)- A16% (9)
- B84% (49)
Explanation
Why B (No) is Correct: Deploying Azure AD DS alone does not meet the goal because Azure AD DS is a managed domain service that creates a new, separate domain in Azure - it does not extend or integrate directly with your on-premises Active Directory identities in a way that enables seamless on-premises credential authentication to HDInsight. For HDInsight to authenticate users using on-premises AD credentials in a hybrid scenario, you need to configure Azure AD Connect to sync on-premises identities to Azure AD, and then use Azure AD DS with a trust relationship, or more correctly, deploy HDInsight with Enterprise Security Package (ESP) joined directly to the on-premises AD domain using a site-to-site VPN or ExpressRoute connection.
Why A (Yes) is Wrong: Simply deploying Azure AD DS is insufficient on its own - it doesn't bridge on-premises Active Directory credentials to HDInsight without additional configuration steps, such as ensuring proper network connectivity (VPN/ExpressRoute) and identity synchronization via Azure AD Connect.
Memory Tip: Think of Azure AD DS as a cloud copy of a domain, not a bridge to your on-premises domain. For true hybrid authentication to HDInsight, remember the full chain: on-premises AD → Azure AD Connect → Azure AD → Azure AD DS + ESP + network connectivity.
Topics
Community Discussion
No community discussion yet for this question.