Which approach shou...
 
Notifications
Clear all

Which approach should the Database Specialist take to reduce downtime?

1 Posts
1 Users
0 Likes
39 Views
Theo
 Theo
(@baintheo)
Noble Member
Joined: 6 months ago
Posts: 367
Topic starter  

A company is using Amazon RDS for MySQL to redesign its business application. A Database Specialist has

noticed that the Development team is restoring their MySQL database multiple times a day when Developers make mistakes in their schema updates. The Developers sometimes need to wait hours to the restores to complete.

Multiple team members are working on the project, making it difficult to find the correct restore point for each mistake.

Which approach should the Database Specialist take to reduce downtime?

  • A . Deploy multiple read replicas and have the team members make changes to separate replica instances
  • B . Migrate to Amazon RDS for SQL Server, take a snapshot, and restore from the snapshot
  • C . Migrate to Amazon Aurora MySQL and enable the Aurora Backtrack feature
  • D . Enable the Amazon RDS for MySQL Backtrack feature

Show Answer Hide Answer

Suggested Answer: C

Explanation:

"Amazon Aurora, a fully-managed relational database service in AWS, is now offering a backtrack feature. With Amazon Aurora with MySQL compatibility, users can backtrack, or "rewind", a database cluster to a specific point in time, without restoring data from a backup. The backtrack process allows a point in time to be specified with one second resolution, and the rewind process typically takes minutes. This new feature facilitates developers in undoing mistakes like deleting data inappropriately or dropping the wrong table."

   
Quote
Share: