Free AWS SOA-C03 Actual Exam Questions - Question 13 Discussion

C because it automates snapshot retention without manual intervention before stack deletion.

C The Snapshot Deletion Policy specifically tells CloudFormation to keep a snapshot when deleting the RDS resource, so it fits perfectly for preserving data automatically. Other options rely on manual or extra setup steps.

Maybe C makes the most sense since it automates snapshot creation on stack deletion, cutting out manual steps. A and D seem way too complex compared to built-in policies.

B/C? B is manual, which risks forgetting snapshots before stack deletion. C automates snapshots on stack deletion, so it’s more reliable and less work overall.

C. This option avoids manual steps and extra resources by using CloudFormation’s native feature to automatically keep a snapshot, ensuring data persistence without additional overhead.

C. It’s the cleanest way to keep a snapshot without manual steps or extra templates.

The question hints at keeping data after deletion, so C fits best for automatic snapshot retention. C

C imo, since it’s built into CloudFormation and triggers a final snapshot automatically, it’s way simpler and less error-prone than scripting or manual stuff. No extra setup needed.

C. The Snapshot DeletionPolicy is designed exactly for this—to keep a final snapshot when the stack is deleted. It’s built into CloudFormation, so it automates retention without needing extra scripts or manual intervention. This tends to be more reliable and less error-prone than having to run separate backup templates or Lambda functions manually. As long as that policy is set on the RDS resource, the snapshot should persist independently of the stack’s lifecycle.

C is the best fit here. Using the Snapshot Deletion Policy directly in the CloudFormation template means snapshots will be automatically kept when the stack gets deleted, which removes the need for manual intervention or extra scripts. A and B add manual steps that could be missed, and D feels like overkill just to handle backups. If the specific RDS engine supports this policy, it’s by far the cleanest and most reliable way to retain data without extra operational overhead.

Option C seems best because the Snapshot Deletion Policy automates snapshot retention, so you don't have to manage backups manually each time the stack gets deleted. Much simpler overall.

B/C? B involves manual intervention which can be missed, making it less efficient. C automates snapshot retention on deletion, so it feels like a cleaner and more reliable solution if supported.

C. This automatically keeps the snapshot when deleting the stack, no extra manual steps needed. It’s just simpler and less error-prone than running scripts or Lambda functions every time.

Good point on automation. Since A relies on ongoing backups, it’s less efficient than using C, which automatically keeps a snapshot when the stack deletes. So C seems way cleaner and more reliable here.

It’s C because the DeletionPolicy snapshop option is designed to keep the snapshot automatically when the stack is deleted, so no manual backup or extra templates are needed.

C, it’s a built-in way to keep snapshots without manual steps.

Forget scripts or manual triggers—DeletionPolicy (C) is built exactly for this.

B/C? Taking a snapshot manually with Lambda (B) guarantees you get the backup right before deletion, no matter what. But if DeletionPolicy (C) works, it’s cleaner and automatic. I’d double-check support first.

C, it automates snapshot retention without extra manual work.

Option C seems the cleanest if supported since it automates snapshot retention without extra manual steps. Even if the RDS engine isn’t specified, most modern CloudFormation versions support DeletionPolicy for snapshots, which prevents data loss on stack deletion. Options A and D feel overcomplicated and error-prone, and B relies on remembering to trigger the Lambda each time, which could be missed. So, C looks like the best balance of reliability and efficiency assuming your CFN template and RDS type support it.