VNet-to-VNet connectivity in Azure - Time & Space Complexity

Time Complexity: VNet-to-VNet connectivity

O(n²)

Understanding Time Complexity

When connecting two virtual networks (VNets) in Azure, it's important to understand how the time to set up and maintain this connection changes as the number of VNets grows.

We want to know: how does the work increase when more VNets are connected?

Scenario Under Consideration

Analyze the time complexity of creating VNet-to-VNet connections using Azure PowerShell.

# Connect multiple VNets by creating peerings
foreach ($vnet1 in $vnets) {
  foreach ($vnet2 in $vnets) {
    if ($vnet1 -ne $vnet2) {
      New-AzVirtualNetworkPeering -Name "$($vnet1.Name)-to-$($vnet2.Name)" `
        -VirtualNetwork $vnet1 -RemoteVirtualNetworkId $vnet2.Id -AllowForwardedTraffic
    }
  }
}

This script creates peering connections between every pair of VNets in a list.

Identify Repeating Operations

We look for the main repeated actions:

• Primary operation: Creating a peering connection between two VNets using New-AzVirtualNetworkPeering.
• How many times: For each VNet, a peering is created with every other VNet, so the number of peerings grows with the square of the number of VNets.

How Execution Grows With Input

As the number of VNets increases, the number of peering connections grows quickly because each VNet connects to all others.

Input Size (n)	Approx. Api Calls/Operations
10	90
100	9,900
1000	999,000

Pattern observation: The number of operations grows roughly by the square of the number of VNets.

Final Time Complexity

Time Complexity: O(n²)

This means that if you double the number of VNets, the number of peering connections roughly quadruples, so the work grows fast as you add more VNets.

Common Mistake

[X] Wrong: "Adding more VNets only increases the number of connections a little bit because each VNet connects to just one other."

[OK] Correct: Each VNet connects to every other VNet, so the total connections grow much faster, not just by one per new VNet.

Interview Connect

Understanding how connection counts grow helps you design scalable network setups and shows you can think about how cloud resources behave as systems grow.

Self-Check

What if we only connected each VNet to a fixed number of other VNets instead of all? How would the time complexity change?

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