An enterprise has a hub-and-spoke virtual network topology in the West US 2 region. The hub virtual network, `vnet-usw2-hub` (), contains an Azure Route Server and a pair of active-active network virtual appliances (NVAs) in the subnet `snet-usw2-nva` (). The NVAs use BGP to peer with the Azure Route Server. The spoke virtual network, `vnet-usw2-spoke` (), contains a subnet named `snet-usw2-app` () and is peered with `vnet-usw2-hub` with gateway transit enabled.
Initially, the NVAs advertise the on-premises range via BGP. To force all on-premises traffic from `snet-usw2-app` through the NVAs, a route table is associated with `snet-usw2-app` containing a user-defined route (UDR) for with the next hop set to the NVAs' internal load balancer IP address ().
A new branch office is added on-premises, and the Virtual Network Gateway in `vnet-usw2-hub` dynamically learns the specific subnet route via ExpressRoute BGP propagation. Azure Route Server propagates this route to `vnet-usw2-spoke`. Security audits show that traffic from `snet-usw2-app` destined for the new branch () is bypassing the NVAs.
You need to ensure that traffic from `snet-usw2-app` to the new branch office is inspected by the NVAs.
What should you do?
- ADisable route propagation on the route table associated with `snet-usw2-app` and create a user-defined route for pointing to the Virtual Appliance IP address of .
- Add a user-defined route for with the next hop set to the Virtual Appliance IP address of in the route table associated with `snet-usw2-app`.Cevap
- CEnable the branch-to-branch routing setting on `vnet-usw2-hub`'s Azure Route Server.
- DModify the BGP community string on the NVAs to advertise with a higher Multi-Exit Discriminator (MED) attribute than the ExpressRoute gateway.