AZ-700 Question 5
Single answerYour company� on-premises network uses the 10.0.0.0/16 IP range. You are tasked with creating a new Azure Virtual Network (VNet) for the engineering department. The VNet must not overlap with the on-premises range, and it should allow for future expansion of subnets. Which address space is the most appropriate for this new Azure VNet?
- A
10.0.0.0/16
- B
10.0.1.0/24
- C
10.1.0.0/16
- D
192.168.0.0/16
Show answer and explanation
Correct answer: C
Explanation
When creating a new VNet in Azure that will eventually connect to on-premises resources, it is crucial to avoid IP address overlap. Overlapping IP address spaces can prevent successful site-to-site or VPN connections and complicate routing. Azure best practices recommend planning your address space thoroughly to allow for subnet expansion and avoid future collisions. For more information, refer to the official Microsoft documentation on designing and implementing Azure VNets: https://learn.microsoft.com/azure/virtual-network/virtual-networks-overview.
- A. Incorrect.
Option A (10.0.0.0/16) directly overlaps with the on-premises network, so it cannot be used if you plan to connect the VNet to the on-premises environment.
- B. Incorrect.
Option B (10.0.1.0/24) also falls within the 10.0.0.0/16 range used on-premises, making it unsuitable for the same reason�overlapping IP spaces.
- C. Correct.
Option C (10.1.0.0/16) is correct because it does not overlap with the on-premises 10.0.0.0/16 network and provides a sufficiently large block of addresses for future subnet expansion.
- D. Incorrect.
Option D (192.168.0.0/16) does not overlap with 10.0.0.0/16, but it may conflict with other commonly used private ranges and might impose additional routing complexities. In most cases, staying within the same 10.x range but a different subnet is simpler to manage.