You need to design a load balancing solution that supports both ultra-low latency TCP connections and HTTP request routing based on URL paths. What is the best approach?

hard📝 Architecture Q9 of 15

AWS - Elastic Load Balancing

AUse a Network Load Balancer for TCP traffic and an Application Load Balancer for HTTP routing

BUse only an Application Load Balancer configured for both TCP and HTTP

CUse a Classic Load Balancer for all traffic types

DUse a Network Load Balancer with HTTP listeners for path-based routing

Step-by-Step Solution

Solution:

Step 1: Analyze requirements
Ultra-low latency TCP connections require NLB; HTTP path-based routing requires ALB.
Step 2: Evaluate load balancer capabilities
ALB supports HTTP routing but not optimized for TCP at scale; NLB supports TCP but not HTTP path routing.
Step 3: Architect solution
Combine NLB for TCP and ALB for HTTP routing to meet both needs effectively.
Final Answer:
Use a Network Load Balancer for TCP traffic and an Application Load Balancer for HTTP routing -> Option A
Quick Check:
Separate load balancers for TCP and HTTP routing [OK]

Quick Trick: Combine NLB for TCP and ALB for HTTP routing [OK]

Common Mistakes:

Expecting ALB to handle ultra-low latency TCP connections
Using NLB for HTTP path-based routing
Relying on Classic Load Balancer for complex routing needs

Master "Elastic Load Balancing" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

You need to design a load balancing solution that supports both ultra-low latency TCP connections and HTTP request routing based on URL paths. What is the best approach?

Step 1: Analyze requirements

Step 2: Evaluate load balancer capabilities

Step 3: Architect solution

Final Answer:

Quick Check:

Want More Practice?