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.
You have a hybrid configuration of Azure Active Directory (Azure AD).
You have an Azure HDInsight cluster on a virtual network.
You plan to allow users to authenticate to the cluster by using their on-premises Active Directory credentials.
You need to configure the environment to support the planned authentication.
Solution: You deploy the On-premises data gateway to the on-premises network.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.B
Instead, you connect HDInsight to your on-premises network by using Azure Virtual Networks and a VPN gateway.
Note: To allow HDInsight and resources in the joined network to communicate by name, you must perform the following actions:
-> Create Azure Virtual Network.
-> Create a custom DNS server in the Azure Virtual Network.
-> Configure the virtual network to use the custom DNS server instead of the default Azure Recursive Resolver.
-> Configure forwarding between the custom DNS server and your on-premises DNS server.
https://docs.microsoft.com/en-us/azure/hdinsight/connect-on-premises-networkThe solution provided of deploying the On-premises data gateway to the on-premises network can potentially meet the goal of allowing users to authenticate to the Azure HDInsight cluster using their on-premises Active Directory credentials, but it is not sufficient on its own.
The On-premises data gateway is a component that enables communication between on-premises data sources and cloud services like Azure HDInsight. It acts as a bridge between the on-premises network and the cloud service by securely transmitting data between the two environments.
However, to enable authentication using on-premises Active Directory credentials, additional configuration is required on both the on-premises network and the Azure HDInsight cluster.
On the on-premises network, you need to configure Azure AD Connect to synchronize user accounts and passwords from the on-premises Active Directory to Azure AD. This allows users to use their on-premises Active Directory credentials to authenticate to Azure services, including the Azure HDInsight cluster.
On the Azure HDInsight cluster, you need to configure Azure AD authentication to enable users to authenticate using their Azure AD credentials. You can configure the cluster to use Azure AD as the identity provider and allow users to authenticate using their Azure AD credentials. Alternatively, you can configure the cluster to use hybrid authentication, where users can authenticate using either their on-premises Active Directory or Azure AD credentials.
Therefore, the solution provided of deploying the On-premises data gateway to the on-premises network can potentially be part of the overall solution, but it is not sufficient on its own to meet the goal of allowing users to authenticate to the Azure HDInsight cluster using their on-premises Active Directory credentials. Additional configuration is required on both the on-premises network and the Azure HDInsight cluster to enable this.