SOA-C02 Monitoring, Logging, and Remediation Practice Question

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 Enhanced Monitoring to view OS-level metrics

  Why this is correct

  Enhanced Monitoring on Amazon RDS delivers a stream of OS-level telemetry, including per-process CPU utilization, memory usage, disk I/O, and network traffic, via the CloudWatch console. This granular view lets you distinguish whether the high CPU is being consumed by the database engine itself or by auxiliary processes such as backups, log writers, or the OS, narrowing the root-cause search. It is a purely diagnostic action—it does not alter the workload but provides the raw data needed to formulate a targeted fix.

• ✗

  Enable Multi-AZ to distribute the load

  Why it's wrong here

  The Multi-AZ deployment option creates a synchronous standby replica in a different Availability Zone, but the standby does not serve any read traffic or absorb compute load from the primary instance. It exists solely for automated failover during an instance or AZ outage, so enabling it would have zero effect on the primary's CPU utilization. Furthermore, turning on Multi-AZ triggers a reboot, which temporarily interrupts service and could actually amplify the problem during a performance investigation.

• ✗

  Delete the slow query log to free up CPU

  Why it's wrong here

  Slow query logs are simply files that capture statements exceeding a specified execution-time threshold; deleting them reclaims disk space but does not stop the slow-running queries from being executed or reduce their resource consumption. High CPU is driven by the queries themselves competing for processor cycles, not by the log files that describe them. To actually relieve CPU pressure, you must rewrite the queries, add appropriate indexes, or adjust database parameters—removing logs is an administrative cleanup unrelated to performance.

• ✓

  Enable Performance Insights to identify high-load queries

  Why this is correct

  Performance Insights is an RDS feature that continuously records database load measured in wait events and correlates it with the specific SQL statements, users, and hosts that are responsible for the load, all displayed on a time-ordered dashboard. By drilling into the 'Top SQL' view, you can immediately spot the queries consuming the most CPU, identify poor execution plans, and see when the load spikes. This makes it the most direct troubleshooting tool for determining the root cause of high CPU from a database perspective.

• ✗

  Increase the instance size to reduce CPU utilization

  Why it's wrong here

  Resizing the DB instance to a larger class is a mitigation tactic that temporarily masks the symptom by giving the database more processor capacity, but it does nothing to diagnose the underlying cause of the CPU saturation. The original inefficient queries or processes remain and will consume the same relative resources on the new instance, potentially leading to further scaling and cost escalation. A sysops administrator should first gather evidence from Enhanced Monitoring or Performance Insights to understand the root cause before committing to a more expensive instance.

Go deeper

Related to this question