The answer is to use continue-update-rollback after resolving the underlying issue or specifying resources to skip. This is correct because when a CloudFormation stack update fails and enters UPDATE_ROLLBACK_FAILED, the rollback itself has been blocked, often by a resource that cannot be deleted or modified due to permissions, dependencies, or configuration conflicts. The continue-update-rollback command allows you to either skip the problematic resource or retry the rollback after fixing the root cause, which is identified by reviewing the stack events for detailed error messages. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this scenario tests your ability to troubleshoot failed stack operations and understand that simply deleting the stack is not the correct first step—many candidates mistakenly choose to delete the stack immediately, but that can orphan resources. A common trap is overlooking the stack events as the primary diagnostic tool. Memory tip: think "Rollback Rescue"—fix the blocker, then continue the rollback, never force-delete without checking events first.
SOA-C02 Deployment, Provisioning, and Automation Practice Question
This SOA-C02 practice question tests your understanding of deployment, provisioning, and automation. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A CloudFormation stack update fails and enters UPDATE_ROLLBACK_FAILED. Which two actions are appropriate next steps? (Choose 2.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Review stack events to identify the resource that blocked rollback.
Option A is correct because when a CloudFormation stack update fails and enters UPDATE_ROLLBACK_FAILED, the stack events provide detailed error messages for each resource that failed during rollback. Reviewing these events is essential to identify the specific resource that blocked the rollback, such as a resource that could not be deleted or updated due to permissions, dependencies, or configuration issues. This diagnosis is the first step before attempting a continue-update-rollback operation.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Review stack events to identify the resource that blocked rollback.
Why this is correct
Stack events show the specific resource and failure reason.
Related concept
Read the scenario before looking for a memorised answer.
✓
Use continue-update-rollback after resolving the underlying issue or specifying resources to skip when appropriate.
Why this is correct
This is the documented recovery path for UPDATE_ROLLBACK_FAILED.
Related concept
Read the scenario before looking for a memorised answer.
✗
Delete the CloudFormation service role from IAM.
Why it's wrong here
Removing permissions is likely to make recovery harder.
✗
Rename the stack to force rollback completion.
Why it's wrong here
Stack names cannot be used to force rollback recovery.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think deleting the service role or renaming the stack are valid recovery actions, but AWS CloudFormation requires explicit rollback continuation or manual intervention via the continue-update-rollback API, not workarounds that break IAM or naming conventions.
Detailed technical explanation
How to think about this question
The UPDATE_ROLLBACK_FAILED state occurs when CloudFormation attempts to revert a failed update but encounters a resource that cannot be rolled back (e.g., a resource that was deleted externally or has a deletion policy that prevents removal). The continue-update-rollback command allows you to either skip the problematic resource (using the --resources-to-skip parameter) or resolve the underlying issue (e.g., manually fixing permissions) and then retry the rollback. Under the hood, CloudFormation uses a state machine that tracks each resource's transition; if a resource fails during rollback, the entire stack is stuck until the issue is addressed.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Deployment, Provisioning, and Automation — This question tests Deployment, Provisioning, and Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Review stack events to identify the resource that blocked rollback. — Option A is correct because when a CloudFormation stack update fails and enters UPDATE_ROLLBACK_FAILED, the stack events provide detailed error messages for each resource that failed during rollback. Reviewing these events is essential to identify the specific resource that blocked the rollback, such as a resource that could not be deleted or updated due to permissions, dependencies, or configuration issues. This diagnosis is the first step before attempting a continue-update-rollback operation.
What should I do if I get this SOA-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company is using AWS CloudFormation to manage infrastructure. A recent stack update failed, and the SysOps administrator needs to roll back to the previous known good state. However, the stack is in UPDATE_ROLLBACK_FAILED state. What should the administrator do to recover the stack?
hard
✓ A.Use the ContinueUpdateRollback API or AWS Management Console to resume the rollback after addressing the failure cause
B.Delete the stack and recreate it from the previous template
C.Contact AWS Support to enable automatic rollback recovery
D.Execute another stack update with the same parameters to overwrite the failed state
Why A: Option B is correct because when a stack is in UPDATE_ROLLBACK_FAILED, you can continue the rollback by fixing the underlying issue (e.g., deleting a resource that cannot be rolled back) and then executing ContinueUpdateRollback. Option A is wrong because deleting the stack would remove all resources, causing data loss. Option C is wrong because updating the stack again may not resolve the rollback failure and could compound errors. Option D is wrong because CloudFormation does not have an automatic rollback recovery feature; manual intervention is required.
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SOA-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 SOA-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.