SOA-C02 Monitoring, Logging, and Remediation Practice Question
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?
⚠ Common exam trap
It's easy for candidates to 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.
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
✓
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.
Answer analysis
Option-by-option breakdown
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 measures the percentage of the allocated vCPU resources consumed by the RDS database engine. While a large number of connections can increase CPU usage if each connection runs work, CPUUtilization can also be low when connections are idle or high from a single intensive query, so it does not reflect the connection count. An alarm on CPUUtilization would fail to trigger for connection exhaustion when queries are light.
- ✓
DatabaseConnections
Why this is correct
DatabaseConnections is a CloudWatch metric that directly reports the number of client network connections currently established to the RDS instance. This metric can be compared against the max_connections parameter, and when it approaches that ceiling, new connection requests fail with a 'Too many connections' error. Therefore, DatabaseConnections is the appropriate metric to monitor and alarm on to diagnose connection-limit issues.
- ✗
NetworkThroughput
Why it's wrong here
NetworkThroughput indicates the volume of data transmitted to and from the database instance in bytes per minute, not the number of active sessions. A single large query or a backup job can generate high throughput, while many idle connections can produce throughput near zero. Because throughput does not linearly track connection count, it cannot be used to detect connection-limit exhaustion reliably.
- ✗
FreeableMemory
Why it's wrong here
FreeableMemory reflects the amount of RAM available on the RDS instance, and each database connection does consume some memory for session state and buffers. However, memory can also be depleted by large query result sets, sort operations, or cache growth, and connection counts often hit the configured limit before memory is fully exhausted. Thus FreeableMemory is related but not a direct measure of the number of database connections.
Go deeper
Related to this question
About these practice questions
One of 1,169 original SOA-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.