AZ-700 Question 2
Single answerYou are designing an IP address space for a new multi-tier application hosted in Azure. Your on-premises environment already uses the 10.0.0.0/8 address range. You want to ensure that all Azure resources will be reachable from on-premises without IP conflicts and leave room for future expansions. Which address space should you assign to your new Azure Virtual Network?
- A
10.0.0.0/16
- B
172.16.0.0/16
- C
192.168.0.0/24
- D
10.12.0.0/24
Show answer and explanation
Correct answer: B
Explanation
When creating an Azure Virtual Network that must integrate with an on-premises environment, it is critical to select an address range that does not overlap with any existing private ranges on-prem. Since 10.0.0.0/8 is fully utilized on-premises, choosing 172.16.0.0/16 avoids conflicts and provides a sufficiently large IP range for future subnets or workloads. For more details, refer to Microsoft documentation on Azure Virtual Network address space planning (https://learn.microsoft.com/azure/virtual-network/virtual-networks-address-space).
- A. Incorrect.
Option A: 10.0.0.0/16. This falls within the existing on-premises range (10.0.0.0/8), so it would cause overlapping address issues.
- B. Correct.
Option B: 172.16.0.0/16. This is a private address space that does not overlap with 10.0.0.0/8, offering enough addresses for scalable workloads.
- C. Incorrect.
Option C: 192.168.0.0/24. While it is a valid private address space, /24 might be too small if you anticipate many subnets or large workloads.
- D. Incorrect.
Option D: 10.12.0.0/24. This also resides within 10.0.0.0/8 and would conflict with the on-premises range.