All posts
Written by Sujith Quintelier β€’ Jun 3, 2022

πŸ“˜ AZ-700 Prep Highlights

Jun 3, 2022

This blog post captures my notes from the AZ-700 course, which is designed to teach Network Engineers how to design, implement, and maintain Azure networking solutions. The course covers a wide range of networking topics, including:

  • Designing, implementing, and managing core Azure networking infrastructure
  • Hybrid networking connections for on-premises integration
  • Load balancing strategies for optimizing traffic distribution
  • Routing and private access to Azure services
  • Network security and traffic filtering
  • Monitoring and troubleshooting network connectivity

1. Virtual Networks (VNets)

Azure Virtual Networks (VNets) are the backbone of networking in Azure, allowing resources to communicate securely.

VNet Capabilities

Azure VNets support:
βœ… Communication with the internet
βœ… Communication between Azure resources
βœ… Secure connectivity to on-premises networks
βœ… Traffic filtering using NSGs (Network Security Groups)
βœ… Routing network traffic efficiently

VNet Address Space

Azure VNets use private IP address ranges as defined in RFC 1918:

IP RangePrefix
10.0.0.0 - 10.255.255.25510/8
172.16.0.0 - 172.31.255.255172.16/12
192.168.0.0 - 192.168.255.255192.168/16

Subnet Allocation

Azure reserves 5 IPs per subnet:
πŸ”Ή x.x.x.0 β†’ Network address
πŸ”Ή x.x.x.1 β†’ Default gateway
πŸ”Ή x.x.x.2 & x.x.x.3 β†’ Azure DNS mapping
πŸ”Ή x.x.x.255 β†’ Broadcast address

2. Scopes in Azure

In Azure, every resource must have a unique name within its defined scope. Scopes are hierarchical:

1️⃣ Global (e.g., Storage Accounts)
2️⃣ Management Group
3️⃣ Subscription
4️⃣ Resource Group (e.g., VNets)
5️⃣ Resource (individual resource instances)

3. Regions & Availability Zones

Regions & Subscriptions

  • Resources in a VNet must be in the same region, but cross-region connectivity is possible.
  • VNets can be linked across different subscriptions.

Availability Zones (AZs)

Availability Zones provide high availability by distributing resources across physically separate data centers within a region.

πŸ”Ή Zonal Services β†’ Resources pinned to a specific zone
πŸ”Ή Zone-Redundant Services β†’ Automatically replicated across zones
πŸ”Ή Non-Regional Services β†’ Resilient to zone-wide and region-wide failures

4. Public IPs in Azure

Public IPs enable external communication for Azure resources. They can be static (unchanging) or dynamic (reassigned upon restart).

Public IP TypeAllocationSecurityZone Support
Basic SKUStatic / DynamicOpen by default❌ No AZ support
Standard SKUStatic onlySecure by default (NSG required)βœ… Zone-redundant

5. DNS Resolution in Azure

Azure provides both public and private DNS services to resolve domain names.

DNS
DNS

Public DNS

Azure DNS manages internet-facing domain names and supports:
πŸ”Ή A / AAAA records for IPv4/IPv6
πŸ”Ή CNAME records for aliasing domains

Private DNS

For internal name resolution within VNets, Azure supports:
1️⃣ Azure DNS Private Zones
2️⃣ Azure-provided name resolution
3️⃣ Custom DNS servers

πŸ”Ή Azure’s built-in DNS resolver: 168.63.129.16

DNS forwarding allows on-premises resources to resolve Azure hostnames, ensuring seamless hybrid connectivity.

πŸ“Œ Example: Conditional Forwarding
To resolve hostnames across VNets, use custom DNS servers with conditional forwarding rules.

6. VNet Peering for Cross-Network Connectivity

Azure VNet Peering allows seamless communication between VNets without a VPN.

Peering TypeScopePerformance
Regional PeeringSame Azure regionHigh bandwidth, low latency
Global PeeringCross-regionUses Azure backbone

VNet Peering Benefits

βœ… Secure private communication (no internet exposure)
βœ… No need for VPN gateways
βœ… Supports NSGs for access control
βœ… Works across subscriptions and tenants

Peering
Peering

7. Gateway Transit for Shared VPN Access

Gateway Transit allows one VNet to use another VNet’s VPN gateway for cross-premises connectivity.

πŸ’‘ Use case: A hub-and-spoke topology where a single gateway in the hub VNet provides VPN access to multiple spokes.

Gateway Transit
Gateway Transit

8. Azure Traffic Routing

Azure manages traffic routing through:

1️⃣ System Routes (default routes created by Azure)

πŸ”Ή Internet traffic β†’ Sent via the default Internet Gateway
πŸ”Ή Private traffic β†’ Stays within the VNet

2️⃣ Custom Routes (UDRs - User Defined Routes)

Use route tables to override system routes.
πŸ’‘ Example: Direct traffic to a firewall appliance instead of the default gateway.

Default Route Table

SourceDestinationNext Hop
Default0.0.0.0/0Internet
Default10.0.0.0/8None
Default192.168.0.0/16None

Final Thoughts

This post provides a comprehensive summary of key Azure networking concepts from AZ-700. Understanding VNets, peering, DNS, and routing is essential for designing scalable, secure, and high-performing cloud networks.

πŸ“Œ Key Takeaways:
βœ… Master VNet and subnet design to optimize address space
βœ… Use peering and gateway transit for hybrid connectivity
βœ… Leverage DNS solutions to simplify name resolution
βœ… Control traffic with NSGs & UDRs for security and compliance

πŸ”₯ If you’re studying for AZ-700, focus on hands-on labs to reinforce concepts! πŸš€

comments powered by Disqus