Networking
CoreAzure Virtual Network and subnets
Private address spaces and delegated subnet boundaries.
Key points
- VNet supplies a regional private address space for Azure resources.
- Subnets divide the address space and provide an association boundary for network controls.
- Address ranges must be valid, nonoverlapping, and sized for Azure reservations plus growth.
Best-known use cases
- Create separate application and data subnets.
- Attach an NSG or route table to a workload boundary.
What candidates often confuse it with
- VNet vs subnet: whole regional private network vs deployable address segment.
- Subnet vs resource group: network placement boundary vs management lifecycle container.
Key takeaway
Plan nonoverlapping VNet and subnet ranges before deploying resources and associating network controls.
Related services
- VNet peering
- Azure public IP addresses
Relevant exam tasks
- D4.1.S1 — Create and configure virtual networks and subnets
- D4.1.S2 — Create and configure virtual network peering
- D4.1.S3 — Configure public IP addresses