A financial organization is deploying a hybrid network architecture. A central virtual network named `vnet-transit-hub` () connects to the company's on-premises datacenter through an Azure ExpressRoute gateway. To support dynamic routing, the organization deploys a third-party Network Virtual Appliance (NVA) in `vnet-transit-hub` within a subnet named `snet-nva` (). An Azure Route Server is deployed in the mandatory `RouteServerSubnet` () to exchange routing information.
The organization needs to ensure that the NVA and the on-premises datacenter can dynamically exchange routing information through BGP without maintaining manual static routes.
Which design action must be taken to support this routing requirement?
- AConfigure BGP peering between the Network Virtual Appliance (NVA) and the Azure Route Server, and associate a User Defined Route (UDR) with the RouteServerSubnet to redirect on-premises traffic to the NVA.
- BEstablish a direct BGP session from the on-premises router to the Network Virtual Appliance (NVA) by configuring individual IP rules for BGP port 179 within the Network Security Group on the RouteServerSubnet.
- Configure BGP peering between the Network Virtual Appliance (NVA) and the Azure Route Server, and enable the branch-to-branch setting on the Azure Route Server.Cevap
- DDeploy a Basic Load Balancer in front of the Network Virtual Appliance (NVA) to distribute the BGP peer traffic originating from the Azure Route Server's dual instances.
Cevap
Configure BGP peering between the Network Virtual Appliance (NVA) and the Azure Route Server, and enable the branch-to-branch setting on the Azure Route Server.
To exchange routes dynamically, BGP peering must be configured between the Route Server and the NVA. In addition, the branch-to-branch (Route-to-Route) setting on the Azure Route Server must be enabled to allow it to propagate routes between the ExpressRoute gateway and the NVA.
Adım Adım Çözüm
Anahtar Kavram
Azure Route Server enables dynamic route propagation between NVAs and virtual network gateways. Peering the NVA with the Route Server and enabling branch-to-branch connectivity are required to allow transit routing.
Alternatif Yöntem
Instead of using Azure Route Server, you could configure static routes (UDRs) in every spoke VNet pointing to the NVA's IP address. However, this is not dynamic and does not scale well as the network grows, making Route Server the optimal design choice.
Tahmini Süre:1m 30s