An enterprise is designing a high-availability hybrid network topology in Azure to support dynamic routing and traffic inspection. The design includes the following components:
* A hub virtual network named `vnet-hub-useast` () containing an Azure Route Server in the `RouteServerSubnet` () and two active-active Network Virtual Appliances (NVAs) in `subnet-nva` ().
* A spoke virtual network named `vnet-spoke-prod` () containing `subnet-web` ().
* A spoke virtual network named `vnet-spoke-data` () containing `subnet-db` ().
The NVAs establish BGP sessions with the Azure Route Server. The Route Server is configured with Branch-to-Branch enabled to exchange routes between the NVAs and an ExpressRoute Gateway in the hub.
You need to design a routing solution that meets the following requirements:
1. Subnets in `vnet-spoke-prod` and `vnet-spoke-data` must dynamically receive the on-premises routes advertised by the NVAs via BGP.
2. All spoke-to-spoke traffic (between `vnet-spoke-prod` and `vnet-spoke-data`) must be directed through the NVAs for security inspection.
3. Local traffic within `vnet-spoke-prod` (destined within ) must not be sent to the NVAs.
Which two configurations should you include in the design? (Select two.)
- Configure a User-Defined Route (UDR) on the route table for subnet-web with the address prefix and the next hop set to the internal load balancer IP of the NVAs.Cevap
- Configure virtual network peering between vnet-hub-useast and vnet-spoke-prod with 'Allow gateway transit' enabled on the hub side and 'Use the remote virtual network's gateway or Route Server' enabled on the spoke side.Cevap
- CConfigure a User-Defined Route (UDR) on the route table for subnet-web with the address prefix and the next hop set to the internal load balancer IP of the NVAs.
- DConfigure a User-Defined Route (UDR) on the route table for subnet-web with the address prefix and the next hop set to the internal load balancer IP of the NVAs.