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…

Question

Options

• AYes
• BNo

• A
  19% (6)
• B
  81% (25)

Explanation

Explanation

Option B (No) is correct because deploying the On-premises data gateway does not enable Active Directory authentication for HDInsight clusters - the data gateway is designed to facilitate data connectivity between cloud services (like Power BI or Azure Logic Apps) and on-premises data sources, not to handle identity authentication. To allow users to authenticate to an Azure HDInsight cluster using their on-premises Active Directory credentials in a hybrid setup, you need to configure Azure AD Domain Services (AAD DS) and set up the cluster as a domain-joined HDInsight cluster using the Enterprise Security Package (ESP). Additionally, Azure AD Connect must be in place to synchronize on-premises AD identities to Azure AD, enabling seamless authentication. Option A (Yes) is wrong because the On-premises data gateway simply has no role in Active Directory-based Kerberos/LDAP authentication for HDInsight.

Memory Tip:

Think of the On-premises data gateway = data pipe, not an identity bridge. Whenever a question involves authenticating users from on-premises AD to Azure services, think Azure AD Connect + Azure AD Domain Services, not the data gateway.

No community discussion yet for this question.