DBS-C01 · Question #184
An ecommerce company is migrating its core application database to Amazon Aurora MySQL. The company is currently performing online transaction processing (OLTP) stress testing with concurrent…
The correct answer is A. Enable Enhanced Monitoring at less than 30 seconds of granularity to review the operating C. Review Amazon RDS Performance Insights to identify the top SQL statements and wait events. https://aws.amazon.com/premiumsupport/knowledge-center/rds-instance-high-cpu/ https://aws.amazon.com/premiumsupport/knowledge-center/rds-mysql-slow-query/
Question
An ecommerce company is migrating its core application database to Amazon Aurora MySQL. The company is currently performing online transaction processing (OLTP) stress testing with concurrent database sessions. During the first round of tests, a database specialist noticed slow performance for some specific write operations. Reviewing Amazon CloudWatch metrics for the Aurora DB cluster showed 90% CPU utilization. Which steps should the database specialist take to MOST effectively identify the root cause of high CPU utilization and slow performance? (Choose two.)
Options
- AEnable Enhanced Monitoring at less than 30 seconds of granularity to review the operating
- BReview the VolumeBytesUsed metric in CloudWatch to see if there is a spike in write I/O.
- CReview Amazon RDS Performance Insights to identify the top SQL statements and wait events.
- DReview Amazon RDS API calls in AWS CloudTrail to identify long-running queries.
- EEnable Advance Auditing to log QUERY events in Amazon CloudWatch before the next round of
How the community answered
(33 responses)- A55% (18)
- B27% (9)
- D12% (4)
- E6% (2)
Explanation
https://aws.amazon.com/premiumsupport/knowledge-center/rds-instance-high-cpu/ https://aws.amazon.com/premiumsupport/knowledge-center/rds-mysql-slow-query/
Topics
Community Discussion
No community discussion yet for this question.