AWS - Elastic Load Balancing
You need to design a highly scalable system that requires static IP addresses and low latency for millions of TCP connections. Which AWS load balancer should you choose and why?
You need to design a highly scalable system that requires static IP addresses and low latency for millions of TCP connections. Which AWS load balancer should you choose and why?
hard📝 Application Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Identify requirements
The system needs static IPs, low latency, and support for millions of TCP connections.Step 2: Match requirements to load balancer features
NLB supports static IPs, is designed for extreme scalability, and handles TCP traffic efficiently with low latency.Step 3: Eliminate incorrect options
ALB focuses on HTTP, Classic LB is older and less scalable, Gateway LB is for network appliances, not general TCP load balancing.Final Answer:
Network Load Balancer, because it supports static IPs and handles millions of TCP connections with low latency -> Option CQuick Check:
Static IP + TCP + scalability = NLB [OK]
Quick Trick: For static IP and TCP scale, choose NLB [OK]
Common Mistakes:
MISTAKES- Choosing ALB for TCP static IP needs
- Confusing Classic LB as newest
- Assuming Gateway LB handles general TCP load balancing
Master "Elastic Load Balancing" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes