Your on-premises network has an IP address range of 10.0.0.0/23. You have an Azure virtual network named VNet1 that contains a virtual machine named VM1. VNet1 has an IP address range of…

The correct answer is C. Configure VNet1 to use the IP address range of 10.0.2.0/24. A Site-to-Site VPN requires that the address spaces on each side do not overlap. The on-premises network is 10.0.0.0/23, which covers the range 10.0.0.0–10.0.1.255. VNet1's current range of 10.0.1.0/24 (10.0.1.0–10.0.1.255) falls entirely within that on-premises range - a…

Implement and manage an on-premises and hybrid networking infrastructure

Question

Your on-premises network has an IP address range of 10.0.0.0/23. You have an Azure virtual network named VNet1 that contains a virtual machine named VM1. VNet1 has an IP address range of 10.0.1.0/24. You need to deploy a Site-to-Site (S2S) VPN to connect the on-premises network to VNet1. What should you do first?

Options

ADeploy Azure Bastion to VNet1.
BDeploy Azure Extended Network.
CConfigure VNet1 to use the IP address range of 10.0.2.0/24.
DConfigure VNet1 to use an IP address range of 10.0.1.128/25.

How the community answered

(65 responses)

A
5% (3)
B
9% (6)
C
85% (55)
D
2% (1)

Explanation

A Site-to-Site VPN requires that the address spaces on each side do not overlap. The on-premises network is 10.0.0.0/23, which covers the range 10.0.0.0–10.0.1.255. VNet1's current range of 10.0.1.0/24 (10.0.1.0–10.0.1.255) falls entirely within that on-premises range - a direct overlap. Azure will not allow a VPN gateway to route between overlapping address spaces. Changing VNet1 to 10.0.2.0/24 eliminates the overlap and allows the S2S VPN to be established. Azure Bastion provides browser-based VM access and is unrelated. Azure Extended Network extends on-premises subnets to Azure, which would worsen the overlap.

Topics

#Site-to-Site VPN#IP Addressing#Network Overlap#Azure Virtual Network

Community Discussion

No community discussion yet for this question.

Full AZ-800 Practice