Azure Route Table Association Scope

Configure and manage virtual networks in Azure
Answer Correct answer: B — An Azure route table can only be directly associated with a subnet, not a VNet or NIC.

You have an Azure subscription that contains the resources shown in the following table. You create a route table named RT1 in the East US Azure region. To which resources can you associate RT1? - image

  1. VNet1 only
  2. Subnet1 only Correct Answer
  3. VNet1 and NIC1 only
  4. Subnet1 and NIC1 only
  5. VNet1, Subnet1, and NIC1

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

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.

Many candidates incorrectly select VNet1 because they confuse route tables with Network Security Groups (NSGs), which can be associated with both subnets and NICs.

Community Discussion (3 comments)

Henrytml 👍 10
answer 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
Sandipmcr 👍 1 Selected: B
No, 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.
arunyadav09 👍 3
Given 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

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

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

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.

Related Analysis

Note: This question is part of a series of questions that pr

S-Grade

You have a Microsoft Entra tenant named contoso.com. You col

A-Grade

You have an Azure subscription that contains a storage accou

A-Grade

Practice All AZ-104 Questions

Access 100 questions with complete answers and detailed explanations.

View Full AZ-104 Practice Test →

← Back to AZ-104 Study Guide