Explanation:
By default, AWS CloudFormation deletes all resources created during a failed stack creation (rollback). To troubleshoot, you can set the OnFailure parameter to DO_NOTHING. This causes CloudFormation to preserve the state and the resources that were successfully created before the failure occurred, allowing the engineer to inspect the resources and logs. Setting DisableRollback to True achieves the same effect, but the option provided in the list is OnFailure set to DO_NOTHING.
Ultimate access to all questions.
Question #8
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?
A
Set the value of the DisableRollback parameter to False during stack creation.
B
Set the value of the OnFailure parameter to DO_NOTHING during stack creation.
C
Specify a rollback configuration that has a rollback trigger of DO_NOTHING during stack creation.
D
Set the value of the OnFailure parameter to ROLLBACK during stack creation.
E
None
F
None
No comments yet.