← Back to Portal

AZ-700 Study Material

Quick Reference Cheat Sheet

10 golden rules, service comparison tables, subnet and limit numbers, NSG default priorities, and CLI/PowerShell command snippets — everything on one page for the final pass before your exam.

10 Golden Rules 6 comparison tables Key numbers CLI & PowerShell
1Routing Precedence: Longest prefix match selects candidates. Then: UDR > BGP > System routes (same length).
2Non-Transitive Peering: VNet peering is non-transitive. Spoke-A cannot reach Spoke-B through the hub — Firewall/NVA + UDRs required.
3Service Endpoints vs Private Endpoints: SE = VNet only, public IP retained. PE = private IP, on-prem access possible, DNS required.
4Virtual WAN Migration Order: Create VWAN → delete existing peerings → connect spokes → update UDRs. Never connect before deleting peerings.
5Firewall Rule Order: DNAT → Network → Application → Default Deny. A Network rule match stops processing — Application rules are never reached for that traffic.
6ExpressRoute Has No Encryption: Use VPN-over-ER (IPsec) for encryption on provider circuits. MACsec is only for ExpressRoute Direct connections.
7DNS Resolver Directions: Inbound endpoint = on-prem → Azure. Outbound endpoint = Azure → on-prem (via forwarding ruleset).
8Hub-Spoke UDR Requirements: Spoke subnets need UDRs to route spoke-to-spoke via Firewall. GatewaySubnet needs UDRs for return traffic from on-prem. Disable BGP propagation on spoke route tables.
9Network Watcher Tools: IP Flow Verify = NSG block check. Next Hop = routing check. Connection Monitor = continuous monitoring. Packet Capture = deep investigation.
10Load Balancer Decision: L4 Regional = Azure LB. L7 Regional = App Gateway. L7 Global = Front Door. DNS Global = Traffic Manager. L4 Global = Cross-Region LB. NVA insertion = Gateway LB.

VPN Gateway vs ExpressRoute vs Virtual WAN

FeatureVPN GatewayExpressRouteVirtual WAN
TransportPublic Internet (IPsec)Private circuit (MPLS/Ethernet)SD-WAN + backbone
Encryption✅ Always (IPsec)❌ Layer 2 only✅ (over tunnels)
Max bandwidth10 Gbps (VpnGw5)10 Gbps (Direct: 100 Gbps)50 Gbps per hub
SLA / latencyVariable (Internet)Dedicated / predictableVariable / backbone
Best for branchesSmall / few sitesCritical / large sites50+ sites / any mix
BGP supportVpnGw1+ only (not Basic)Mandatory (AS 12076)Automatic

Load Balancing Service Comparison

ServiceLayerScopeWAFSSLBest For
Azure Load Balancer (Std)L4RegionalTCP/UDP, VMs, VMSS
Application Gateway (v2)L7Regional✅ TerminateWeb apps, API, WAF
Azure Front Door (Std/Premium)L7Global✅ Premium✅ TerminateGlobal web, CDN, multi-region
Traffic ManagerDNSGlobalPass-throughNon-HTTP, failover, geography
Cross-Region LBL4GlobalGlobal TCP/UDP failover
Gateway LBL4RegionalNVA inline insertion

Front Door vs Traffic Manager

FeatureAzure Front DoorTraffic Manager
LayerL7 (HTTP/HTTPS)DNS (L4 DNS)
Routes app traffic?✅ Yes (Anycast proxy)❌ DNS only
SSL termination✅ At edge PoP❌ None
WAF✅ Built-in (Standard/Premium)
Failover speedSeconds (health probe)Depends on DNS TTL
Protocol supportHTTP/HTTPS onlyAny (TCP, SMTP, custom)

Subnet Sizes

/29 → 3
Minimum usable subnet (8 − 5 reserved)
/28 → 11
16 − 5 reserved addresses
/27 → 27
32 − 5 reserved (GatewaySubnet min)
/26 → 59
64 − 5 reserved (Firewall/Bastion min)
/24 → 251
256 − 5 reserved (common subnet)
5
Azure reserved IPs per subnet (.0,.1,.2,.3,.255)

VPN Gateway Limits

SKUS2S TunnelsP2S ConnectionsThroughput
Basic10128100 Mbps
VpnGw1 / VpnGw1AZ30250650 Mbps
VpnGw2 / VpnGw2AZ305001 Gbps
VpnGw3 / VpnGw3AZ301,0001.25 Gbps
VpnGw4 / VpnGw4AZ1005,0005 Gbps
VpnGw5 / VpnGw5AZ10010,00010 Gbps

NSG Default Rules (Lower Number = Higher Priority)

PriorityNameDirectionAction
65000AllowVnetInBoundInboundAllow
65001AllowAzureLoadBalancerInBoundInboundAllow
65500DenyAllInBoundInboundDeny
65000AllowVnetOutBoundOutboundAllow
65001AllowInternetOutBoundOutboundAllow
65500DenyAllOutBoundOutboundDeny

Azure Firewall SKU Feature Matrix

FeatureBasicStandardPremium
FQDN application rules
Threat Intelligence filtering
IDPS (signature-based)
TLS inspection
URL filtering (full)Partial (SNI)
Web category filtering

Azure CLI — Networking Essentials

# Create VNet with a subnet
az network vnet create -g RG -n MyVNet --address-prefixes 10.0.0.0/16 \
  --subnet-name Subnet1 --subnet-prefixes 10.0.1.0/24

# Create route table and add a route
az network route-table create -g RG -n MyRT
az network route-table route create -g RG --route-table-name MyRT \
  -n ToFirewall --address-prefix 0.0.0.0/0 \
  --next-hop-type VirtualAppliance --next-hop-ip-address 10.0.0.4

