An enterprise is designing a hub-and-spoke network topology in Azure. The hub virtual network, `vnet-weur-hub` (), contains an ExpressRoute Gateway in `GatewaySubnet`, an Azure Route Server in `RouteServerSubnet` (), and a pair of active-passive Network Virtual Appliances (NVAs) in `NvaSubnet` (). The spoke virtual network, `vnet-weur-spoke-prod` (), is peered directly with the hub.
To implement security inspection, all egress traffic to the internet () from both the spoke and the hub must be routed through the NVA (). The NVA advertises the route to the Azure Route Server via BGP.
Which two configurations must you implement to ensure routing functions correctly without routing loops or unsupported configurations?
- Associate a route table to the `NvaSubnet` containing a User Defined Route (UDR) for with a next hop type of `Internet`.Cevap
- Configure the virtual network peering on `vnet-weur-spoke-prod` to use the remote virtual network's gateway or route server, and configure the peering on `vnet-weur-hub` to allow gateway transit.Cevap
- CAssociate a route table to the `RouteServerSubnet` containing a User Defined Route (UDR) for with the next hop set to the NVA's IP address ().
- DDisable BGP route propagation on the route table associated with the `NvaSubnet` to prevent the NVA from learning the default route advertised by the Route Server.
Cevap
Associate a User Defined Route (UDR) for pointing to the next hop type of `Internet` on the `NvaSubnet` route table, and configure the virtual network peering on `vnet-weur-spoke-prod` to use the remote gateway/route server while allowing gateway transit on the `vnet-weur-hub` peering.
When an NVA advertises a default route () via BGP to Azure Route Server, the Route Server propagates this default route to all subnets in the hub VNet and peered spoke VNets. To prevent a routing loop where the NVA forwards traffic back to itself, you must override the BGP route on the NVA's subnet by associating a UDR for with a next hop type of `Internet`. Additionally, for the spoke VNet to receive this dynamic default route from the Route Server in the hub VNet, the VNet peering must be configured to support gateway transit (allowing gateway transit on the hub VNet side and using the remote gateway or route server on the spoke VNet side).
Adım Adım Çözüm
Anahtar Kavram
Azure Route Server routing loop prevention and transit peering configuration.