Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam SOA-C02 Topic 12 Question 98 Discussion

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

A company uses AWS Cloud Formation to deploy its infrastructure. The company recently retired an application. A cloud operations engineer initiates CloudFormation stack deletion, and the stack gets stuck in DELETE FAILED status.

A SysOps administrator discovers that the stack had deployed a security group. The security group is referenced by other security groups in the environment. The SysOps administrator needs to delete the stack without affecting other applications.

Which solution will meet these requirements m the MOST operationally efficient manner?

Show Suggested Answer Hide Answer
Suggested Answer: C

Retain the Security Group:

When deleting a CloudFormation stack, you can specify resources to be retained instead of deleted.

Steps:

Go to the AWS Management Console.

Navigate to CloudFormation and select the stack.

Choose to delete the stack.

In the deletion options, specify that the security group should be retained.

This will delete the stack but keep the security group, ensuring no impact on other applications.


Contribute your Thoughts:

Val
3 months ago
Drift detection? That's like trying to catch a moving train with your bare hands. Option B is the clear winner here.
upvoted 0 times
...
Lettie
3 months ago
Haha, I bet the cloud operations engineer is regretting that 'retired' application right about now. Option B is the way to go!
upvoted 0 times
Tammara
2 months ago
Definitely! Option B seems like the best solution to avoid affecting other applications.
upvoted 0 times
...
Alaine
2 months ago
Yeah, that stack deletion issue sounds like a headache.
upvoted 0 times
...
Demetra
3 months ago
Definitely! Option B seems like the most efficient solution to fix it.
upvoted 0 times
...
Lajuana
3 months ago
Yeah, that stack deletion issue sounds like a headache.
upvoted 0 times
...
...
Serina
3 months ago
I think option D might be the most efficient way to handle this situation.
upvoted 0 times
...
Felix
4 months ago
I'm not sure, option B also sounds like a good solution.
upvoted 0 times
...
Bernardine
4 months ago
Option A sounds like a lot of extra work. Why create a new security group when you can just delete the one that's causing the issue?
upvoted 0 times
Francisca
3 months ago
I agree, creating a change set to delete the security group sounds efficient.
upvoted 0 times
...
Cristal
4 months ago
Option B seems like the most direct solution.
upvoted 0 times
...
...
Margarita
4 months ago
I agree with Viola, creating a new security group seems like the safest option.
upvoted 0 times
...
Viola
4 months ago
I think option A is the best solution.
upvoted 0 times
...
Daisy
4 months ago
I'm not sure about option C. Wouldn't that cause issues with other applications referencing the security group?
upvoted 0 times
Glory
3 months ago
C: That makes sense. Let's go with either option A or B to ensure we don't cause issues with other applications.
upvoted 0 times
...
Johnetta
4 months ago
B: I agree. Option B might also work by using a CloudFormation change set to delete the security group.
upvoted 0 times
...
Lauran
4 months ago
A: Option A seems like the best choice. By creating a new security group with identical rules, we can avoid affecting other applications.
upvoted 0 times
...
...
Claribel
4 months ago
Option B seems the most efficient. Deleting the stack with the security group retained is the way to go.
upvoted 0 times
Hubert
3 months ago
Yeah, that way we can ensure the other applications are not affected.
upvoted 0 times
...
Samira
3 months ago
I think creating a change set is the safest way to go.
upvoted 0 times
...
An
4 months ago
Agreed, it's important to delete the security group separately.
upvoted 0 times
...
Cassie
4 months ago
Option B seems like the best choice.
upvoted 0 times
...
...

Save Cancel