RDS MySQL Slow Query Logs to CloudWatch Logs

• A.Use RDS Events to send slow query metrics to CloudWatch.
• B.Enable RDS Enhanced Monitoring and publish metrics to CloudWatch.
• C.Use AWS CloudTrail to monitor SQL queries.
• ✓ D.Publish slow query logs to CloudWatch Logs, create a metric filter, and set an alarm.

Why D: Option D is correct because slow query logs from RDS MySQL can be published to CloudWatch Logs. Once the logs are in CloudWatch Logs, you can create a metric filter to count the number of slow queries per minute and set a CloudWatch alarm on that metric to alert when the count exceeds a threshold. Option A is incorrect because RDS Events provide notifications about instance events (e.g., failover, maintenance), not slow query metrics. Option B is incorrect because Enhanced Monitoring provides OS-level metrics (e.g., CPU, memory) but not slow query log data. Option C is incorrect because CloudTrail records API calls made to AWS services, not SQL queries executed within RDS.

• A.Enable Performance Insights on the RDS instance and use the Performance Insights dashboard to view slow queries.
• B.Enable Enhanced Monitoring on the RDS instance and configure CloudWatch alarms based on the metrics.
• ✓ C.Modify the DB parameter group to enable slow_query_log and set log_output to FILE, then configure the RDS instance to publish the slowquery log file to CloudWatch Logs.
• D.Configure the RDS instance to export slow query logs to an S3 bucket, then set up a Lambda function to read the logs and send them to CloudWatch Logs.

Why C: Option C is correct because RDS for MySQL can natively stream slow query logs to CloudWatch Logs. This is achieved by modifying the DB parameter group to set 'slow_query_log' to 1 and 'log_output' to 'FILE', then enabling the 'slowquery' log export in the RDS console or CLI. This approach requires no additional infrastructure, minimizing operational overhead. Option A is incorrect because Performance Insights focuses on database performance metrics and schema analysis, not slow query log streaming to CloudWatch. Option B is incorrect because Enhanced Monitoring provides OS-level metrics (CPU, memory, etc.), not slow query logs. Option D is incorrect because exporting logs to S3 and using Lambda adds unnecessary complexity and latency; the native CloudWatch integration is more efficient.

• A.Create an RDS event subscription for 'low storage' events.
• B.Monitor the 'CPUUtilization' metric in CloudWatch.
• ✓ C.Enable the slow query log and publish it to CloudWatch Logs.
• ✓ D.Enable Performance Insights to visualize database load and identify top SQL statements.
• E.Enable Enhanced Monitoring to view process list and SQL queries.

Why C: Enable the slow query log and publish it to CloudWatch Logs (Option C) allows you to capture and analyze slow SQL queries. Performance Insights (Option D) provides a dashboard to visualize database load and identify the top SQL statements causing performance issues. Option A is incorrect because event subscriptions for low storage notify about storage events, not slow queries. Option B is incorrect because monitoring CPUUtilization only indicates high CPU usage but does not identify specific slow queries. Option E is incorrect because Enhanced Monitoring provides OS-level metrics like CPU and memory, not the actual SQL queries.