Restores, versioning, RPO and RTO: SOA-C03 study notes and practice questions
What to know about Restores, versioning, RPO and RTO for the SOA-C03 exam, from the Reliability and Business Continuity domain (22% of the exam guide), then 2 free questions to test it. Part of the SOA-C03 study guide.
A public library's catalog runs on an Amazon RDS for PostgreSQL DB instance with automated backups kept for 14 days.
At 10:42 this morning, a faulty script deleted thousands of loan records. The last manual snapshot was taken yesterday at midnight.
The library wants to recover the data as it was just before 10:42, with as little data loss as possible.
What should a CloudOps engineer do?
Choose one answer.
AA. Restore to 10:41 with point-in-time recovery into a new DB instance, then recover the records from it.
BB. Restore yesterday's midnight snapshot to a new DB instance and switch the application to the new instance's endpoint.
CC. Perform a point-in-time restore of the existing DB instance in place to 10:41, keeping its current endpoint.
DD. Create a read replica of the DB instance and promote it, because the replica still holds the rows the script deleted.
Show the answer and explanation
Answer: A
A. Right: Correct. Automated backups and transaction logs let RDS restore to any second within the retention period. The restore creates a new instance, from which the records can be copied back or which can replace the original. Learn more: Restoring a DB instance to a specified time (opens in a new tab)
B. Wrong: The snapshot is more than 10 hours old, so all changes made this morning before the script ran would be lost. Point-in-time restore gives a much closer recovery point. Learn more: Restoring to a DB instance (opens in a new tab)
Automated backups give RDS point-in-time recovery to any second within the retention window, typically up to about five minutes before now. A restore always creates a new DB instance, so the team either copies the lost rows back or moves the application to the new endpoint. Snapshots lose more data, and replicas copy the mistake.
A ski resort keeps trail maps and lift-status images in an S3 bucket that has S3 Versioning turned on.
A cleanup script mistakenly ran a simple DELETE request, without a version ID, against 3,000 current objects. The website now returns 404 errors for those images.
What is the quickest way for a CloudOps engineer to bring the objects back?
Choose one answer.
AA. Delete the delete markers that the script created, so that the previous versions become the current versions again.
BB. Restore the objects from the bucket's S3 Glacier archive tier, which keeps a copy of every object for 30 days after deletion.
CC. Turn on S3 Object Lock for the bucket and roll the objects back to the last locked state in governance mode.
DD. Open a support case to ask AWS to recover the deleted objects from the bucket's internal backups.
Show the answer and explanation
Answer: A
A. Right: Correct. In a versioned bucket, a DELETE without a version ID only adds a delete marker. Removing the marker makes the most recent earlier version current again, with no data copied. Learn more: Working with delete markers (opens in a new tab)
S3 Versioning protects against accidental deletes. A simple DELETE places a delete marker on top of the object, and the earlier versions remain. Deleting the marker restores access to the previous version, so the fix takes minutes and copies no data.
Want more on Restores, versioning, RPO and RTO? The 5 full-length practice sets have 10 more Restores, versioning, RPO and RTO questions, 325 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets →