Study guide
7.4 User-Defined Routes and Effective Routes
AZ-104 Microsoft Azure Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation and Microsoft Learn Source Control
1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log
2 Chapter 2: Identity, RBAC, and Governance Foundations
2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab
3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization
3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab
4 Chapter 4: Storage Accounts, Access, and Data Protection
4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab
5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep
5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab
6 Chapter 6: Containers, App Service, and Platform Compute
6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab
7 Chapter 7: Virtual Networking, Routing, and Secure Access
7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab
8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting
8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab
9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery
9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab
10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs
10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab
11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path
11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths
7.4 User-Defined Routes and Effective Routes
Key Takeaways Explain This Topic AI
Azure creates system routes automatically, while user-defined routes override or refine paths for traffic that must use firewalls, NVAs, or forced tunneling.
Route selection depends on longest prefix match and next hop type, so a more specific route can change traffic even when a broader default route exists.
Effective routes on a NIC show the actual route set after system routes, peering, gateway propagation, and route table associations are considered.
UDRs must be paired with return path planning, NSG rules, firewall policy, and correct IP forwarding on NVAs.
AZ-104 routing questions often describe symptoms where the correct action is to inspect next hop or effective routes before changing security rules.
Last updated: May 2026
System routes versus UDRs
Azure automatically creates system routes for each subnet. Those routes let resources reach addresses in the VNet, peered VNets, the internet when allowed, and connected networks through gateways when configured. A user-defined route, or UDR, is an administrator-created route in a route table associated with a subnet. UDRs are used when the default path is not the required path.
Common UDR reasons include sending all outbound internet traffic to Azure Firewall, routing spoke-to-spoke traffic through a hub NVA, forcing traffic to on-premises, or overriding a learned route with a more specific path. UDRs are subnet-level controls. You do not attach a route table directly to a VM NIC in the usual AZ-104 workflow.
Route table example:
Address prefix Next hop type Next hop address Meaning
0.0.0.0/0 Virtual appliance 10.0.1.4 Send default traffic to firewall.
10.42.0.0/16 Virtual appliance 10.0.1.4 Send data spoke traffic to firewall.
172.20.0.0/16 Virtual network gateway None Send corporate traffic to VPN gateway.
10.41.0.0/16 Virtual network None Keep local VNet traffic local when needed.
Longest prefix match
Azure route selection follows longest prefix match. The route with the most specific matching prefix wins. A route for 10.42.1.0/24 is more specific than 10.42.0.0/16 , and both are more specific than 0.0.0.0/0 . This matters when a default route sends internet traffic to a firewall but a specific route sends storage traffic, partner traffic, or another spoke prefix somewhere else.
Example: Destination: 10.42.1.25
Routes:
- 0.0.0.0/0 -> firewall
- 10.42.0.0/16 -> peering
- 10.42.1.0/24 -> virtual appliance 10.0.1.4
- Selected route: 10.42.1.0/24 -> virtual appliance
If a question says one subnet can reach a destination but another cannot, compare their route table associations and effective routes. Subnets in the same VNet can have different route tables. A single wrong association can make only one tier fail.
Next hop types
Recognize the next hop types by scenario. Virtual appliance is used for Azure Firewall or an NVA and requires a next hop private IP. Virtual network gateway sends traffic to a VPN or ExpressRoute gateway. Internet sends traffic to the internet path. Virtual network keeps traffic inside the VNet. None drops matching traffic.
A route to None is a deliberate blackhole. It can be useful for blocking a prefix, but on the exam it may appear as the reason a connection fails even though an NSG appears open. Security rules allow or deny after routing has a path; if the selected route is None , the packet is dropped by routing.
Effective routes and next hop tools
Effective routes are the administrator's evidence. They combine system routes, user-defined routes, propagated routes, and peering routes for a NIC. Portal path: Network interface > Effective routes . You can also reach related views from the VM networking blade.
Network Watcher next hop asks Azure what next hop would be used from a source VM to a destination IP. This is especially useful when you suspect forced tunneling, gateway propagation, or an unexpected UDR. It answers the routing question before you spend time editing NSGs.
- CLI examples: az network nic show-effective-route-table \
- -resource-group rg-network \
- -name nic-web-01 \
- -output table
- az network watcher show-next-hop \
- -resource-group rg-network \
- -vm vm-web-01 \
- -source-ip 10.41.1.4 \
- -dest-ip 10.42.1.10
- Forced tunneling and hub firewall routing
Forced tunneling sends broad traffic, often 0.0.0.0/0 , to a firewall, NVA, or gateway instead of the Azure internet path. In a hub-and-spoke design, workload subnets in spokes may have a UDR that points default traffic to Azure Firewall in the hub. The firewall then applies policy and sends allowed traffic onward.
- Diagram: spoke VM 10.41.1.4
- |
- UDR 0.0.0.0/0 -> 10.0.1.4
- |
- hub Azure Firewall 10.0.1.4
- |
- internet or on-premises depending on policy and routes
This design needs four things: the UDR on the source subnet, peering that permits the path, firewall policy that allows the flow, and return routing that brings replies back through a valid path. If any one is missing, the route table might look correct but the connection still fails.
Route propagation
When a virtual network gateway exists, routes can be propagated to subnets. Route table settings can disable BGP route propagation. In AZ-104 scenarios, a subnet may fail to reach on-premises because gateway-propagated routes are disabled or because a UDR sends traffic elsewhere. Conversely, a subnet may unexpectedly send traffic to on-premises because propagated routes exist and are more specific than a default route.
When troubleshooting hybrid traffic, compare the on-premises prefix route, default route, and any more specific UDR. Also confirm the on-premises network has a return route to the Azure prefix. Azure routing can be correct in one direction while the remote router drops the return path.
Routing workflow for the exam
Use this sequence under time pressure:
Identify source subnet, destination IP, and port.
Check whether the destination IP is private, public, peered, or on-premises.
Inspect effective routes on the source NIC.
Run next hop if available.
Confirm UDR association on the source subnet.
Check peering, gateway propagation, and NVA IP forwarding if a virtual appliance is involved.
Then inspect NSGs, firewall policy, and guest firewall.
Scenario traps
Do not solve every connectivity failure with an NSG rule. If routing sends the packet to None , a firewall, or the wrong gateway, an allow rule will not help. Do not add a default route to a firewall without ensuring the firewall can reach Azure platform dependencies or required update endpoints. Do not forget that an NVA must be configured to forward traffic, and its NIC settings and guest OS must support forwarding.
A classic case says a VM can reach another VM by private IP until a route table is associated with the subnet. That points to a UDR problem. Another says internet access stopped after a 0.0.0.0/0 route was added to a firewall. That points to firewall policy, firewall public IP, SNAT, or return path, not a missing public IP on every VM.