The correct answer involves three key steps: checking the CloudFormation stack events for error messages, reviewing the specific resource status in the console, and using the `--retain-resources` parameter to preserve resources that failed to delete during rollback. When a stack update enters `UPDATE_ROLLBACK_IN_PROGRESS`, CloudFormation automatically attempts to revert changes, but a rollback itself can fail if a resource cannot be deleted or reverted—this is where stack events become critical, as they log the exact resource and reason for the failure. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your ability to differentiate between troubleshooting tools: change sets are for previewing updates, not diagnosing failures, and `DescribeStackResource` gives resource-level details but not the root cause. A common trap is confusing rollback failure investigation with update previewing. Memory tip: think "Events first, retain last"—always start with stack events to pinpoint the error, then use `--retain-resources` to save stuck resources during rollback.
DOP-C02 Incident and Event Response Practice Question
This DOP-C02 practice question tests your understanding of incident and event response. 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 company uses AWS CloudFormation to manage infrastructure. A stack update fails with the error: 'UPDATE_ROLLBACK_IN_PROGRESS'. The DevOps engineer needs to investigate the cause. Which THREE steps should the engineer take? (Choose THREE.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Review the CloudFormation console to identify which resource failed.
Options A, D, and E are correct. Option A: The CloudFormation console shows the specific resource that caused the failure. Option D: Stack events provide detailed status and error messages. Option E: The '--retain-resources' parameter can preserve resources that failed to delete during rollback. Option B is wrong because change sets are used to preview changes before execution, not to troubleshoot failures. Option C is wrong because DescribeStackResource returns specific resource details but not the overall failure cause; also, it's not a primary troubleshooting step.
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.
✗
Create a change set to see what changes were attempted.
Why it's wrong here
Change sets are for previewing changes, not for troubleshooting failures.
✗
Use the 'describe-stack-resource' AWS CLI command to get the resource status.
Why it's wrong here
This provides resource status but not the root cause of the failure.
✓
Review the CloudFormation console to identify which resource failed.
Why this is correct
The console highlights the failed resource.
Related concept
Read the scenario before looking for a memorised answer.
✓
Use the '--retain-resources' option to preserve resources that failed to delete.
Why this is correct
This can be used to retain resources during rollback to prevent data loss.
Related concept
Read the scenario before looking for a memorised answer.
✓
Check the CloudFormation stack events for error messages.
Why this is correct
Stack events contain the error details for the failed resource.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which DOP-C02 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Incident and Event Response — This question tests Incident and Event Response — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Review the CloudFormation console to identify which resource failed. — Options A, D, and E are correct. Option A: The CloudFormation console shows the specific resource that caused the failure. Option D: Stack events provide detailed status and error messages. Option E: The '--retain-resources' parameter can preserve resources that failed to delete during rollback. Option B is wrong because change sets are used to preview changes before execution, not to troubleshoot failures. Option C is wrong because DescribeStackResource returns specific resource details but not the overall failure cause; also, it's not a primary troubleshooting step.
What should I do if I get this DOP-C02 question wrong?
Identify which DOP-C02 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 uses AWS CloudFormation to manage infrastructure. During a deployment, a stack update fails and the stack is in ROLLBACK_IN_PROGRESS state. The DevOps engineer needs to investigate the failure while preserving the resources that were created before the failure. What should the engineer do?
medium
A.Delete the stack to start fresh.
B.Use the 'describe-stack-events' API to view the error and then manually fix the issue.
C.Call the 'cancel-update' API to stop the rollback and keep the current state.
✓ D.Use the 'continue-update-rollback' API with the 'resources-to-skip' parameter to skip the failing resource.
Why D: Option D is correct because using 'continue update rollback' with the 'resources to skip' parameter allows the engineer to skip specific resources and preserve them while continuing the rollback for others. Option A is wrong because deleting the stack removes all resources. Option B is wrong because 'describe stack events' provides information but does not prevent the rollback from continuing. Option C is wrong because 'cancel update' is not a valid operation; CloudFormation does not support canceling a rollback.
Variation 2. A company uses AWS CloudFormation to manage infrastructure. During an incident, a stack update fails with the error 'The following resource(s) failed to create: [AWS::RDS::DBInstance]'. Which AWS service should the engineer use to view detailed error messages for the failed resource creation?
easy
A.AWS Config timeline
✓ B.AWS CloudFormation console Events tab
C.AWS Service Catalog
D.AWS CloudTrail event history
Why B: Option A is correct because CloudFormation events provide detailed error messages for resource creation failures. Option B (CloudTrail) records API calls but not CloudFormation-specific resource errors. Option C (Config) is for configuration compliance. Option D (Service Catalog) is for product provisioning, not troubleshooting stack failures.
Variation 3. A company uses AWS CloudFormation to manage infrastructure. An engineer notices that a stack update has failed, leaving the stack in a ROLLBACK_IN_PROGRESS state. Which TWO actions should the engineer take to investigate and resolve the issue?
medium
A.Manually stop the rollback and continue with the update
B.Re-launch the stack with the same template
✓ C.View the stack events in the CloudFormation console to see the specific error message
D.Delete the stack and re-launch it
✓ E.Review the change set that was applied during the update
Why C: Options B and D are correct. The engineer should view the stack events to see the specific error, then review the change set to understand what changes were attempted. Option A is wrong because deleting the stack would lose resources; C is wrong because re-launching may repeat the error; E is wrong because stopping rollback is not recommended without understanding the issue.
Variation 4. A company uses AWS CloudFormation to manage infrastructure. A stack update fails with a 'ROLLBACK_IN_PROGRESS' status. The DevOps engineer needs to investigate the failure. Which TWO actions should the engineer take?
easy
A.Review AWS CloudTrail logs for the 'UpdateStack' API call.
✓ B.Review the 'Stack Events' tab in the CloudFormation console to see the specific error messages.
C.Check the 'Rollback triggers' configuration for the stack.
✓ D.Examine the stack's 'Template' and 'Parameters' to ensure they are correct.
E.Create a Change Set to see the proposed changes before re-attempting the update.
Why B: Option A is correct because the 'Stack Events' tab shows detailed error messages for each resource. Option D is correct because viewing the stack's template and parameters helps identify misconfigurations. Option B is wrong because rollback triggers are for deletion, not update failures. Option C is wrong because CloudTrail logs API calls, not template validation errors. Option E is wrong because Change Sets are used for reviewing changes before execution, not for debugging failed updates.
Variation 5. A company uses AWS CloudFormation to manage infrastructure. A recent stack update failed with the error 'UPDATE_ROLLBACK_FAILED'. The stack is now in a 'UPDATE_ROLLBACK_FAILED' state, and the engineer needs to fix the stack. What is the correct course of action?
hard
A.Contact AWS Support to fix the stack
B.Delete the stack and recreate it
C.Submit another stack update with the desired configuration
✓ D.Continue the rollback using the 'ContinueUpdateRollback' API
Why D: Option A is correct because when a rollback fails, you can continue the rollback (which may skip resources that failed to roll back) or perform a stack operation to fix. Option B is wrong because deleting may not be possible if the stack is stuck. Option C is wrong because you cannot update a stack in rollback failed state without first continuing rollback. Option D is wrong because support can help but is not the direct action.
Variation 6. An organization uses AWS CloudFormation to manage infrastructure. During an incident, a stack update fails with 'UPDATE_ROLLBACK_FAILED' status. The engineer needs to bring the stack to a consistent state without losing data. What is the BEST approach?
hard
✓ A.Use the 'ContinueUpdateRollback' API to skip the resource that caused the failure.
B.Create a new stack from the same template and migrate resources.
C.Manually correct the resource configuration that caused the failure, then perform a stack update.
D.Delete the stack and then recreate it from the same template.
Why A: The 'ContinueUpdateRollback' API is the best approach because it allows the stack to resume the rollback process, skipping the resource that caused the failure, and bringing the stack to a consistent 'UPDATE_ROLLBACK_COMPLETE' state without manual intervention or data loss. This API is specifically designed for the 'UPDATE_ROLLBACK_FAILED' status, enabling you to skip resources that cannot be rolled back (e.g., due to a non-reversible change) while preserving the rest of the stack's state.
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 DOP-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 DOP-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.