Azure Route Table Association Scope
Short answer
B An Azure route table can only be directly associated with a subnet, not a VNet or NIC.
Question
Key Takeaways
Tests knowledge of Azure networking scope; the common trap is assuming route tables can be attached directly to VNets or NICs.
Determines the valid association targets for an Azure route table, establishing that subnets are the only direct association point.
Common mistake: Many candidates incorrectly select VNet1 because they confuse route tables with Network Security Groups (NSGs), which can be associated with both subnets and NICs.
Expert Analysis
Why the Answer Is Correct
In Azure, route tables must be associated with a subnet. When you associate a route table with a subnet, all network interfaces within that subnet inherit those routes. You cannot associate a route table directly with a Virtual Network (VNet) or a Network Interface Card (NIC). Therefore, RT1 can only be associated with Subnet1.Why the Other Options Are Wrong
Options involving VNet1 are incorrect because Azure does not support direct route table association at the VNet level; routing is enforced per-subnet. Options involving NIC1 are incorrect because while NSGs can be applied to NICs, route tables are strictly subnet-level objects. A NIC inherits its routing from the subnet it resides in, but it cannot host the route table itself.Community Comment Notes
The community consensus strongly supports the subnet-only association. As Henrytml noted, "You cannot directly associate a route table with a virtual network (VNet) or a network interface card (NIC)." Another user confirmed via official documentation that "Route tables are applied at the subnet level." This aligns with Microsoft's architecture where subnet-level policies govern traffic flow for contained resources.Official Reference
https://learn.microsoft.com/en-us/azure/virtual-network/manage-route-table
This link opens the official vendor documentation in a new tab.
Exam Strategy
Always distinguish between NSGs and Route Tables when reviewing association options. Remember: NSGs = Subnet OR NIC; Route Tables = Subnet ONLY.
Frequently Asked Questions
Why can't I attach a route table to a NIC?
Route tables define how traffic leaves a subnet. Since a NIC belongs to a specific subnet, it inherits the routes defined at the subnet level automatically.
Is this different from NSG associations?
Yes. NSGs can be applied to both subnets and individual NICs to filter traffic, whereas route tables are exclusively subnet-level objects for directing traffic paths.
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors, not of islever. The comments shown first are the most substantive of the thread — ranked by depth, community endorsement and relevance; expand the list below to read the rest.
From public community threads 3
-
Henrytml 👍 10answer is correct You cannot directly associate a route table with a virtual network (VNet) or a network interface card (NIC). Route tables are applied at the subnet level, and all resources within that subnet will follow the routes defined in the associated route table
-
arunyadav09 👍 3Given answer Subnet1 only is right. You can only associate a route table to subnets in virtual networks that exist in the same Azure location and subscription as the route table. https://learn.microsoft.com/en-us/azure/virtual-network/manage-route-table You can associate zero, or one, network security group to each subnet and network interface in a virtual machine. The same network security group can be associated to as many subnets and network interfaces as you choose. https://learn.microsoft.com/en-us/azure/virtual-network/network-security-group-how-it-works
-
Sandipmcr 👍 1 Answered BNo, you cannot directly assign a route table to a network interface (NIC) in Azure. Route tables in Azure are associated at the subnet level, not the NIC level. All network interfaces within a subnet inherit the routing rules defined by the route table associated with that subnet.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AZ-104 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-104 Practice Test →