What is a key benefit of using an Application Load Balancer over a Classic Load Balancer in ECS?

Question

Options

• ASimpler and older technology
• BAbility to route traffic based on content type
• CLimited to HTTP/HTTPS traffic
• DHigher costs for small-scale applications

• A
  3% (2)
• B
  89% (59)
• C
  2% (1)
• D
  6% (4)

Explanation

B is correct because the Application Load Balancer (ALB) supports content-based routing - it can inspect the request path, host headers, and other attributes to direct traffic to different ECS services or target groups. This is critical in microservices architectures where a single ALB can route /api/* to one service and /web/* to another, all behind one load balancer.

Why the distractors are wrong:

• A - "Simpler and older" describes the Classic Load Balancer, not a benefit of ALB.
• C - Being limited to HTTP/HTTPS is a restriction, not a benefit; ALB's HTTP/HTTPS support is actually a feature, but the CLB also handles these protocols.
• D - ALB can actually be more cost-effective at scale; higher cost for small apps is a drawback, not a benefit.

Memory tip: Think "ALB = Aware Load Balancer" - it's aware of the content of your request and can make smart routing decisions, unlike the Classic LB which routes blindly at the connection level.

No community discussion yet for this question.