AWS Solutions Architect Associate (SAA-C03) · Free practice question 5 of 12
RDS point-in-time restore
At 2:47 PM, a faulty deployment at Quimby Travel corrupted rows in an Amazon RDS for MySQL database that has automated backups enabled with a 7-day retention period. The team wants to recover the database to its state at 2:45 PM. What should they do?
- A.Promote a read replica created before the deployment
- B.Perform a point-in-time restore to 2:45 PM, which creates a new DB instance, and point the application to it
- C.Restore the most recent manual snapshot over the existing DB instance
- D.Reboot the DB instance with failover to the Multi-AZ standby
Show answer and explanation
Correct answer: B. Perform a point-in-time restore to 2:45 PM, which creates a new DB instance, and point the application to it
Why: Automated backups plus transaction logs allow a point-in-time restore to any second within the retention period, and the restore creates a new DB instance that the application must be pointed to. A read replica would already have received the corrupting changes, snapshot restores cannot overwrite an existing instance and return only to the snapshot time, and a Multi-AZ standby is synchronously replicated so it holds the same corrupted data.
More free AWS Solutions Architect Associate (SAA-C03) questions
- IAM explicit deny overrides allow
- VPC Flow Logs for connectivity troubleshooting
- Transit Gateway instead of peering mesh
- Scheduled scaling for predictable peaks
- Route 53 geolocation routing
- Data Lifecycle Manager for EBS snapshots
- DynamoDB Streams with Lambda
- Amazon MQ for broker migrations
- Graviton instances for price-performance
- Amazon Inspector vulnerability scanning
- Root user protection best practices