CompTIA Cloud+ (CV0-004)TroubleshootingMedium
A cloud engineer is reviewing an alert for a critical web service that indicates 'High Error Rate (HTTP 5xx)'. Further investigation reveals that the 503 Service Unavailable errors are occurring intermittently, often following periods of high traffic. The application is deployed behind a load balancer and uses an auto-scaling group. What is the MOST likely root cause?
- AThe load balancer's health checks are misconfigured, incorrectly marking healthy instances as unhealthy.
- BThere is a network ACL blocking traffic between the load balancer and the backend instances.
- CThe auto-scaling group's scaling policies are not aggressive enough to handle sudden traffic spikes.
- DThe backend database is experiencing deadlocks due to unoptimized queries.
Show answer & explanationAnswer & explanation
Correct answer: C. The auto-scaling group's scaling policies are not aggressive enough to handle sudden traffic spikes.
Intermittent 503 errors, especially during high traffic, point to the application servers being overwhelmed. If an auto-scaling group is in place, the most likely cause is that it's not scaling out quickly enough to meet demand, leading to service unavailability during spikes.
Why the other options are wrong
- A. Misconfigured health checks might cause instances to be removed incorrectly, but 503s would likely be more consistent or related to specific instance removals, not just high traffic.
- B. A network ACL blocking traffic would cause consistent connection failures, not intermittent 503s only during high traffic periods.
- D. Database deadlocks would typically manifest as application errors (e.g., HTTP 500 or specific database errors) and performance degradation, but less directly as widespread 503 'Service Unavailable' from the web service itself, unless the entire web service crashes due to database unavailability.
Auto-Scaling Policy Responsiveness
The ability of an auto-scaling group's policies to quickly and effectively add or remove instances in response to changes in application workload, preventing resource exhaustion or over-provisioning.
- Crucial for handling variable traffic patterns.
- Slow scaling can lead to performance degradation (e.g., 503 errors) during spikes.
- Factors include cooldown periods, metric thresholds, and instance launch times.
Memory trick: Traffic surge, but the scaling taxi isn't fast enough.