Quick Answer
The answer is the DatabaseConnections CloudWatch metric. This metric is correct because it directly tracks the current number of active client sessions against your RDS instance, and the “Too many connections” error occurs precisely when this count hits the instance’s max_connections parameter limit. By monitoring DatabaseConnections, you can set a CloudWatch Alarm to trigger when connections approach that threshold, allowing proactive scaling or connection pooling adjustments before the error disrupts your application. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this question tests your ability to distinguish between connection-oriented metrics and performance-oriented metrics like CPUUtilization or DatabaseConnectionsBurstBalance—a common trap is choosing a metric that measures resource pressure rather than the direct connection count. Remember that DatabaseConnections is a count, not a percentage, so you must know your instance’s max_connections value to set a meaningful alarm threshold. Memory tip: think “Connections = Count, not Capacity” to avoid confusing it with resource utilization metrics.
This SOA-C02 practice question tests your understanding of monitoring, logging, and remediation. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A SysOps administrator is troubleshooting an application that intermittently fails to connect to an RDS database. The error logs show 'Too many connections'. What CloudWatch metric should the administrator monitor to proactively detect this issue?
CPUUtilization
Why wrong: CPUUtilization indicates processor load, not connection count.
DatabaseConnections
Directly tracks the number of database connections.
NetworkThroughput
Why wrong: Network throughput does not directly reflect connection count.
FreeableMemory
Why wrong: Memory is related but not a direct measure of connections.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
DatabaseConnections
The 'Too many connections' error indicates that the RDS database has reached its maximum allowed number of simultaneous client connections. The DatabaseConnections CloudWatch metric tracks the current number of connections to the DB instance, so monitoring this metric allows the administrator to set an alarm when connections approach the instance's max_connections limit, enabling proactive scaling or connection management before errors occur.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
CPUUtilization
Why it's wrong here
CPUUtilization indicates processor load, not connection count.
DatabaseConnections
Why this is correct
Directly tracks the number of database connections.
Related concept
Read the scenario before looking for a memorised answer.
NetworkThroughput
Why it's wrong here
Network throughput does not directly reflect connection count.
FreeableMemory
Why it's wrong here
Memory is related but not a direct measure of connections.
Common exam traps
The trap here is that candidates may confuse performance metrics like CPU or memory with the specific connection limit error, overlooking that the 'Too many connections' error is directly tied to the DatabaseConnections metric and the max_connections configuration.
Detailed technical explanation
The max_connections parameter in RDS is set based on the instance class (e.g., db.t3.micro defaults to 66 connections, while larger instances allow more). The DatabaseConnections metric reports the current count of active connections, including those in sleep or idle states. Proactive monitoring should consider that connection pools or application retries can cause spikes; setting an alarm at 80-90% of max_connections allows time to adjust the parameter or scale the instance before errors occur.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Monitoring, Logging, and Remediation — study guide chapter
Learn the concepts, then practise the questions
Monitoring, Logging, and Remediation practice questions
Targeted practice on this topic area only
All SOA-C02 questions
1,546 questions across all exam domains
AWS Certified SysOps Administrator Associate SOA-C02 study guide
Full concept coverage aligned to exam objectives
SOA-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise SOA-C02 questions linked to Monitoring, Logging, and Remediation.
Practise SOA-C02 questions linked to Reliability and Business Continuity.
Practise SOA-C02 questions linked to Deployment, Provisioning, and Automation.
Practise SOA-C02 questions linked to Security and Compliance.
Practise SOA-C02 questions linked to Networking and Content Delivery.
Practise SOA-C02 questions linked to Cost and Performance Optimization.
Practise SOA-C02 questions linked to SOA-C02 fundamentals.
Practise SOA-C02 questions linked to SOA-C02 scenario.
Practise SOA-C02 questions linked to SOA-C02 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Monitoring, Logging, and Remediation — This question tests Monitoring, Logging, and Remediation — Read the scenario before looking for a memorised answer..
The correct answer is: DatabaseConnections — The 'Too many connections' error indicates that the RDS database has reached its maximum allowed number of simultaneous client connections. The DatabaseConnections CloudWatch metric tracks the current number of connections to the DB instance, so monitoring this metric allows the administrator to set an alarm when connections approach the instance's max_connections limit, enabling proactive scaling or connection management before errors occur.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.