SOA-C02 Monitoring, Logging, and Remediation Practice Question
A SysOps administrator is managing a fleet of EC2 instances in an Auto Scaling group. The instances are behind an Application Load Balancer. The administrator notices that the 'SurgeQueueLength' metric for the ALB is frequently high. What does this indicate, and what is the BEST remediation action?
⚠ Common exam trap
It's easy for candidates to confuse SurgeQueueLength with connection-level metrics (like idle timeout) or assume the load balancer itself is the bottleneck, when in fact the metric directly indicates insufficient target capacity.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The targets are not able to handle the request rate; increase the desired capacity or add scaling policies.
The SurgeQueueLength metric measures the number of requests that are queued by the Application Load Balancer (ALB) because no healthy target is available to process them. A frequently high value indicates that the targets (EC2 instances) are overwhelmed and cannot keep up with the incoming request rate. The best remediation is to increase the desired capacity of the Auto Scaling group or add scaling policies (e.g., based on SurgeQueueLength or RequestCountPerTarget) to automatically add more instances to handle the load.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The targets are unhealthy; decrease the desired capacity to reduce load.
Why it's wrong here
Unhealthy targets would typically be indicated by elevated HTTP 5xx responses or health check failures, not by a high SurgeQueueLength. Decreasing the desired capacity would reduce the number of available targets further, causing even more requests to queue and increasing the backlog rather than alleviating it.
- ✓
The targets are not able to handle the request rate; increase the desired capacity or add scaling policies.
Why this is correct
A high SurgeQueueLength metric for an Application Load Balancer signifies that requests are waiting in the load balancer's queue because the registered targets are not processing them fast enough. To resolve this, you should increase the desired capacity of your Auto Scaling group or add scaling policies, such as target tracking based on the ALBRequestCountPerTarget metric, so more targets are available to handle the request rate.
- ✗
The load balancer is accepting too many connections; increase the idle timeout.
Why it's wrong here
The idle timeout setting controls how long a connection can remain open with no activity before the load balancer closes it; it does not affect how quickly requests are dequeued and forwarded to targets. Increasing the idle timeout would merely hold connections open longer, doing nothing to reduce the queue of pending requests that are waiting for an available target.
- ✗
The load balancer is overloaded; replace it with a Network Load Balancer.
Why it's wrong here
Replacing the Application Load Balancer with a Network Load Balancer would not solve a capacity problem at the target level, because an NLB operates at Layer 4 and simply forwards traffic without HTTP-aware load balancing. The bottleneck is the targets' inability to keep pace with the incoming request rate, so the load balancer type is irrelevant; you need more target capacity, not a different balancer.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SOA-C02 question from scratch — 1,169 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SOA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SOA-C02 exam.