Networking
CoreAzure Load Balancer
Layer 4 internal/public traffic distribution, probes, and rules.
Key points
- Layer 4 distribution using public or internal frontend configurations.
- Backend pools list targets and health probes determine eligibility for new flows.
- Rules map frontend protocol and port to backend protocol and port.
Best-known use cases
- Distribute private TCP traffic across VMs.
- Publish a public regional service across healthy backends.
What candidates often confuse it with
- Public vs internal Load Balancer: internet frontend vs private VNet frontend.
- Load Balancer vs Azure DNS: distribute flows to healthy targets vs resolve a name to an address.
Key takeaway
Configure frontend, rule, probe, pool, and backend path as one complete Layer 4 load-balancing chain.
Related services
- Azure DNS
- Azure Application Gateway
Relevant exam tasks
- D4.3.S1 — Configure Azure DNS
- D4.3.S2 — Configure an internal or public load balancer
- D4.3.S3 — Troubleshoot load balancing