AWS Certified SysOps Administrator Practice Exam

How can you ensure snapshots of EBS volumes are kept when deleting CloudFormation stacks?

1. By configuring resource tags for the EBS volumes.

2. Utilize the DeletionPolicy=snapshot setting in CloudFormation.

3. Set a lifecycle policy for EBS volumes in S3 before deletion.

4. Manually take snapshots before deleting the stacks.

The correct answer is: Utilize the DeletionPolicy=snapshot setting in CloudFormation.

Utilizing the DeletionPolicy=snapshot setting in CloudFormation is the correct approach to ensure that snapshots of EBS volumes are preserved when deleting CloudFormation stacks. When you apply this deletion policy to an EBS volume resource within your CloudFormation template, it instructs AWS to create a snapshot automatically just before the resource is deleted. This means that even though the stack and its associated resources are being removed, you still retain a snapshot of your data at the time of deletion, which can later be used to restore the volume. This feature streamlines management, as it eliminates the need for any manual intervention to create snapshots prior to deletion, which can be prone to human error or oversight. Instead, by incorporating the appropriate deletion policy directly into your CloudFormation template, you ensure a consistent and automated approach to managing EBS snapshots. The other options do not provide a direct or reliable method to keep snapshots upon stack deletion. Configuring resource tags for EBS volumes does not affect how deletion is handled by CloudFormation. Setting a lifecycle policy for EBS volumes in S3 is not a functionality that applies; lifecycle policies are for S3 objects, not EBS volumes. While manually taking snapshots is a possible approach, it is not efficient or necessary with the