SOA-C03 · Question #83
A CloudOps engineer is troubleshooting an AWS CloudFormation stack creation that failed. Before the CloudOps engineer can identify the problem, the stack and its resources are deleted. For future…
The correct answer is B. Set the value of the OnFailure parameter to DO_NOTHING during stack creation. When OnFailure=DO_NOTHING is set in AWS CloudFormation, the stack remains in the “CREATE_FAILED” state instead of being automatically rolled back and deleted. This preserves any successfully created resources, allowing the CloudOps engineer to investigate and correct the issue…
Question
A CloudOps engineer is troubleshooting an AWS CloudFormation stack creation that failed. Before the CloudOps engineer can identify the problem, the stack and its resources are deleted. For future deployments, the CloudOps engineer must preserve any resources that CloudFormation successfully created. What should the CloudOps engineer do to meet this requirement?
Options
- ASet the value of the DisableRollback parameter to False during stack creation.
- BSet the value of the OnFailure parameter to DO_NOTHING during stack creation.
- CSpecify a rollback configuration that has a rollback trigger of DO_NOTHING during stack creation.
- DSet the value of the OnFailure parameter to ROLLBACK during stack creation.
How the community answered
(46 responses)- A4% (2)
- B70% (32)
- C9% (4)
- D17% (8)
Explanation
When OnFailure=DO_NOTHING is set in AWS CloudFormation, the stack remains in the “CREATE_FAILED” state instead of being automatically rolled back and deleted. This preserves any successfully created resources, allowing the CloudOps engineer to investigate and correct the issue without losing existing resources.
Topics
Community Discussion
No community discussion yet for this question.