Instiq
Chapter 4 · Design Infrastructure Solutions·v2.0.0·Updated 6/3/2026·~11 min

What's changed: Deepened AZ-305 Chapter 4 (added comparison tables, scenarios, FAQs, exam traps, deep-dive paragraphs to each section; localized figures to Japanese)

4.3Designing Networking

Key points

Understand networking design—VNet/subnets/NSG, peering/hub-spoke, VPN Gateway/ExpressRoute, Front Door/App Gateway/Load Balancer, and Private Link. Design secure, scalable connectivity.

Networking is about isolation, connectivity, and protection. Build on VNets and extend securely with hub-spoke and private connectivity.

4.3.1Networking composition

Diagram of Azure networking design: built on VNets and subnets isolated by NSGs (subnet/NIC traffic control); many VNets connected via hub-spoke (shared services in a hub VNet with peered spokes, or Virtual WAN); on-prem connectivity via VPN Gateway (encrypted; S2S/P2S) and ExpressRoute (dedicated, low-latency/stable); load balancing via Front Door/Application Gateway (L7) and Load Balancer (L4); and private connectivity to PaaS via Private Link/private endpoints.
Networking design
  • VNet/subnets/NSG: isolate with virtual networks; control subnet/NIC traffic with NSG.
  • Hub-spoke: centralize shared services in a hub VNet, peering spokes (or Virtual WAN).
  • VPN Gateway/ExpressRoute: on-prem connectivity. VPN = encrypted (S2S/P2S), ExpressRoute = dedicated (low-latency/stable).
  • Private Link: connect to PaaS (Storage/SQL, etc.) via private IP, avoiding public exposure.
Exam point

Common on AZ-305: subnet/NIC traffic control = NSG, consolidate many VNets = hub-spoke/Virtual WAN, encrypted on-prem = VPN Gateway, dedicated = ExpressRoute, private PaaS connectivity = Private Link/private endpoints, global L7 = Front Door, regional L7 = App Gateway, L4 = Load Balancer.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.