Why Spoke Traffic Bypasses Azure Firewall: Route Table Not Associated
A company has deployed Azure Firewall in a hub virtual network with forced tunneling enabled. Spoke virtual networks are peered to the hub. The security team reports that outbound traffic from the spoke VMs is bypassing the firewall. What is the most likely reason?
Quick Answer
The answer is that the spoke subnets lack a route table with a default route (0.0.0.0/0) pointing to the Azure Firewall. This is the most likely reason because forced tunneling relies on a user-defined route (UDR) associated with the spoke’s subnet to redirect all outbound traffic to the firewall’s private IP; without that route table association, the spoke VMs will use the default internet path, bypassing the firewall entirely. On the AZ-500 exam, this scenario tests your understanding of how forced tunneling and route propagation interact in a hub-and-spoke topology—a common trap is assuming the hub’s route table alone controls spoke traffic, but each spoke subnet must have its own UDR. A simple memory tip: “No route, no firewall—spoke traffic goes straight to the wire.”
⚠ Common exam trap
Test-takers frequently assume forced tunneling on the firewall itself automatically redirects all spoke traffic, but in reality, forced tunneling only affects traffic from the firewall's own subnet; spoke subnets require explicit UDRs to route traffic to the firewall.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The spoke subnets do not have a route table with a default route (0.0.0.0/0) pointing to the Azure Firewall.
Forced tunneling on Azure Firewall requires that all outbound traffic from spoke VMs is routed to the firewall via a user-defined route (UDR) with a default route (0.0.0.0/0) pointing to the firewall's private IP as the next hop. Without this route, traffic from spoke subnets will use the default system route and bypass the firewall, even if the firewall itself is configured with forced tunneling.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The Azure Firewall policy has an allow-all network rule.
Why it's wrong here
Even with an allow-all rule, traffic must first be routed to the firewall.
- ✗
Azure Firewall is deployed in the same virtual network as the spoke VMs.
Why it's wrong here
The firewall is in the hub, not the spoke. If it were in the same VNet, it would still need UDRs.
- ✗
The spoke virtual networks are not peered to the hub.
Why it's wrong here
If not peered, traffic cannot reach the firewall. But the question says they are peered.
- ✓
The spoke subnets do not have a route table with a default route (0.0.0.0/0) pointing to the Azure Firewall.
Why this is correct
Without a UDR forcing traffic to the firewall, spoke VMs will use the default internet route, bypassing the firewall.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every AZ-500 question from scratch — 194 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on AZ-500
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company has a hub-spoke network topology with Azure Firewall deployed in the hub virtual network. Spoke virtual networks are peered to the hub. The security team needs to ensure that all outbound internet traffic from virtual machines in a spoke subnet goes through the Azure Firewall. They have configured a route table on the spoke subnet with a default route (0.0.0.0/0) pointing to the Azure Firewall private IP address. However, traffic from spoke VMs is still bypassing the firewall and going directly to the internet. What is the most likely reason?
hard- ✓ A.The route table is not associated with the spoke subnet.
- B.Azure Firewall is not configured with DNAT rules for outbound traffic.
- C.The spoke VNet peering does not allow gateway transit.
- D.The route table has a higher priority than system routes.
Why A: The most likely reason is that the route table containing the default route (0.0.0.0/0) pointing to the Azure Firewall private IP has not been associated with the spoke subnet. Without this association, the subnet continues to use system routes, which include a default route to the internet via the Azure default gateway, allowing traffic to bypass the firewall. Associating the route table with the subnet is a required step to override the system default route.
Variation 2. A company is designing a hub-spoke network topology with Azure Firewall in the hub virtual network. Spoke virtual networks are peered to the hub. They want to ensure that all outbound internet traffic from virtual machines in a spoke subnet goes through the Azure Firewall. They have configured a route table on the spoke subnet with a default route (0.0.0.0/0) pointing to the Azure Firewall's private IP address as the next hop. However, traffic is still bypassing the firewall. What is the most likely cause?
medium- A.The Azure Firewall is in a different region than the spoke VNet.
- ✓ B.The route table is not associated to the spoke subnet.
- C.The Azure Firewall does not have the correct network and application rules configured.
- D.The spoke VNet has the 'Use remote virtual network gateways' setting disabled.
Why B: The most likely cause is that the route table with the default route (0.0.0.0/0) pointing to the Azure Firewall's private IP has not been associated to the spoke subnet. Without this association, the route table is not applied to the subnet's traffic, so the default system route (which directs internet traffic directly to the internet) remains in effect, bypassing the firewall. Associating the route table to the subnet is a required step for user-defined routes (UDRs) to influence traffic flow.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-500 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-500 exam.