Your company has an Azure environment with a hub virtual network named `vnet-hub-prod` () that contains a Virtual Network Gateway, and a spoke virtual network named `vnet-spoke-app` (). You configure Virtual Network Peering between `vnet-hub-prod` and `vnet-spoke-app`. You need to ensure that virtual machines in `vnet-spoke-app` can access your on-premises network through the gateway in `vnet-hub-prod`. Which two configuration settings should you select? (Select two.)
- On the peering configuration from vnet-hub-prod to vnet-spoke-app, select 'Use this virtual network's gateway or Route Server'.Cevap
- On the peering configuration from vnet-spoke-app to vnet-hub-prod, select 'Use the remote virtual network's gateway or Route Server'.Cevap
- CCreate a User Defined Route (UDR) in vnet-spoke-app that redirects the subnet's local traffic () to the gateway in vnet-hub-prod.
- DCreate a User Defined Route (UDR) in vnet-hub-prod that routes traffic destined for vnet-spoke-app () to the Virtual Network Gateway.
Cevap
On the peering configuration from vnet-hub-prod to vnet-spoke-app, select 'Use this virtual network's gateway or Route Server', and on the peering configuration from vnet-spoke-app to vnet-hub-prod, select 'Use the remote virtual network's gateway or Route Server'.
To enable gateway transit in Azure Virtual Network Peering, you must configure both ends of the peering connection. In the hub virtual network (which contains the gateway), the peering to the spoke must be configured with 'Use this virtual network's gateway or Route Server' to allow the gateway to be shared. In the spoke virtual network, the peering to the hub must be configured with 'Use the remote virtual network's gateway or Route Server' to route outbound traffic through the remote gateway.
Adım Adım Çözüm
Anahtar Kavram
Virtual Network Peering Gateway Transit allows peered virtual networks to share a VPN or ExpressRoute gateway, eliminating the need to deploy gateways in every spoke virtual network.
Tahmini Süre:1m 0s