What's changed: Deepened AZ-104 Chapter 4 to Associate depth (tables, scenarios, FAQ, traps; localized figures)
4.3Network Connectivity and Name Resolution
Understand VNet-to-VNet connectivity with peering, on-prem connectivity via VPN/ExpressRoute, Azure Load Balancer, and name resolution with Azure DNS.
Connecting multiple networks and on-premises, and making them reachable by name, is part of the admin’s job. Learn peering, VPN/ExpressRoute, and DNS.
4.3.1Connectivity and name resolution options
For secure management access to VMs, use Azure Bastion. It provides RDP/SSH from the browser (Azure portal) without exposing public IPs or ports 3389/22 to the internet, so you do not need a separate jump-box VM.
- VNet peering: connects VNet to VNet privately with low latency.
- VPN gateway: connects on-prem via an encrypted tunnel over the internet. ExpressRoute: a dedicated private circuit, faster and more reliable.
- Azure Load Balancer: distributes inbound traffic across VMs (L4). Azure DNS: name resolution with public/private zones.
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.