Which action should the SysOps administrator take before deleting the AWS CloudFormation stack?
Add a Retain deletion policy to the DynamoDB resource in the AWS CloudFormation stack.
Add a Snapshot deletion policy to the DynamoDB resource in the AWS CloudFormation stack.
Enable termination protection on the AWS CloudFormation stack.
Update the application’s IAM policy with a Deny statement for the dynamodb:DeleteTable action.
Explanations:
Adding a Retain deletion policy to the DynamoDB resource in the CloudFormation stack ensures that the DynamoDB table will not be deleted when the stack is deleted. The Retain policy preserves the resource even if the stack is deleted.
There is no Snapshot deletion policy for DynamoDB tables. While snapshots are relevant for some AWS resources (like RDS), they do not apply to DynamoDB in this context.
Enabling termination protection on the CloudFormation stack prevents the entire stack from being deleted. It does not specifically address the need to retain the DynamoDB table while deleting other resources.
Updating the IAM policy to deny thedynamodb:DeleteTableaction does not prevent CloudFormation from deleting the table. CloudFormation will ignore the IAM policy during stack deletion and still delete resources unless a Retain policy is set.
I plot that the answer is:
Add a Retain deletion policy to the DynamoDB resource in the AWS CloudFormation stack.