Explanation:
When an AWS CloudFormation stack fails to delete due to a dependency issue (like a security group being referenced by resources outside the stack), the stack enters the DELETE_FAILED state. The most operationally efficient way to resolve this without affecting the dependent applications is to issue the delete stack command again and select the option to retain the problematic resource (the security group). This bypasses the deletion of the security group, allowing the rest of the stack to be successfully deleted while keeping the security group intact for the other applications.
Ultimate access to all questions.
A company uses AWS CloudFormation 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 in the MOST operationally efficient manner?
A
Create a new security group that has a different name. Apply identical rules to the new security group. Replace all other security groups that reference the new security group. Delete the stack.
B
Create a CloudFormation change set to delete the security group. Deploy the change set.
C
Delete the stack again. Specify that the security group be retained.
D
Perform CloudFormation drift detection. Delete the stack.
No comments yet.