A city’s permit-api fleet runs in an Auto Scaling group and must receive HTTP traffic with path-based routing and instance health checks. Which load balancer should the architect choose?
Select an answer to reveal the explanation.
Short Explanation
An ALB is the traffic cop that understands HTTP paths and can pull unhealthy permit-api cars out of the lane. NLBs are great for raw TCP, Gateway Load Balancer is for appliances, and raw Route 53 to instance IPs skips real L7 health and scaling hygiene.
Full Explanation
Application Load Balancers operate at Layer 7 and are the appropriate choice for HTTP(S) distribution, path- or host-based routing, and health checks against Auto Scaling groups. Network Load Balancers excel at Layer 4 TCP/UDP performance but are not the primary fit when HTTP routing is required. Gateway Load Balancer fronts third-party appliances, and DNS-only distribution to instance IPs lacks ALB’s application-aware load distribution and ASG integration.