Explanation:
By default, AWS CloudFormation rolls back the stack and deletes any created resources if stack creation fails. To troubleshoot, you need to preserve the resources to see their state. Setting the OnFailure parameter to DO_NOTHING (or using the rollback-on-failure flag set to false in the console) ensures that CloudFormation leaves the resources intact instead of deleting them. Option A is incorrect because setting DisableRollback to False is the default behavior (enabling rollback). Option D is also the default behavior.
Ultimate access to all questions.
Question 12: A SysOps administrator is troubleshooting an AWS CloudFormation stack creation that failed. Before the SysOps administrator can identify the problem, the stack and its resources are deleted. For future deployments, the SysOps administrator must preserve any resources that CloudFormation successfully created.
What should the SysOps administrator 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
No comments yet.