Notifications
Clear all
Topic starter
14/09/2022 8:38 pm
A company has a database monitoring solution that uses Amazon CloudWatch for its Amazon RDS for SQL Server environment. The cause of a recent spike in CPU utilization was not determined using the standard metrics that were collected. The CPU spike caused the application to perform poorly, impacting users. A Database Specialist needs to determine what caused the CPU spike.
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.)
- A . Enable Amazon CloudWatch Events and view the incoming T-SQL statements causing the CPU to spike.
- B . Enable Enhanced Monitoring metrics to view CPU utilization at the RDS SQL Server DB instance level.
- C . Implement a caching layer to help with repeated queries on the RDS SQL Server DB instance.
- D . Use Amazon QuickSight to view the SQL statement being run.
- E . Enable Amazon RDS Performance Insights to view the database load and filter the load by waits, SQL statements, hosts, or users.
Suggested Answer: BE
Explanation:
https://aws.amazon.com/premiumsupport/knowledge-center/rds-instance-high-cpu/ “Several factors can cause an increase in CPU utilization. For example, user-initiated heavy workloads, analytic queries, prolonged deadlocks and lock waits, multiple concurrent transactions, long-running transactions, or other processes that utilize CPU resources. First, you can identify the source of the CPU usage by: Using Enhanced Monitoring Using Performance Insights"
Explanation:
https://aws.amazon.com/premiumsupport/knowledge-center/rds-instance-high-cpu/ “Several factors can cause an increase in CPU utilization. For example, user-initiated heavy workloads, analytic queries, prolonged deadlocks and lock waits, multiple concurrent transactions, long-running transactions, or other processes that utilize CPU resources. First, you can identify the source of the CPU usage by: Using Enhanced Monitoring Using Performance Insights"