VNet peering for connectivity in Azure - Mini Project: Build & Apply

VNet Peering for Connectivity

📖 Scenario: You are setting up two virtual networks (VNets) in Azure for a company. These VNets need to communicate with each other securely and efficiently without going through the internet.To achieve this, you will create two VNets and then connect them using VNet peering.

🎯 Goal: Build two Azure VNets named VNetA and VNetB with specified address spaces, and configure VNet peering between them to enable direct connectivity.

📋 What You'll Learn

Create an Azure virtual network called VNetA with address space 10.0.0.0/16 in resource group ResourceGroup1.

Create an Azure virtual network called VNetB with address space 10.1.0.0/16 in resource group ResourceGroup1.

Create VNet peering from VNetA to VNetB with allowVirtualNetworkAccess enabled.

Create VNet peering from VNetB to VNetA with allowVirtualNetworkAccess enabled.

💡 Why This Matters

🌍 Real World

Companies often need to connect different parts of their cloud network securely. VNet peering allows this without exposing traffic to the internet.

💼 Career

Cloud engineers and network administrators use VNet peering to design scalable and secure network architectures in Azure.

1

Create the first virtual network VNetA

Create an Azure virtual network called VNetA with address space 10.0.0.0/16 in resource group ResourceGroup1. Use the Azure CLI command az network vnet create with the exact parameters.

Azure

# Your code here

Hint

Use az network vnet create with --resource-group, --name, and --address-prefix options.

2

Create the second virtual network VNetB

Create an Azure virtual network called VNetB with address space 10.1.0.0/16 in resource group ResourceGroup1. Use the Azure CLI command az network vnet create with the exact parameters.

Azure

az network vnet create --resource-group ResourceGroup1 --name VNetA --address-prefix 10.0.0.0/16 --location eastus
# Your code here

Hint

Repeat the az network vnet create command with the new name and address prefix.

3

Create VNet peering from VNetA to VNetB

Create a VNet peering connection from VNetA to VNetB in resource group ResourceGroup1. Use the Azure CLI command az network vnet peering create with --allow-vnet-access enabled.

Azure

az network vnet create --resource-group ResourceGroup1 --name VNetA --address-prefix 10.0.0.0/16 --location eastus
az network vnet create --resource-group ResourceGroup1 --name VNetB --address-prefix 10.1.0.0/16 --location eastus
# Your code here

Hint

Use az network vnet peering create with --vnet-name as VNetA and --remote-vnet as VNetB.

4

Create VNet peering from VNetB to VNetA

Create a VNet peering connection from VNetB to VNetA in resource group ResourceGroup1. Use the Azure CLI command az network vnet peering create with --allow-vnet-access enabled.

Azure

az network vnet create --resource-group ResourceGroup1 --name VNetA --address-prefix 10.0.0.0/16 --location eastus
az network vnet create --resource-group ResourceGroup1 --name VNetB --address-prefix 10.1.0.0/16 --location eastus
az network vnet peering create --resource-group ResourceGroup1 --name VNetA-to-VNetB --vnet-name VNetA --remote-vnet VNetB --allow-vnet-access
# Your code here

Hint

Repeat the peering creation with --vnet-name as VNetB and --remote-vnet as VNetA.

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