An enterprise environment uses a hub-and-spoke topology. The hub virtual network is `vnet-hub-prod` (address space ) and hosts a network virtual appliance (NVA) at . Two spoke virtual networks are peered only to the hub: `vnet-spoke-web` (address space ) and `vnet-spoke-data` (address space ). You need to route all traffic between the two spokes through the NVA without overriding the default routing for communication within each spoke's own address space. Which two configurations should you implement?
- In the route table associated with the subnets in `vnet-spoke-web`, add a route for with a next hop of Virtual Appliance at .Answer
- In the route table associated with the subnets in `vnet-spoke-data`, add a route for with a next hop of Virtual Appliance at .Answer
- CIn the route table associated with the subnets in `vnet-spoke-web`, add a route for with a next hop of Virtual Appliance at .
- DIn the route table associated with the subnets in `vnet-spoke-data`, add a route for with a next hop of Virtual Appliance at .
Answer
To route inter-spoke traffic through the NVA, you must add a route for the remote spoke's address prefix ( in the web spoke, and in the data spoke) with a next hop pointing to the NVA's IP address. You must avoid creating user-defined routes for a spoke's own local address prefix, as doing so overrides the default system route for the local virtual network and disrupts internal communication.
To route transit traffic between the two spoke virtual networks through the NVA, you must define routes for the non-local spoke prefixes. Thus, the route table for the web spoke needs a route for the database spoke prefix (), and the route table for the database spoke needs a route for the web spoke prefix (). Both routes must point to the NVA's IP address at . This setup ensures that inter-spoke traffic is routed through the NVA, while local traffic within each spoke is handled by the default system route.
Step-by-Step Solution
Key Concept
User-Defined Routes and Default System Route Overrides