SOA-C02 Deployment, Provisioning, and Automation Practice Question

A company uses AWS CloudFormation to deploy a stack that includes an Amazon RDS DB instance with automated backups enabled. The stack is deleted and then recreated. The administrator wants to restore data from the backup of the original DB instance. How can this be achieved?

⚠ Common exam trap

SOA-C02 often tests the misconception that automated backups persist after instance deletion like manual snapshots do — candidates must remember automated backups die with the instance unless explicitly retained.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Data cannot be restored because automated backups are deleted when the DB instance is deleted.

When an RDS DB instance is deleted, its automated backups are deleted along with it — they are tied to the instance's lifecycle and are not retained independently. Because the CloudFormation stack deletion removed the original DB instance, the automated backups no longer exist, so there is nothing to restore from. Unless a manual snapshot was taken beforehand, the data is unrecoverable.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Restore from the latest automated backup stored in S3.
Why it's wrong here
Automated backups for RDS are stored in Amazon S3, but they are intrinsically tied to the lifecycle of the DB instance. When you delete the instance, its automated backups are deleted as part of the same process; they are not accessible as standalone objects in S3 that you can restore from later. Therefore, referencing the 'latest automated backup' is meaningless after the instance is terminated unless you explicitly created a final manual snapshot.
✗
Restore from the automated backup snapshot that is retained after deletion.
Why it's wrong here
This option incorrectly assumes that automated backup snapshots survive the deletion of the DB instance. In RDS, automated backups are only retained for the backup retention period of the live instance, and they are permanently removed when the instance is deleted. Only manual snapshots, which you create explicitly via the console or API, are retained after the instance is terminated. Since the scenario did not mention a manual snapshot, this recovery path does not exist.
✗
Use the RDS recycle bin to recover the deleted DB instance.
Why it's wrong here
RDS does not offer a recycle bin or any similar soft-delete feature that allows you to recover a deleted DB instance. Unlike services such as S3 with versioning or a Trash concept, a deleted RDS instance is immediately and permanently removed from the service. The only way to preserve data before deletion is to take a final DB snapshot, and since no such snapshot was mentioned, the recycle bin option is not a valid recovery mechanism.
✓
Data cannot be restored because automated backups are deleted when the DB instance is deleted.
Why this is correct
When an RDS DB instance is deleted, all automated backups—including system snapshots and transaction logs—are also deleted by default, unless you had previously chosen to create a final snapshot. Since the CloudFormation stack deletion did not specify that a final snapshot was taken, the automated backups were lost along with the instance. Therefore, the data cannot be restored because no independent backup artifact survives the instance deletion.

Go deeper

SOA-C02 Deployment, Provisioning, and Automation Practice Question

Why each option matters

Option-by-option breakdown

Related to this question