In the context of ECS, which load balancer types are most suitable for distributing HTTP and HTTPS traffic efficiently?

Question

Options

• AApplication Load Balancer
• BNetwork Load Balancer
• CClassic Load Balancer
• DSimple Routing Load Balancer

• A
  93% (27)
• C
  3% (1)
• D
  3% (1)

Explanation

Application Load Balancer (ALB) is the premier choice for HTTP/HTTPS in ECS - it operates at Layer 7, enabling content-based routing (path, host, headers), native ECS dynamic port mapping, and SSL/TLS termination. Network Load Balancer (NLB) also qualifies because it operates at Layer 4 (TCP/TLS), can handle HTTPS passthrough or TLS termination at extreme throughput with ultra-low latency, and integrates fully with ECS target groups.

Classic Load Balancer (C) is wrong because it's a legacy service that AWS has deprecated; it lacks modern ECS features like dynamic port mapping and target groups, making it unsuitable for new architectures. Simple Routing Load Balancer (D) is a distractor - it doesn't exist as an AWS load balancer type; "Simple Routing" is a Route 53 DNS policy, not a load balancer.

Memory tip: Think in layers - "ALB = Application layer (Layer 7) = HTTP/HTTPS smart routing; NLB = Network layer (Layer 4) = raw TCP/TLS speed." Both integrate with ECS. Classic is the old guard (retired), and "Simple" belongs to Route 53, not load balancing.

No community discussion yet for this question.