-
Hi Roland,
You are right that in Azure, any VNet can always route traffic within itself. For example, resources inside TDVnet3 can naturally communicate with each other without additional configuration. That’s the default behavior and doesn’t depend on peering.
However, the key to this exam scenario lies in the peering configuration shown:
-
TDVnet1 ↔ TDVnet2: directly peered.
-
TDVnet1 ↔ TDVnet3: directly peered.
-
TDVnet2 ↔ TDVnet3: not peered.
-
Gateway transit is disabled, so TDVnet1 cannot act as a router to forward traffic between TDVnet2 and TDVnet3.
From this setup, here’s what it means for routing:
-
TDVnet1 has direct connections to both TDVnet2 and TDVnet3, so it can send packets to either.
-
TDVnet3 has a direct connection only to TDVnet1, so packets from TDVnet3 can only go to TDVnet1.
-
TDVnet3 cannot reach TDVnet2, because peering in Azure is non-transitive — traffic can’t flow through TDVnet1 as a “bridge.”
So, while technically TDVnet3 can route traffic to itself, the exam question is focused on cross-VNet routing, where self-routing is assumed and not listed in the answer choices.
That’s why the correct answer for the question is:
-
TDVnet1 packets can be routed to: TDVnet2 and TDVnet3
-
TDVnet3 packets can be routed to: TDVnet1 only
Hope this clears up any confusion you have. If you need further assistance, please don’t hesitate to contact us.
Best regards,
Nikee @ Tutorials Dojo
-
