Examkin

Soru

Zorluk: OrtaVirtual Network Connectivity and Routing

An organization is designing a hub-and-spoke virtual network topology in Azure. The hub virtual network, `vnet-neure-hub-01` (10.240.0.0/1610.240.0.0/16), contains an Azure Route Server in the `RouteServerSubnet` (10.240.2.0/2410.240.2.0/24) and a pair of Network Virtual Appliances (NVAs) in `snet-nva` (10.240.1.0/2410.240.1.0/24) that establish BGP sessions with the Route Server. The NVAs advertise on-premises network routes (192.168.0.0/16192.168.0.0/16). You peer a spoke virtual network named `vnet-neure-spoke-app` (10.241.0.0/2410.241.0.0/24) with `vnet-neure-hub-01`. You must ensure that virtual machines in `vnet-neure-spoke-app` can dynamically learn the routes advertised by the NVAs via Azure Route Server, without using User-Defined Routes (UDRs). Which two configurations should you implement?

  1. Configure the peering from `vnet-neure-spoke-app` to `vnet-neure-hub-01` to use the remote virtual network's gateway or Route Server.Cevap
  2. Configure the peering from `vnet-neure-hub-01` to `vnet-neure-spoke-app` to use this virtual network's gateway or Route Server.Cevap
  3. C
    Create a route table in `vnet-neure-spoke-app` with a route for 192.168.0.0/16192.168.0.0/16 pointing to the virtual IP of the Azure Route Server as the next hop.
  4. D
    Enable branch-to-branch transit in the Azure Route Server configuration.

Cevap

Configure the peering from `vnet-neure-spoke-app` to `vnet-neure-hub-01` to use the remote virtual network's gateway or Route Server, and configure the peering from `vnet-neure-hub-01` to `vnet-neure-spoke-app` to use this virtual network's gateway or Route Server.
The correct configurations involve enabling gateway and Route Server transit on both ends of the Virtual Network Peering. Specifically, you must configure the peering from the spoke VNet to the hub VNet to use the remote virtual network's gateway or Route Server, and configure the peering from the hub VNet to the spoke VNet to use this virtual network's gateway or Route Server. These settings allow the routing table of the spoke VNet to be dynamically updated with the BGP routes exchanged between the Route Server and the NVAs.

Adım Adım Çözüm

1
Analyze Azure Route Server routing requirements for spoke virtual networks.
Identify that spoke VNets peered with a hub VNet containing Azure Route Server do not automatically receive advertised BGP routes unless transit peering settings are enabled.
By default, Route Server does not propagate learned routes to spoke virtual networks unless transit routing settings are configured on the virtual network peering.
2
Configure the spoke-to-hub peering properties.
Enable 'Use the remote virtual network's gateway or Route Server' on the peering configuration from the spoke VNet to the hub VNet.
This allows the spoke VNet to consume the routing services provided by the Azure Route Server located in the peered hub VNet.
3
Configure the hub-to-spoke peering properties.
Enable 'Use this virtual network's gateway or Route Server' on the peering configuration from the hub VNet to the spoke VNet.
This grants permission for the hub VNet to propagate its gateway and Route Server routes to the peered spoke VNet.

Anahtar Kavram

Azure Route Server facilitates dynamic route exchange between NVAs and virtual networks using BGP. To allow peered spoke VNets to dynamically learn routes propagated by the Route Server in a hub VNet, transit options must be enabled on both sides of the VNet peering (specifically `useRemoteGateways` on the spoke side and `allowGatewayTransit` on the hub side).
Bu soruyu puanla

Konular

Virtual Network Connectivity and Routing

Bu konudan daha fazla soru