Subnets are subdivisions within a Virtual Network (VNet). They allow you to segment your network and enhance control.
- Devices within a subnet can communicate directly with each other.
- Security: Subnets can be isolated with network security groups (NSGs) for improved control.
- NICs and Subnets: A virtual machine’s network interface (NIC) connects it to one subnet.
- A VM can have multiple NICs, which allows it to connect to multiple subnets.
- IP Addresses:
- Public IPs can be assigned to VMs and public load balancers.
- Private IPs are used for internal communication and internal load balancers.
- Load balancers distribute traffic either to the internet (public) or within the VNet (private).
- IP addresses can be static or dynamic.
- CIDR Notation: IP ranges for subnets are defined using CIDR (Classless Inter-Domain Routing) notation.
- For example,
192.168.1.0/24defines 256 addresses from192.168.1.0to192.168.1.255. 192.168.1.0/16covers a much larger range:192.168.0.0to192.168.255.255.
- For example,
Virtual Networks and Peering give you powerful tools to design secure, scalable, and connected cloud architectures. Subnets provide additional flexibility and segmentation. Whether you’re connecting within Azure or bridging your on-premises systems, VNets offer the flexibility to build robust solutions.
Want to practice designing your own Azure network? Get hands-on in our AZ-900 video course – or click here to go back to the AZ-900 list of requirements.
Please click here to find out more about Microsoft’s AZ-900 exam.
