How to Investigate a CloudFormation ROLLBACK_COMPLETE State
A DevOps engineer notices that a CloudFormation stack update fails with the error: 'UPDATE_ROLLBACK_FAILED'. The stack is in a state where some resources were updated, but others failed to update. The engineer needs to fix the stack and complete the update. What should the engineer do FIRST?
⚠ Common exam trap
The trap is reaching for destructive or workaround actions (delete and recreate, force a new update) instead of the documented recovery API, ContinueUpdateRollback, which is the only supported first step in UPDATE_ROLLBACK_FAILED.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Manually correct the resources that are preventing rollback, then use 'ContinueUpdateRollback'
When a CloudFormation stack update fails and rollback also fails, the stack enters UPDATE_ROLLBACK_FAILED. The documented recovery path is to manually fix the underlying resource issue that is blocking rollback, then call ContinueUpdateRollback to resume the rollback and return the stack to a stable state. This is the first corrective action before any further updates can be attempted.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add a new resource to the stack to force a new update
Why it's wrong here
Adding a resource does not clear UPDATE_ROLLBACK_FAILED; CloudFormation refuses further updates until the rollback is completed via ContinueUpdateRollback. Forcing a new update by adding resources belongs to routine stack evolution, not recovery from a rollback that could not finish.
- ✓
Manually correct the resources that are preventing rollback, then use 'ContinueUpdateRollback'
Why this is correct
UPDATE_ROLLBACK_FAILED means CloudFormation cannot roll back because a resource is in an unusable state. The engineer must first manually repair those resources outside CloudFormation, then run ContinueUpdateRollback so the stack can resume rolling back before the update is retried.
- ✗
Submit another stack update with the original template to overwrite the changes
Why it's wrong here
CloudFormation rejects updates while the stack sits in UPDATE_ROLLBACK_FAILED, so resubmitting the original template cannot overwrite the partial changes. Reapplying a template is the normal route to revert drift on a healthy stack, not to escape a failed rollback.
- ✗
Delete the stack and recreate it with the same template
Why it's wrong here
Deleting the stack discards the resources CloudFormation still tracks, including those already updated, and cannot resolve the failed rollback state; the engineer must first run ContinueUpdateRollback with skipped resources. Recreating from the template suits deliberately rebuilding a stack, not recovering one stuck mid-update.
Go deeper
Related to this question
About these practice questions
This SAP-C02 question is part of Courseiva's 984-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.