A cloud application's auto-scaling group is configured to scale out when CPU utilization exceeds 70%, but the application continues to experience high latency even after new instances launch. Monitoring shows CPU is at 65%. What is the most likely cause of the latency?

Question

Accepted Answer

A. A bottleneck in another resource dimension — such as memory exhaustion, database connection limits, or network bandwidth — that is not captured by the CPU scaling metric. Autoscaling based on CPU alone may miss bottlenecks in memory, database connections, or network bandwidth. If CPU is at 65% (below the threshold) but latency is high, the constraint exists in another resource dimension. The CompTIA Cloud+ V4 Troubleshooting domain covers diagnosing deployment and service disruption issues; Operations covers observability for multi-dimensional performance analysis.

A cloud application's auto-scaling group is configured to scale out when CPU utilization exceeds 70%, but the application continues to experience high latency even after new instances launch. Monitoring shows CPU is at 65%. What is the most likely cause of the latency?

Related Questions

Discussion