Exam AWS Certified SysOps Administrator - Associate All Questions

View all questions & answers for the AWS Certified SysOps Administrator - Associate exam

Exam AWS Certified SysOps Administrator - Associate topic 1 question 231 discussion

Exam question from Amazon's AWS Certified SysOps Administrator - Associate

Question #: 231
Topic #: 1

[All AWS Certified SysOps Administrator - Associate Questions]

A SysOps administrator needs to delete an AWS CloudFormation stack that is no longer in use. The CloudFormation stack is in the DELETE_FAILED state. The SysOps administrator has validated the permissions that are required to delete the CloudFormation stack.

Which of the following are possible causes of the DELETE_FAILED state? (Choose two.)

A. The configured timeout to delete the stack was too low for the delete operation to complete.
B. The stack contains nested stacks that must be manually deleted first.
C. The stack was deployed with the --disable-rollback option.
D. There are additional resources associated with a security group in the stack.
E. There are Amazon S3 buckets that still contain objects in the stack.

Show Suggested Answer

Suggested Answer: DE 🗳️

by Gil80 at Feb. 13, 2023, 12:19 p.m.

Disclaimers:

- ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Submit Cancel

SceneDev

5 months, 1 week ago

Selected Answer: BE

D. (There are additional resources associated with a security group in the stack. )https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-delete-stack-fail . The documentation highlights that security groups with active associations or dependencies outside the stack can prevent deletion. For example, if an EC2 instance outside the stack uses the security group, the stack cannot delete it. Correct answers B and E. If the scope includes external dependencies (not explicitly stated in the question), D (security group dependencies) could also be a valid answer. However, B and E align best with the AWS documentation and the question's context.

upvoted 1 times

...

numark

6 months, 3 weeks ago

Selected Answer: BE

While resources associated with a security group can complicate the deletion process, CloudFormation generally manages dependencies and associated resources appropriately. However, this could lead to a DELETE_FAILED state if there are complex dependencies or manual deletion policies in place that prevent the deletion of the security group or the resources associated with it. It's important to note that while this could potentially be a cause, it's less likely than option B or E, which are common scenarios that directly prevent the deletion of CloudFormation stacks.

upvoted 2 times

...

TwinSpark

1 year, 8 months ago

Selected Answer: DE

"Some resources must be empty before they can be deleted. For example, you must delete all objects in an Amazon S3 bucket or remove all instances in an Amazon EC2 security group before you can delete the bucket or security group." Why cannot be B : "This includes nested stacks whose root stacks have termination protection enabled. Deactivate termination protection on the root stack, then perform the delete operation again. It's strongly recommended that you don't delete nested stacks directly, but only delete them as part of deleting the root stack and all its resources." So the problem with nested stack is only if termination protection is enabled https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-delete-stack-fails

upvoted 2 times

...

Abilash2605

1 year, 10 months ago

Selected Answer: DE

Deleting parent stack will automatically delete nested stack. this article below mentions "Some resources must be empty before they can be deleted. For example, you must delete all objects in an Amazon S3 bucket or remove all instances in an Amazon EC2 security group before you can delete the bucket or security group" https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-delete-stack-fails

upvoted 3 times

...

jipark

1 year, 10 months ago

Selected Answer: BE

why not D : it might cause a resource deletion to fail, but not cause delete stack fail.

upvoted 2 times

...

Christina666

1 year, 11 months ago

Selected Answer: DE

S3, nested stacks

upvoted 1 times

Christina666

1 year, 11 months ago

Check this link, should be BE https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-delete-stack-fails:~:text=but%20not%20deleted-,Delete%20stack%20fails,-To%20resolve%20this

upvoted 3 times

...

Christina666

1 year, 11 months ago

Sorry BE B. One possible cause of the DELETE_FAILED state is that the stack contains nested stacks, and the deletion of the parent stack cannot proceed until the nested stacks are manually deleted first. Nested stacks are separate CloudFormation stacks that are created and managed as part of the resources in the parent stack. When a parent stack is deleted, CloudFormation will attempt to delete the nested stacks, but if there are any issues, the parent stack deletion will fail. E. Another possible cause of the DELETE_FAILED state is that there are Amazon S3 buckets that still contain objects in the stack. If there are objects (files) present in the S3 buckets that were created as part of the CloudFormation stack, the deletion of the stack will fail. CloudFormation cannot delete the S3 buckets that have objects in them, and those buckets must be emptied or manually deleted before the stack deletion can be completed successfully.

upvoted 3 times

...

Gomer

2 years, 1 month ago

Selected Answer: DE

These two quotes sum it up, and were probably were the source of the question: "It's strongly recommended that you don't delete nested stacks directly, but only delete them as part of deleting the root stack and all its resources." "Some resources must be empty before they can be deleted. For example, you must delete all objects in an Amazon S3 bucket or remove all instances in an Amazon EC2 security group before you can delete the bucket or security group." https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-delete-stack-fails

upvoted 4 times

...

braveheart22

2 years, 3 months ago

Yes, D is an option from my point of view, and B as my second option. https://www.quora.com/What-are-some-reasons-that-AWS-CloudFormation-fails-to-delete-a-stack

upvoted 2 times

...

Phinx

2 years, 4 months ago

Selected Answer: DE

D, E is correct

upvoted 4 times

...

SomboonCH

2 years, 4 months ago

Selected Answer: DE

I think DE correct. Ref : https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-delete-stack-fails Some resources must be empty before they can be deleted. For example, you must delete all objects in an Amazon S3 bucket or remove all instances in an Amazon EC2 security group before you can delete the bucket or security group.

upvoted 4 times

...

Gil80

2 years, 4 months ago

Selected Answer: AD

I think D is obvious, but A is not that obvious. According to: https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-stack-delete-failed/ and https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-lambda-resource-delete/ Quote: "To delete a stack for a custom resource that failed to stabilize in the expected amount of time..." That means that there are resources that took too long to terminate which caused the DELEATE_FAILED state.

upvoted 1 times

Phinx

2 years, 4 months ago

you don't need to specify a timeout when deleting a stack.

upvoted 1 times

...