Your company has an Azure environment with a hub virtual network named `vnet-hub-core` () and a spoke virtual network named `vnet-prod-spoke` (). The virtual networks are peered. A firewall is deployed in the hub virtual network with the private IP address . You are configuring a route table for the subnets in `vnet-prod-spoke` to ensure all internet-bound traffic is routed through the firewall in the hub. Which route should you add to the route table to meet this requirement without breaking local communication within the spoke virtual network?
- A route with address prefix , next hop type Virtual appliance, and next hop IP address Answer
- BA route with address prefix , next hop type Virtual appliance, and next hop IP address
- CA route with address prefix , next hop type Virtual appliance, and next hop IP address
- DA route with address prefix , next hop type Virtual network gateway, and next hop IP address
Answer
A route with address prefix , next hop type Virtual appliance, and next hop IP address
The correct option is the route with address prefix , next hop type Virtual appliance, and next hop IP address . This configuration directs all traffic destined for the internet through the Azure Firewall in the hub virtual network. Because Azure uses Longest Prefix Match (LPM), the default local system route for the spoke () will take precedence for internal traffic, leaving local subnet-to-subnet communication intact.
Step-by-Step Solution
Key Concept
Azure User-Defined Routes (UDR) and Longest Prefix Match (LPM) routing rules.