SAA-C03 ยท High-performing networks and edge
Choosing a load balancer
Application Load Balancer (layer 7, path and host routing), Network Load Balancer (layer 4, static IP, extreme throughput) and Gateway Load Balancer (third-party appliances).
Key points
- ALB: layer 7, HTTP/HTTPS; routes by host, path, header, method, query string, source IP; TLS offload, user authentication.
- NLB: layer 4 (TCP, UDP, TLS), millions of requests/s, static IP per AZ (or Elastic IP); non-HTTP, fixed IPs, TLS pass-through.
- GWLB: layer 3, all ports, spreads traffic over virtual appliances (firewalls, IDS/IPS) via GENEVE port 6081; GWLB endpoints as route next hop.
- Classic Load Balancer: legacy.
Source: https://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html
Practice questions
At which OSI layer does a Network Load Balancer operate?
- Layer 3 (network)
- Layer 4 (transport)
- Layer 6 (presentation)
- Layer 7 (application)
Show answer
Answer: B. Layer 4 (transport)
The NLB works at layer 4, the transport layer, balancing TCP, UDP and TLS flows. The ALB works at layer 7 and the Gateway Load Balancer at layer 3.
Which requirements point to a Network Load Balancer rather than an Application Load Balancer?
- Clients must reach the load balancer on fixed Elastic IP addresses
- Requests to /images/* must go to a different target group
- The application speaks a custom UDP protocol
- Users must sign in through Amazon Cognito before reaching targets
- Targets must receive the TLS traffic still encrypted and decrypt it
Show answer
Answer: A. Clients must reach the load balancer on fixed Elastic IP addresses, C. The application speaks a custom UDP protocol, E. Targets must receive the TLS traffic still encrypted and decrypt it
An NLB provides a static IP per AZ (and can take one Elastic IP per subnet), balances UDP, and with a TCP listener on 443 passes encrypted traffic through so the targets decrypt it. Path-based routing and authenticating users at the load balancer are ALB features.
A Gateway Load Balancer is the right choice when you want to route HTTP requests to different microservices based on the URL path.
Show answer
Answer: False
False. A GWLB works at layer 3 and exists to insert and scale virtual appliances such as firewalls and IDS/IPS in the traffic path; it does not read URLs. Path-based routing is an ALB feature.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
