SOA-C02 Monitoring, Logging, and Remediation Practice Question
A SysOps administrator notices that an Amazon RDS instance's CPU utilization is consistently above 90% during peak hours. The administrator needs to investigate which queries are consuming the most CPU. Which action should the administrator take?
⚠ Common exam trap
Candidates often confuse aggregate metrics (CloudWatch CPUUtilization) or OS-level metrics (Enhanced Monitoring) with database-specific query performance analysis, leading candidates to choose options that show overall CPU usage but not the root-cause queries.
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
✓
Enable Performance Insights for the RDS instance and review the top SQL queries.
Performance Insights is the correct tool because it provides a database-specific performance schema that visualizes database load and identifies the top SQL queries consuming resources. By enabling Performance Insights on the RDS instance, the administrator can directly view which queries are responsible for the high CPU utilization during peak hours, allowing targeted optimization.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable Performance Insights for the RDS instance and review the top SQL queries.
Why this is correct
Performance Insights is the correct choice because it correlates database load with individual SQL statements. The top SQL queries view breaks down DB Load by query, showing which SQL text is consuming CPU and waiting on resources in near real time. This lets you pinpoint the specific query (or queries) causing the CPU bottleneck, along with its execution plan and host/user details, rather than just seeing a metric spike.
- ✗
Use CloudWatch Logs Insights to query the database error log for slow queries.
Why it's wrong here
This fails because the database error log typically does not contain slow query information; slow queries are written to the RDS slow query log, which is a separate file and must be explicitly enabled and published to CloudWatch Logs. Even if the slow query log is present, CloudWatch Logs Insights can only search text such as query duration and elapsed time; it cannot quantify the real-time database load contribution of each query or show wait-event context the way Performance Insights does. The error log is meant for errors, not performance diagnostics.
- ✗
Enable detailed CloudWatch metrics for the RDS instance and analyze the CPUUtilization metric.
Why it's wrong here
Enabling detailed CloudWatch metrics will only give you a higher-resolution CPUUtilization time series; it does not identify which query or database session is responsible for that CPU usage. You would see a high CPU percentage but have no way to map that utilization to specific SQL statements or database operations. This makes it useful for detecting a problem, but not for root-cause query optimization, which is what the administrator needs.
- ✗
Enable RDS Enhanced Monitoring and review the 'cpuCreditUsage' metric.
Why it's wrong here
Enhanced Monitoring provides OS-level metrics, such as process CPU usage, memory, disk I/O, and network, but it does not expose query-level SQL text or execution details. Furthermore, the 'cpuCreditUsage' metric is associated with burstable EC2/DB instances that use CPU credits; RDS Enhanced Monitoring doesn't emit a metric named 'cpuCreditUsage' for standard RDS instances. Even if credit usage were relevant, it would only indicate CPU oversubscription, not which queries are consuming the credits.
Go deeper
Related to this question
About these practice questions
This SOA-C02 question is part of Courseiva's 1,169-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SOA-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A SysOps administrator is troubleshooting an Amazon RDS for MySQL instance that is experiencing high CPU utilization. The administrator wants to identify the specific queries consuming the most CPU. What is the MOST efficient way to achieve this?
easy- A.Use CloudWatch metrics for RDS and create a dashboard for CPU utilization.
- ✓ B.Enable Performance Insights for the RDS instance and view the top SQL queries.
- C.Enable Enhanced Monitoring for the RDS instance and view the CPU metrics.
- D.Enable CloudWatch Logs for the RDS instance and filter for slow query logs.
Why B: Performance Insights provides a built-in database load visualization and a dashboard that directly shows the top SQL queries consuming the most resources, including CPU. This is the most efficient method because it requires no additional configuration beyond enabling the feature and immediately surfaces the specific queries causing high CPU utilization.
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.