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…

Question

Options

• ADeploy multiple read replicas and have the team members make changes to separate replica
• BMigrate to Amazon RDS for SQL Server, take a snapshot, and restore from the snapshot
• CMigrate to Amazon Aurora MySQL and enable the Aurora Backtrack feature
• DEnable the Amazon RDS for MySQL Backtrack feature

• A
  6% (1)
• B
  12% (2)
• C
  76% (13)
• D
  6% (1)

Explanation

Explanation

Option C is correct because Amazon Aurora MySQL supports the Backtrack feature, which allows you to rewind the database to a specific point in time within seconds - without needing to restore from a backup or snapshot. This dramatically reduces downtime compared to traditional restores, and developers can quickly and precisely backtrack to a point just before a schema mistake was made.

Why the distractors are wrong:

• Option A is incorrect because read replicas are for scaling read traffic, not for schema testing or rollback - schema changes replicated to replicas would propagate the same mistake.
• Option B is incorrect because migrating to SQL Server adds unnecessary complexity, and snapshot restores are still slow and don't solve the core problem of lengthy recovery times.
• Option D is a trap - Backtrack is not available on standard Amazon RDS for MySQL; it is exclusively an Aurora-specific feature, making this option technically impossible.

Memory Tip

Remember: "Backtrack = Aurora only." If you see "Backtrack" in an exam question, the answer will always involve Amazon Aurora, never standard RDS. Think of Aurora as having a rewind button that RDS simply doesn't have.

No community discussion yet for this question.