A company runs a network architecture in Microsoft Azure. The layout consists of a virtual network named `VNet-Corp` () with three subnets: `Subnet-App` (), `Subnet-Db` (), and `Subnet-NVA` (). A firewall appliance named `NVA1` is placed in `Subnet-NVA` with a private IP address of .
You must ensure that all network packets originating from the application tier (`Subnet-App`) and destined for the database tier (`Subnet-Db`) are inspected by `NVA1`.
Which two actions should you perform? (Each correct answer presents part of the solution.)
- Enable IP forwarding on the network interface of `NVA1`.Answer
- Create a route table, add a route for destination with a next hop type of Virtual appliance and IP address , and associate the route table with `Subnet-App`.Answer
- CCreate a route table, add a route for destination with a next hop type of Virtual network gateway and IP address , and associate the route table with `Subnet-App`.
- DConfigure a virtual network peering link directly between `Subnet-App` and `Subnet-Db` and enable gateway transit.
Answer
Enable IP forwarding on the network interface of `NVA1`, and create a route table containing a route for destination with a next hop type of Virtual appliance and IP address , then associate the route table with `Subnet-App`.
To route traffic from a subnet through a Network Virtual Appliance (NVA), you must create a route table with a User-Defined Route (UDR) pointing to the NVA's IP address. The next hop type must be set to 'Virtual appliance' to ensure Azure correctly forwards the packets to the NVA's private IP. Additionally, because the NVA will receive traffic destined for a different IP address (the database subnet), you must enable IP forwarding on the NVA's network interface (NIC) so that the operating system inside the NVA can forward the traffic to its final destination rather than dropping it.
Step-by-Step Solution
Key Concept
Configuring user-defined routes to redirect subnet traffic through a network virtual appliance, requiring both a route table entry and IP forwarding enablement on the appliance's network interface.
Estimated Time:2m 0s