Question 921 of 1,740
Incident and Event ResponsemediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is the `--disable-rollback` option (or `DisableRollback` in the template). This feature instructs CloudFormation to halt the stack update at the point of failure, leaving all resources—including the failed ones—intact rather than automatically reverting to the last known good state. By disabling rollback, engineers can retain the failed resources for direct debugging, log analysis, and root cause investigation without the stack being torn down. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this concept tests your understanding of recovery and troubleshooting workflows during stack updates; a common trap is confusing `--disable-rollback` with `--on-failure DO_NOTHING`, which only applies to stack creation, not updates. Remember the memory tip: "Disable rollback to keep the wreckage"—if you need to inspect what broke, prevent the cleanup.

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 deploy infrastructure. During an incident, a stack update fails with a stack rollback. The engineer needs to prevent the stack from rolling back on future failures and instead retain the resources for debugging. Which CloudFormation feature should the engineer use?

Question 1mediummultiple choice
Full question →

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

Use the '--disable-rollback' option when updating the stack

The `--disable-rollback` option (or `DisableRollback` in the CloudFormation template) instructs AWS CloudFormation to leave the stack in its current state (with the failed resources intact) instead of automatically rolling back to the last known good state. This allows engineers to retain the resources for debugging without the stack being torn down on failure.

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.

  • Enable drift detection on the stack

    Why it's wrong here

    Drift detection identifies differences, not rollback prevention.

  • Use the '--disable-rollback' option when updating the stack

    Why this is correct

    This retains resources for debugging.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use AWS CloudFormation StackSets to deploy the stack

    Why it's wrong here

    StackSets are for multi-account deployments.

  • Create a change set before updating instead of direct update

    Why it's wrong here

    Change sets preview changes but don't prevent rollback.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse change sets (which preview changes) with the ability to prevent rollback, or mistakenly think drift detection or StackSets can alter rollback behavior, when only the `--disable-rollback` flag directly controls whether resources are retained on failure.

Detailed technical explanation

How to think about this question

When `--disable-rollback` is used, CloudFormation sets the stack status to `UPDATE_FAILED` and leaves all successfully created or updated resources in place, while resources that failed to create/update remain in a failed state. This is particularly useful during incident response because you can inspect the failed resource (e.g., an EC2 instance or an RDS database) directly in the AWS console, capture logs, or run diagnostics without the stack automatically deleting them. Note that subsequent stack operations (e.g., another update or deletion) may still require manual cleanup of these retained resources.

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 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 exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related DOP-C02 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DOP-C02 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DOP-C02 question test?

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: Use the '--disable-rollback' option when updating the stack — The `--disable-rollback` option (or `DisableRollback` in the CloudFormation template) instructs AWS CloudFormation to leave the stack in its current state (with the failed resources intact) instead of automatically rolling back to the last known good state. This allows engineers to retain the resources for debugging without the stack being torn down on failure.

What should I do if I get this DOP-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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

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.