Why VNet peering for connectivity in Azure? - Purpose & Use Cases

The Big Idea

What if connecting your cloud networks was as easy as building a private road between two neighborhoods?

The Scenario

Imagine you have two separate neighborhoods (networks) in a city, and you want to build a private road between them so people can visit each other easily.

Without a direct road, people have to take long detours through public highways, which is slow and less secure.

The Problem

Manually connecting these neighborhoods means setting up complex gates, security checks, and routes that are hard to manage.

This process is slow, prone to mistakes, and can cause traffic jams or security leaks.

The Solution

VNet peering acts like building a private, secure road directly between the two neighborhoods.

This road is fast, simple to set up, and lets resources in both networks communicate as if they were in the same neighborhood.

Before vs After

✗ Before

Create VPN gateways and configure complex routing tables between VNets

✓ After

Use VNet peering to connect VNets directly with a few clicks or commands

What It Enables

It enables seamless, secure, and high-speed communication between different virtual networks without complicated setup.

Real Life Example

A company has separate VNets for development and production environments but needs them to share data securely and quickly.

Using VNet peering, they connect these VNets so their apps can talk to each other without delays or extra security risks.

Key Takeaways

Manual network connections are complex and error-prone.

VNet peering creates simple, direct, and secure links between virtual networks.

This improves speed, security, and ease of management.

Practice

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

easy

A. To connect two virtual networks for direct communication

B. To create a backup of virtual machines

C. To deploy applications faster

D. To monitor network traffic

Solution

1. Step 1: Understand VNet peering concept

   VNet peering allows two virtual networks to communicate directly without going through the internet.

2. Step 2: Identify the main use case

   This direct communication is the primary purpose, enabling resource sharing securely within Azure.

3. Final Answer:

   To connect two virtual networks for direct communication -> Option A

4. Quick Check:

   VNet peering = direct network connection [OK]

Hint: VNet peering links networks directly, not backups or monitoring [OK]

Common Mistakes:

• Confusing peering with VM backup
• Thinking peering speeds up app deployment
• Assuming peering is for traffic monitoring

2. Which of the following is the correct way to create a VNet peering in Azure Portal?

easy

A. Create a new VNet with peering enabled by default

B. Create peering from one VNet only

C. Create peering from both VNets involved

D. Enable peering in the subscription settings

Solution

1. Step 1: Review peering setup requirements

   VNet peering requires configuration from both virtual networks to allow full communication.

2. Step 2: Identify correct procedure

   Creating peering from both VNets ensures bidirectional connectivity and proper routing.

3. Final Answer:

   Create peering from both VNets involved -> Option C

4. Quick Check:

   Peering setup = both sides configured [OK]

Hint: Peering needs setup on both VNets, not just one [OK]

Common Mistakes:

• Configuring peering only on one VNet
• Assuming peering is automatic on new VNets
• Looking for peering in subscription settings

3. Given two VNets, VNetA and VNetB, peered correctly, what happens when a VM in VNetA tries to ping a VM in VNetB?

medium

A. The ping fails because VNets cannot communicate even if peered

B. The ping fails because peering blocks ICMP traffic

C. The ping succeeds only if both VMs are in the same subnet

D. The ping succeeds because peering allows direct communication

Solution

1. Step 1: Understand VNet peering behavior

   Peering connects VNets so resources can communicate directly, including ping (ICMP) traffic if allowed by NSGs.

2. Step 2: Analyze the ping scenario

   If no network security group blocks ICMP, ping from VM in VNetA to VM in VNetB will succeed due to peering.

3. Final Answer:

   The ping succeeds because peering allows direct communication -> Option D

4. Quick Check:

   Peering enables direct VM communication [OK]

Hint: Peering allows direct traffic unless blocked by security rules [OK]

Common Mistakes:

• Assuming peering blocks ping by default
• Thinking VMs must be in same subnet to communicate
• Believing peering does not enable VNet communication

4. You created VNet peering from VNetA to VNetB but forgot to create peering from VNetB to VNetA. What is the result?

medium

A. Full bidirectional communication between VNets

B. Unidirectional communication from VNetA to VNetB only

C. No communication between VNets

D. Peering automatically completes from both sides

Solution

1. Step 1: Understand peering directionality

   Peering must be created on both VNets for full bidirectional communication.

2. Step 2: Analyze partial peering effect

   With peering only from VNetA to VNetB, traffic flows from A to B but not from B to A.

3. Final Answer:

   Unidirectional communication from VNetA to VNetB only -> Option B

4. Quick Check:

   One-sided peering = one-way traffic [OK]

Hint: Peering one side = one-way connection only [OK]

Common Mistakes:

• Assuming peering is automatic both ways
• Expecting no communication at all
• Thinking peering creates full connection from one side

5. You have two VNets in different Azure regions and want to enable secure, low-latency communication between them. Which VNet peering type should you use?

hard

A. Global VNet peering

B. Local VNet peering

C. VPN Gateway peering

D. ExpressRoute peering

Solution

1. Step 1: Identify peering types and their use cases

   Local VNet peering works within the same region; global VNet peering connects VNets across regions.

2. Step 2: Choose peering for cross-region communication

   Global VNet peering enables secure, low-latency communication between VNets in different Azure regions.

3. Final Answer:

   Global VNet peering -> Option A

4. Quick Check:

   Cross-region VNet peering = global peering [OK]

Hint: Use global peering for cross-region VNet connection [OK]

Common Mistakes:

• Choosing local peering for different regions
• Confusing VPN Gateway with peering
• Selecting ExpressRoute which is for on-premises