Question

After a routine deployment, users intermittently receive HTTP 502 Bad Gateway errors from an application behind a cloud load balancer. The load balancer health checks pass most of the time, backend instances show low CPU and memory, and the application logs show no exceptions. However, the load balancer access logs reveal that failed requests correspond to entries where the backend response time exceeds the load balancer's configured idle/response timeout. Which action is the MOST appropriate next step to resolve the errors?

Accepted Answer

Align the load balancer's backend response/idle timeout with the application's processing time and investigate slow endpoints

Answer

Increase the number of backend instances in the target group to add more capacity

Answer

Enable sticky sessions on the load balancer so requests reach a consistent backend

Answer

Replace the load balancer health check protocol from HTTP to TCP to reduce false negatives