Which action should the SysOps administrator take before deleting the AWS Cloud Formation stack?

A SysOps administrator has used AWS Cloud Formal ion to deploy a serverless application Into a production VPC. The application consists of an AWS Lambda function an Amazon DynamoDB table, and an Amazon API Gateway API. The SysOps administrator must delete the AWS Cloud Formation stack without deleting the DynamoDB table.

Which action should the SysOps administrator take before deleting the AWS Cloud Formation stack?
A . Add a Retain deletion policy to the DynamoDB resource in the AWS CloudFormation stack
B . Add a Snapshot deletion policy to the DynamoDB resource in the AWS CloudFormation stack.
C . Enable termination protection on the AWS Cloud Formation stack.
D . Update the application’s IAM policy with a Deny statement for the dynamodb:DeleteTabie action.

View Answer

Answer: A

Explanation:

To delete the AWS CloudFormation stack without deleting the DynamoDB table, you need to apply a deletion policy to the DynamoDB resource. The Retain deletion policy ensures that the specified resource is not deleted when the stack is deleted. Instead, it is retained.

Steps:

Modify the CloudFormation Template:

Add a deletion policy to the DynamoDB table resource.

json

Copy code

{

"Resources": {

"MyDynamoDBTable": {

"Type": "AWS::DynamoDB::Table",

"DeletionPolicy": "Retain",

…

}

}

}

Reference: AWS CloudFormation DeletionPolicy Attribute

Update the Stack:

Update the CloudFormation stack with the modified template.

Reference: Updating a Stack

Delete the Stack:

Proceed to delete the stack. The DynamoDB table will be retained.

Reference: Deleting a Stack