# Associate route table with subnet
az network vnet subnet update -g RG --vnet-name MyVNet -n Subnet1 \
  --route-table MyRT

# Disable BGP route propagation on route table
az network route-table update -g RG -n MyRT \
  --disable-bgp-route-propagation true

# Create NSG rule (allow HTTP)
az network nsg rule create -g RG --nsg-name MyNSG -n AllowHTTP \
  --priority 100 --direction Inbound --access Allow \
  --protocol Tcp --destination-port-ranges 80

# Enable Private Endpoint Network Policies on subnet
az network vnet subnet update -g RG --vnet-name MyVNet -n PrivateSubnet \
  --private-endpoint-network-policies Enabled

# Create Private DNS Zone and link to VNet
az network private-dns zone create -g RG -n privatelink.database.windows.net
az network private-dns link vnet create -g RG \
  --zone-name privatelink.database.windows.net \
  --name MyDnsLink --virtual-network MyVNet --registration-enabled false

# Check effective routes on a NIC
az network nic show-effective-route-table -g RG -n MyNicName -o table

# IP Flow Verify (Network Watcher)
az network watcher test-ip-flow --vm MyVM -g RG \
  --direction Inbound --protocol TCP \
  --local 10.0.1.4:80 --remote 1.2.3.4:60000

PowerShell — Networking Essentials

# Get effective routes on a VM NIC
Get-AzEffectiveRouteTable -NetworkInterfaceName "MyNic" `
  -ResourceGroupName "RG" | Format-Table

# Create a route table and UDR
$rt = New-AzRouteTable -Name "MyRT" -ResourceGroupName "RG" `
  -Location "uksouth" -DisableBgpRoutePropagation
Add-AzRouteConfig -Name "ToFirewall" -RouteTable $rt `
  -AddressPrefix "0.0.0.0/0" -NextHopType "VirtualAppliance" `
  -NextHopIpAddress "10.0.0.4"
Set-AzRouteTable -RouteTable $rt

# Associate route table with subnet
$vnet = Get-AzVirtualNetwork -Name "MyVNet" -ResourceGroupName "RG"
$subnet = Get-AzVirtualNetworkSubnetConfig -VirtualNetwork $vnet `
  -Name "Subnet1"
Set-AzVirtualNetworkSubnetConfig -VirtualNetwork $vnet `
  -Name "Subnet1" -AddressPrefix $subnet.AddressPrefix `
  -RouteTable $rt
Set-AzVirtualNetwork -VirtualNetwork $vnet

# Get VPN Gateway connection status
Get-AzVirtualNetworkGatewayConnection -Name "MyConn" `
  -ResourceGroupName "RG" | Select-Object Name, ConnectionStatus

# Start a packet capture (Network Watcher)
New-AzNetworkWatcherPacketCapture -NetworkWatcher $nw `
  -TargetVirtualMachineId $vm.Id -PacketCaptureName "MyCapture" `
  -StorageAccountId $storage.Id
Azure ServiceSub-resourcePrivate DNS Zone
Azure SQL DatabasesqlServerprivatelink.database.windows.net
Azure SQL Managed InstancemanagedInstanceprivatelink.{dns_zone}.database.windows.net
Azure Blob Storageblobprivatelink.blob.core.windows.net
Azure File Storagefileprivatelink.file.core.windows.net
Azure Queue Storagequeueprivatelink.queue.core.windows.net
Azure Table Storagetableprivatelink.table.core.windows.net
Azure Key Vaultvaultprivatelink.vaultcore.azure.net
Azure Container Registryregistryprivatelink.azurecr.io
Azure Cosmos DB (SQL API)sqlprivatelink.documents.azure.com
Azure App Service / Functionssitesprivatelink.azurewebsites.net
Azure Event Hubsnamespaceprivatelink.servicebus.windows.net
Azure Service Busnamespaceprivatelink.servicebus.windows.net
Azure Monitor (Log Analytics)workspaceprivatelink.ods.opinsights.azure.com

Each VNet that needs Private Endpoint DNS resolution must have its own VNet link to the Private DNS Zone (registration-enabled: false for most zones).

Trap 1: "ExpressRoute encrypts data in transit" — FALSE. Private only. Use VPN-over-ER for encryption.
Trap 2: "Traffic Manager routes application traffic" — FALSE. DNS only — never sees packets.
Trap 3: "AllowGatewayTransit goes on the spoke peering" — FALSE. Hub peering gets AllowGatewayTransit. Spoke gets UseRemoteGateways.
Trap 4: "Service Endpoints work from on-premises" — FALSE. VNet only. Private Endpoints are needed for on-premises access.
Trap 5: "NSG rules automatically apply to Private Endpoint NICs" — FALSE. Must enable privateEndpointNetworkPolicies on the subnet.
Trap 6: "VPN Gateway Basic SKU supports BGP and P2S with IKEv2" — FALSE. No BGP. No IKEv2/Entra on Basic.
Trap 7: "AzureFirewallSubnet needs a route table" — FALSE in standard deployments. Only for forced tunnelling scenarios.
Trap 8: "A Network rule allow for TCP 443 lets Application rules evaluate for FQDN" — FALSE. Network rule match stops processing.
Trap 9: "Standard Load Balancer provides outbound Internet access automatically" — FALSE. Requires NAT Gateway or explicit outbound rules.
Trap 10: "DDoS Protection Standard stops HTTP floods" — FALSE. L3/L4 only. HTTP floods require WAF on App Gateway or Front Door.
Trap 11: "ExpressRoute FastPath applies to spoke VNets peered with the hub" — FALSE. FastPath only applies to the hub VNet.
Trap 12: "MACsec can be used on provider-based ExpressRoute circuits" — FALSE. MACsec requires ExpressRoute Direct (your own port at the Microsoft edge).