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…

Question

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

• A
  4% (1)
• C
  4% (1)
• D
  93% (26)

Explanation

There appears to be an error in the provided answer key - the correct answer is actually B, not D.

OnFailure=DO_NOTHING leaves the stack in a CREATE_FAILED state while keeping all successfully created resources intact, which is exactly what the administrator needs for troubleshooting.

Why each option is right or wrong:

• A (DisableRollback = False): False is the default, meaning rollback is enabled - resources get deleted on failure. Setting it to True would preserve resources, but False does the opposite.
• B (OnFailure = DO_NOTHING) - Correct: The stack halts in a failed state without deleting any already-created resources, allowing the administrator to inspect what succeeded and what failed.
• C (rollback trigger of DO_NOTHING): DO_NOTHING is not a valid rollback trigger type. CloudFormation rollback triggers use CloudWatch Alarms, so this option describes a configuration that doesn't exist.
• D (OnFailure = ROLLBACK): This triggers rollback, which deletes all resources created during the failed stack deployment - the exact behavior the administrator is trying to avoid.

Memory tip: Think of DO_NOTHING literally - CloudFormation does nothing (no cleanup, no deletion) when it fails, leaving the forensic evidence behind. ROLLBACK cleans up after itself like it never happened.

Note for exam prep: If your source marks D as correct, it contains an error. Verify against the AWS CloudFormation CreateStack documentation - OnFailure=DO_NOTHING is the documented way to preserve resources on failure.

No community discussion yet for this question.