Question

Difficulty: EasyConfigure Virtual Network Peering

You have two Azure virtual networks named VNet1 and VNet2. VNet1 is configured with the address space 10.1.0.0/1610.1.0.0/16, and VNet2 is configured with the address space 10.1.100.0/2410.1.100.0/24. Is the statement true or false that you can configure virtual network peering between VNet1 and VNet2?

Answer: Answer

Answer

False
Virtual network peering cannot be established between virtual networks with overlapping IP address spaces. Because 10.1.100.0/2410.1.100.0/24 overlaps with 10.1.0.0/1610.1.0.0/16, Azure will block the creation of the peering connection.

Step-by-Step Solution

1
Analyze the IP address spaces of both virtual networks.
VNet1 uses 10.1.0.0/1610.1.0.0/16 (IP range 10.1.0.010.1.0.0 to 10.1.255.25510.1.255.255). VNet2 uses 10.1.100.0/2410.1.100.0/24 (IP range 10.1.100.010.1.100.0 to 10.1.100.25510.1.100.255).
To determine if virtual network peering can be established, you must check for overlapping IP address spaces.
2
Compare the IP ranges to check for overlap.
The range of VNet2 (10.1.100.0/2410.1.100.0/24) is completely inside the range of VNet1 (10.1.0.0/1610.1.0.0/16). Therefore, the address spaces overlap.
Azure prevents virtual network peering creation if there is any overlap in the address spaces of the participating networks.
3
Evaluate the statement based on Azure peering requirements.
Peering cannot be configured. The statement is False.
Since the address spaces overlap, the configuration will fail.

Key Concept

Azure Virtual Network Peering requires non-overlapping IP address spaces.
Estimated Time:45s
Rate this question