A company is launching a new Amazon RDS for MySQL Multi-AZ DB instance to be used as a data store for a custom-built application. After a series of tests with point-in-time recovery disabled, the company decides that it must have point-in-time recovery reenabled before using the DB instance to store production data.
What should a database specialist do so that point-in-time recovery can be successful?
Correct Answer: A
Explanation from Amazon documents:
Performance Insights is a feature of Amazon Aurora MySQL that helps you quickly assess the load on your database and determine when and where to take action. Performance Insights displays a dashboard that shows the database load in terms of average active sessions (AAS), which is the average number of sessions that are actively running SQL statements at any given time. Performance Insights also shows the top SQL statements, waits, hosts, and users that are contributing to the database load.
Amazon DevOps Guru is a fully managed service that helps you improve the operational performance and availability of your applications by detecting operational issues and recommending specific actions for remediation. Amazon DevOps Guru applies machine learning to automatically analyze data such as application metrics, logs, events, and traces for behaviors that deviate from normal operating patterns. Amazon DevOps Guru supports Amazon RDS as a resource type and can monitor the performance and availability of your RDS databases.
By turning on Performance Insights for the Aurora MySQL database and configuring and turning on Amazon DevOps Guru for RDS, the database specialist can automatically detect and diagnose database performance issues and resolve bottlenecks faster. This solution will allow the database specialist to monitor the database load and identify the root causes of performance problems using Performance Insights, and receive actionable insights and recommendations from Amazon DevOps Guru to improve the operational performance and availability of the database.
Therefore, option A is the correct solution to meet the requirements. Option B is not sufficient because creating a CPU usage alarm will only notify the database specialist when the CPU utilization is high, but it will not help diagnose or resolve the database performance issues. Option C is not efficient because using the Amazon RDS query editor to get the process ID of the query that is causing the database to lock and running a command to end the process will require manual intervention and may cause data loss or inconsistency. Option D is not efficient because using the SELECT INTO OUTFILE S3 statement to query data from the database and saving the data directly to an Amazon S3 bucket will incur additional time and cost, and using Amazon Athena to analyze the files for long-running queries will not help prevent or resolve locking contention on the database.
Bonita
10 months agoLorean
10 months agoParis
10 months agoGail
11 months agoBonita
11 months agoMitsue
11 months ago