AZ-700 Question 1
Select 2You are designing a new Azure Virtual Network for a multi-tier application consisting of front-end, business logic, and database subnets. Your on-premises network uses 192.168.0.0/16, and an upcoming project will require site-to-site VPN connectivity between on-premises and Azure. You also plan to deploy domain controllers in the Azure VNet that must have static private IP addresses. Which two design considerations should you implement to avoid address conflicts and ensure optimal IP address management?
- A
Use 192.168.0.0/16 for your Azure VNet to match the on-premises address space for easy integration.
- B
Choose a non-overlapping address space such as 10.1.0.0/16, and segment it into appropriately sized subnets for each application tier.
- C
Use a /24 subnet for each tier and assign static IP addresses to domain controllers from the DHCP dynamic allocation pool for simplicity.
- D
Exclude static IP addresses for domain controllers from the dynamic allocation range and configure them within the same subnet.
Show answer and explanation
Correct answers: B, D
Explanation
When designing IP schemes for Azure VNets, you must avoid overlapping address spaces with on-premises networks to enable smooth connectivity via site-to-site VPN. Azure best practices recommend selecting a distinct address block and then subdividing it into subnets sized for your workloads� current and future needs. Additionally, any static IP addresses (for domain controllers or other critical VMs) should be excluded from the subnet� DHCP allocation to prevent potential IP conflicts. For more details, refer to the official Microsoft documentation: https://learn.microsoft.com/azure/virtual-network/virtual-networks-address-spaces-overview.
- A. Incorrect.
Option 1 is incorrect. Reusing the on-premises IP range (192.168.0.0/16) for Azure leads to an overlap when you set up site-to-site VPN. This prevents proper routing between on-premises and Azure.
- B. Correct.
Option 2 is correct. Selecting a non-overlapping address space (e.g., 10.1.0.0/16) prevents conflict with on-premises networks. Creating multiple subnets provides logical separation and sufficient capacity for future growth.
- C. Incorrect.
Option 3 is incorrect. While using /24 subnets is a common approach, assigning static IP addresses from inside the DHCP dynamic range increases the risk of IP conflicts and is not aligned with best practices.
- D. Correct.
Option 4 is correct. Reserving static IP addresses outside the subnet� dynamic allocation range ensures there is no conflict between statically assigned IP addresses and automatically allocated addresses.