VNet-to-VNet connectivity in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Understanding VNet Peering Behavior

You have two Azure VNets in the same region. You create a VNet peering between them. What is the expected behavior regarding traffic flow?

A Traffic between VNets is routed privately within Azure backbone network.

B Traffic between VNets requires a VPN gateway to flow.

C Traffic between VNets is routed through the internet.

D Traffic between VNets is blocked by default even after peering.

💡 Hint

Think about how Azure handles peered VNets in the same region.

VNet peering connects VNets privately through Azure's backbone network, allowing direct traffic without going over the internet or requiring VPN gateways.

❓ Configuration

intermediate

Configuring VNet-to-VNet VPN Gateway Connection

You want to connect two VNets in different Azure regions using VPN gateways. Which configuration step is mandatory?

A Deploy VPN gateways in both VNets and create a connection between them.

B Create a VNet peering between the two VNets.

C Enable service endpoints on both VNets.

D Assign the same address space to both VNets.

💡 Hint

Consider how VNets in different regions connect securely.

To connect VNets in different regions, you must deploy VPN gateways in each VNet and create a VPN connection between them. VNet peering does not support cross-region connections without gateways.

❓ security

advanced

Security Implications of VNet Peering

After peering two VNets, which security control must you configure to restrict traffic between them?

A Service endpoints must be enabled.

B Azure Firewall must be disabled to allow traffic.

C Network Security Groups (NSGs) on subnets or NICs.

D VPN Gateway policies must be applied.

💡 Hint

Think about how to control traffic flow inside a VNet or between VNets.

NSGs control inbound and outbound traffic at subnet or NIC level, allowing you to restrict traffic between peered VNets. VPN Gateway policies and service endpoints do not control peering traffic.

❓ service_behavior

advanced

Effect of Address Space Overlap in VNet Peering

You attempt to peer two VNets that have overlapping IP address spaces. What will happen?

A Azure will automatically adjust address spaces to avoid conflict.

B Peering will succeed but traffic will be dropped.

C Peering will succeed and traffic routes normally.

D Peering will fail due to address space overlap.

💡 Hint

Consider Azure's validation rules for VNet peering.

Azure does not allow peering between VNets with overlapping IP address spaces. The peering creation will fail to prevent routing conflicts.

✅ Best Practice

expert

Optimizing Cross-Region VNet Connectivity

You have multiple VNets across different regions that need to communicate securely and with low latency. Which architecture is best?

A Use VNet peering between all VNets regardless of region.

B Use Azure Virtual WAN to connect VNets through a hub-and-spoke model.

C Deploy VPN gateways in each VNet and connect all via VPN tunnels.

D Connect VNets via public internet with IPsec tunnels.

💡 Hint

Think about scalable and performant multi-region connectivity solutions.

Azure Virtual WAN provides a managed hub-and-spoke architecture that optimizes connectivity between multiple VNets across regions with better performance and simplified management compared to individual VPN tunnels or peering.