Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam SOA-C02 Topic 6 Question 75 Discussion

Actual exam question for Amazon's SOA-C02 exam
Question #: 75
Topic #: 6
[All SOA-C02 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Christiane
2 months ago
As a SysOps admin, I'm already deleting stacks for breakfast. This is child's play! A all the way, no doubt.
upvoted 0 times
D) Update the application's IAM policy with a Deny statement for the dynamodb:DeleteTabie action.
upvoted 0 times
...
Starr
3 days ago
C) Enable termination protection on the AWS Cloud Formation stack.
upvoted 0 times
...
Annamae
9 days ago
B) Add a Snapshot deletion policy to the DynamoDB resource in the AWS CloudFormation stack.
upvoted 0 times
...
Dana
14 days ago
A) Add a Retain deletion policy to the DynamoDB resource in the AWS CloudFormation stack
upvoted 0 times
...
Lorean
17 days ago
C) Enable termination protection on the AWS Cloud Formation stack.
upvoted 0 times
...
Elliot
18 days ago
B) Add a Snapshot deletion policy to the DynamoDB resource in the AWS CloudFormation stack.
upvoted 0 times
...
Elroy
29 days ago
C) Alright, let's go with A then. Thanks for the advice!
upvoted 0 times
...
Olive
1 months ago
A) Trust me, I've done this plenty of times. A is the way to go.
upvoted 0 times
...
Aaron
1 months ago
A) Add a Retain deletion policy to the DynamoDB resource in the AWS CloudFormation stack
upvoted 0 times
...
Chun
1 months ago
B) Are you sure about that? Maybe we should double-check.
upvoted 0 times
...
Arleen
2 months ago
A) Add a Retain deletion policy to the DynamoDB resource in the AWS CloudFormation stack.
upvoted 0 times
...
...
Novella
2 months ago
D is a clever idea, but it feels like a bit of a workaround. A is the more straightforward solution to this problem.
upvoted 0 times
...
Kenia
2 months ago
I'm not sure, but I think option B could also work. Snapshot deletion policy might be a good choice.
upvoted 0 times
...
Delmy
2 months ago
I agree with Marvel. Adding a Retain deletion policy to the DynamoDB resource makes sense.
upvoted 0 times
...
Letha
2 months ago
Haha, C is just trying to save the whole stack, not the specific resource we need to keep. Nice try, but A is the way to go.
upvoted 0 times
Adelina
1 months ago
Haha, C is just trying to save the whole stack, not the specific resource we need to keep. Nice try, but A is the way to go.
upvoted 0 times
...
Frank
2 months ago
A) Add a Retain deletion policy to the DynamoDB resource in the AWS CloudFormation stack
upvoted 0 times
...
...
Marvel
2 months ago
I think the SysOps administrator should choose option A.
upvoted 0 times
...
Sheridan
2 months ago
Hmm, not sure about this one. I was considering B, but Retain seems like the better option to preserve the DynamoDB table.
upvoted 0 times
Stanford
20 days ago
Let's go with A then, to be on the safe side and keep the DynamoDB table intact.
upvoted 0 times
...
Brett
21 days ago
I'm not sure, but A does sound like the safest option to preserve the DynamoDB table.
upvoted 0 times
...
Mona
1 months ago
I agree, A is the best choice to make sure the DynamoDB table is not deleted.
upvoted 0 times
...
Orville
2 months ago
I think A is the correct option. It will retain the DynamoDB table when deleting the CloudFormation stack.
upvoted 0 times
...
...
Floyd
2 months ago
I'm not sure, but I think enabling termination protection on the AWS Cloud Formation stack could also be a good option.
upvoted 0 times
...
Maynard
2 months ago
Wow, this question really tests our AWS knowledge! I think the answer is A - adding a Retain deletion policy to the DynamoDB resource. That way, the table won't be deleted when the stack is removed.
upvoted 0 times
...
Yoko
2 months ago
I agree with Roselle. Adding a Retain deletion policy will prevent the DynamoDB table from being deleted.
upvoted 0 times
...
Roselle
3 months ago
I think the SysOps administrator should add a Retain deletion policy to the DynamoDB resource.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77