Which combination of steps should be taken to provide more visibility into the processes and queries running during an increase in CPU load?
(Choose two.)
Enable Amazon CloudWatch Events and view the incoming T-SQL statements causing the CPU to spike.
Enable Enhanced Monitoring metrics to view CPU utilization at the RDS SQL Server DB instance level.
Implement a caching layer to help with repeated queries on the RDS SQL Server DB instance.
Use Amazon QuickSight to view the SQL statement being run.
Enable Amazon RDS Performance Insights to view the database load and filter the load by waits, SQL statements, hosts, or users.
Explanations:
Amazon CloudWatch Events does not provide the capability to track or view incoming T-SQL statements. It is used for responding to events in the AWS environment, not for monitoring SQL queries.
Enhanced Monitoring provides detailed metrics at the RDS instance level, including OS-level metrics like CPU utilization, which can help identify resource constraints affecting database performance.
Implementing a caching layer can help reduce CPU usage for repeated queries but does not help in diagnosing or identifying the root cause of past CPU spikes.
Amazon QuickSight is a business intelligence tool used for data visualization and reporting, but it does not offer direct visibility into SQL statements running on an RDS instance.
RDS Performance Insights allows deeper analysis of database load by providing insights on waits, SQL statements, users, and hosts, making it helpful for pinpointing the cause of CPU spikes.
I deduce that the answer is:
Enable Enhanced Monitoring metrics to view CPU utilization at the RDS SQL Server DB instance level.