AZ-140 · Question #239
Your on-premises network contains an Active Directory domain that syncs with a Microsoft Entra tenant. You have a new Azure virtual network named VNet1. You plan to implement an Azure Virtual…
The correct answer is B. a local network gateway D. a Site-to-site (IPSec) connection type E. a virtual network gateway. To connect Azure Virtual Desktop session hosts to an on-premises Active Directory domain, a Site-to-Site VPN is required, which involves configuring an Azure Virtual Network Gateway, a Local Network Gateway, and a Site-to-Site (IPSec) connection type.
Question
Your on-premises network contains an Active Directory domain that syncs with a Microsoft Entra tenant. You have a new Azure virtual network named VNet1. You plan to implement an Azure Virtual Desktop host pool named Pool1. The session hosts in Pool will be joined to the Active Directory domain. You need to recommend a networking solution for connectivity between Azure Virtual Desktop and the on-premises network. Which three resources should you include in the recommendation? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Options
- Aa public load balancer
- Ba local network gateway
- Ca VNet-to-VNet connection type
- Da Site-to-site (IPSec) connection type
- Ea virtual network gateway
- Fa public IP address for every session host
How the community answered
(39 responses)- A5% (2)
- B77% (30)
- C3% (1)
- F15% (6)
Why each option
To connect Azure Virtual Desktop session hosts to an on-premises Active Directory domain, a Site-to-Site VPN is required, which involves configuring an Azure Virtual Network Gateway, a Local Network Gateway, and a Site-to-Site (IPSec) connection type.
A public load balancer is not typically used for establishing connectivity between an Azure VNet and an on-premises network for Active Directory domain join.
A local network gateway in Azure represents the on-premises VPN device and its network, enabling Azure resources to connect to the on-premises environment.
A VNet-to-VNet connection type is used to connect two Azure virtual networks, not an Azure VNet to an on-premises network.
A Site-to-site (IPSec) connection type establishes a secure tunnel between an Azure virtual network gateway and an on-premises VPN device, allowing the Azure Virtual Desktop session hosts to communicate with the on-premises Active Directory.
An Azure virtual network gateway is required to establish a Site-to-Site VPN connection from the Azure virtual network to the on-premises network.
A public IP address for every session host is unnecessary and potentially insecure for connecting to an on-premises Active Directory domain, as the VPN tunnel handles private connectivity.
Concept tested: Azure Site-to-Site VPN for hybrid connectivity
Source: https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways
Topics
Community Discussion
No community discussion yet for this question.