An enterprise deploys a hub-and-spoke virtual network topology in Azure. The Hub Virtual Network (vnet-hub-prod, CIDR: 10.200.0.0/16) contains a subnet (snet-hub-nva, CIDR: 10.200.1.0/24) that hosts a firewall Network Virtual Appliance (NVA) at IP address 10.200.1.4. The Spoke Virtual Network (vnet-spoke-app, CIDR: 10.201.0.0/16) contains a subnet (snet-app-prod, CIDR: 10.201.1.0/24) hosting application servers. The virtual networks are peered.
The enterprise has the following requirements:
1. All outbound internet traffic from snet-app-prod must be routed through the NVA at 10.200.1.4 for security inspection.
2. Application servers in snet-app-prod must communicate directly with database servers in another subnet (snet-app-db, CIDR: 10.201.2.0/24) within the same virtual network without traversing the NVA, to minimize latency.
3. Access to public Azure Key Vault instances must go directly over the Azure backbone network using service tags.
A junior administrator creates a custom Route Table, associates it with snet-app-prod, and defines the following user-defined routes (UDRs):
- Route 1: Address prefix 0.0.0.0/0 -> Next hop: Virtual appliance (10.200.1.4)
- Route 2: Address prefix 10.201.0.0/16 -> Next hop: Virtual appliance (10.200.1.4)
- Route 3: Address prefix AzureKeyVault (Service Tag) -> Next hop: Internet
Following this configuration, application servers in snet-app-prod lose all connectivity to database servers in snet-app-db.
Which modification to the Route Table will restore the required network connectivity?
- AChange the address prefix of Route 2 to 10.200.0.0/15 to cover all internal networks while leaving the local virtual network address space unaffected.
- BDelete Route 3 and configure individual Network Security Group rules with specific public IP addresses for each Azure Key Vault endpoint to allow direct outbound access.
- Delete Route 2 from the Route Table so that traffic within the virtual network is handled by the default system-defined local route.Answer
- DModify the next hop of Route 1 to point to the frontend private IP address of a Basic SKU Load Balancer that load balances a pool of network virtual appliances.