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.

Practice

1. What is the main purpose of VNet-to-VNet peering in Azure?

easy

A. To create a backup of a virtual network

B. To securely connect two virtual networks for resource sharing

C. To connect a virtual network to the internet

D. To increase the size of a single virtual network

Solution

1. Step 1: Understand VNet-to-VNet peering concept

   VNet-to-VNet peering connects two virtual networks securely to allow communication.

2. Step 2: Identify the purpose of peering

   It enables resource sharing between VNets without exposing them to the internet.

3. Final Answer:

   To securely connect two virtual networks for resource sharing -> Option B

4. Quick Check:

   VNet peering = secure VNet connection [OK]

Hint: Peering connects VNets securely, not to internet or backup [OK]

Common Mistakes:

• Confusing peering with internet connectivity
• Thinking peering increases VNet size
• Assuming peering creates backups

2. Which of the following is the correct way to establish VNet peering between two VNets in Azure?

easy

A. Create peering from VNet1 to VNet2 only

B. Create peering from VNet2 to VNet1 only

C. Create peering from both VNet1 to VNet2 and VNet2 to VNet1

D. No peering needed, VNets connect automatically

Solution

1. Step 1: Review peering setup requirements

   Peering must be created from both VNets to allow two-way communication.

2. Step 2: Identify correct peering configuration

   Only creating peering one way does not enable full connectivity.

3. Final Answer:

   Create peering from both VNet1 to VNet2 and VNet2 to VNet1 -> Option C

4. Quick Check:

   Two-way peering needed = Create peering from both VNet1 to VNet2 and VNet2 to VNet1 [OK]

Hint: Peering must be two-way for full VNet connectivity [OK]

Common Mistakes:

• Setting peering only one way
• Assuming VNets connect automatically
• Confusing peering with VPN gateways

3. Given two VNets, VNetA and VNetB, with peering configured correctly, what happens if you try to access a VM in VNetB from VNetA?

medium

A. The VM in VNetB is accessible as if on the same network

B. The VM in VNetB is blocked by default firewall rules

C. The VM in VNetB is unreachable without a VPN gateway

D. The VM in VNetB is accessible only via public IP

Solution

1. Step 1: Understand effect of correct VNet peering

   Peering allows VNets to communicate privately as if on the same network.

2. Step 2: Analyze access to VM in peered VNet

   VMs can be accessed using private IPs without VPN or public IP.

3. Final Answer:

   The VM in VNetB is accessible as if on the same network -> Option A

4. Quick Check:

   Peering enables private access = The VM in VNetB is accessible as if on the same network [OK]

Hint: Peered VNets act like one network for VM access [OK]

Common Mistakes:

• Thinking VPN gateway is always needed
• Assuming public IP is required
• Confusing firewall rules with peering

4. You set up VNet peering from VNet1 to VNet2 but cannot access resources in VNet2 from VNet1. What is the most likely cause?

medium

A. Peering was not created from VNet2 to VNet1

B. VNet1 and VNet2 have overlapping IP address ranges

C. Network Security Groups block traffic between VNets

D. All of the above

Solution

1. Step 1: Check peering configuration

   Peering must be created both ways; missing one side blocks communication.

2. Step 2: Verify IP address ranges and security rules

   Overlapping IPs cause routing conflicts; NSGs may block traffic.

3. Step 3: Combine all issues

   Any of these can cause access failure; all are common mistakes.

4. Final Answer:

   All of the above -> Option D

5. Quick Check:

   Multiple causes block access = All of the above [OK]

Hint: Check peering, IP ranges, and NSGs when access fails [OK]

Common Mistakes:

• Ignoring one-way peering setup
• Overlapping IP ranges unnoticed
• Not checking firewall or NSG rules

5. You have two VNets in different Azure regions that need to communicate privately. Which approach is best to enable this with minimal latency and no internet exposure?

hard

A. Use VNet-to-VNet peering with global peering enabled

B. Set up a VPN gateway connection between the VNets

C. Connect VNets via public IP addresses

D. Use ExpressRoute with public peering

Solution

1. Step 1: Identify connectivity options for cross-region VNets

   Global VNet peering allows private, low-latency connection between VNets in different regions.

2. Step 2: Compare alternatives

   VPN gateways add latency and complexity; public IPs expose traffic; ExpressRoute public peering is not private.

3. Step 3: Choose best practice

   Global VNet peering is recommended for private, fast cross-region VNet communication.

4. Final Answer:

   Use VNet-to-VNet peering with global peering enabled -> Option A

5. Quick Check:

   Global peering = private, low latency cross-region [OK]

Hint: Global peering connects regions privately with low latency [OK]

Common Mistakes:

• Using VPN gateways unnecessarily
• Exposing traffic via public IPs
• Confusing ExpressRoute public peering with private