A company has two Azure virtual networks, VNet-A and VNet-B, connected via VNet peering. They want all traffic between the VNets to be inspected by a network virtual appliance (NVA) deployed in a subnet in VNet-A. They have configured a user-defined route (UDR) on the subnet in VNet-B that points the destination address space of VNet-A to the private IP of the NVA. However, traffic between the VNets is still not passing through the NVA. What is the most likely cause?
Answer choices
Why each option matters
Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.
Distractor review
The UDR is not associated with the subnet in VNet-B.
If the UDR were not associated, the traffic would follow default routes. The problem states they configured a UDR on the subnet, so association is assumed. This is not the most likely cause.
Best answer
The NVA's network interface (NIC) does not have IP forwarding enabled.
IP forwarding must be enabled on the NVA's NIC so that the NVA can accept packets not addressed to itself and forward them. This is a common configuration step that is often missed.
Distractor review
The VNet peering connection is not in a 'Connected' state.
If the peering were not connected, there would be no traffic at all. The traffic is flowing but not through the NVA, indicating peering is functional.
Distractor review
The NVA is deployed in the same subnet as the source VMs.
The NVA is in a subnet in VNet-A, and the UDR points to it. The location of the NVA relative to the source subnet does not affect the need for IP forwarding.
Common exam trap
Common exam trap: usable hosts are not the same as total addresses
Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.
Technical deep dive
How to think about this question
Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.
KKey Concepts to Remember
- CIDR notation defines the prefix length.
- Block size helps identify subnet boundaries.
- Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
- The required host count determines the smallest suitable subnet.
TExam Day Tips
- Write the block size before choosing the subnet.
- Check whether the question asks for hosts, subnets or a specific address range.
- Do not confuse /24, /25, /26 and /27 host counts.
Related practice questions
Related AZ-500 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
More questions from this exam
Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.
Question 1
A DevOps team wants Defender for Cloud to identify secrets exposed in GitHub repositories. What should be configured?
Question 2
A public web application should be protected from OWASP-style attacks and network-layer DDoS attacks. Which two Azure services are most relevant?
Question 3
A Sentinel scheduled rule runs every 5 minutes and looks back 1 hour. Analysts see repeated alerts for the same event. Which change best prevents duplicate detections without missing late-arriving logs?
Question 4
A SOC analyst needs a Sentinel query that detects multiple failed sign-ins followed by a successful sign-in for the same user. Which table is the best primary source?
Question 5
A Sentinel watchlist contains high-value administrator accounts. Which KQL pattern best uses it in a detection rule?
Question 6
A SOC wants a Sentinel rule to include account, host, and IP entities so analysts can pivot during investigation. What should be configured in the analytics rule?
FAQ
Questions learners often ask
What does this AZ-500 question test?
CIDR notation defines the prefix length.
What is the correct answer to this question?
The correct answer is: The NVA's network interface (NIC) does not have IP forwarding enabled. — When a UDR is used to route traffic to an NVA, the NVA's network interface must have IP forwarding enabled to receive traffic not destined to its own IP. Without IP forwarding, the NVA will drop the packets. The UDR itself has a higher priority than the system route for virtual network peering, so that is not the issue. The NVA must be configured as a router by enabling IP forwarding on its NIC.
What should I do if I get this AZ-500 question wrong?
Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.
Discussion
Sign in to join the discussion.