Question 526 of 1,740
Configuration Management and IaCmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to use the `aws cloudformation continue-update-rollback` command with the `--resources-to-skip` parameter to skip the RDS DB instance, then apply a change set with the desired parameter change. This is correct because when a CloudFormation update rollback failure occurs on a resource that cannot be reverted—like an RDS DB instance with a custom parameter group—the stack becomes stuck in `UPDATE_ROLLBACK_FAILED` state. The `continue-update-rollback` command with `--resources-to-skip` tells CloudFormation to ignore that specific resource during rollback, allowing the stack to reach `UPDATE_ROLLBACK_COMPLETE` without manual deletion or data loss. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your understanding of rollback failure recovery and the distinction between stack-level and resource-level rollback behavior. A common trap is attempting to delete the stack or manually revert the parameter group, which risks data loss or downtime. Memory tip: think "skip the stuck resource, then re-apply the fix"—the stack must first complete its rollback before you can update it again.

DOP-C02 Configuration Management and IaC Practice Question

This DOP-C02 practice question tests your understanding of configuration management and iac. 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 manages its infrastructure using AWS CloudFormation. They have a production stack that includes an Amazon RDS Multi-AZ DB instance. The stack was created using the 'aws cloudformation create-stack' command with default settings. The DB instance uses a custom DB parameter group. A DevOps engineer needs to modify a parameter in the DB parameter group and update the stack. The engineer updates the template to change the parameter value and runs 'aws cloudformation update-stack'. The update fails with a 'ROLLBACK_IN_PROGRESS' status. The engineer checks the CloudFormation console and sees that the DB instance was successfully modified, but the stack is rolling back. The rollback fails because the DB instance cannot be reverted to the original parameter value. The stack is now in 'UPDATE_ROLLBACK_FAILED' state. What should the engineer do to resolve this situation and apply the desired parameter change?

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 'aws cloudformation continue-update-rollback' command with the '--resources-to-skip' parameter to skip the DB instance, allowing the stack to reach 'UPDATE_ROLLBACK_COMPLETE'. Then apply a change set with the desired parameter change.

Option B is correct because when a CloudFormation stack is in UPDATE_ROLLBACK_FAILED state, the `continue-update-rollback` command with `--resources-to-skip` allows you to skip the resource that cannot be rolled back (the RDS DB instance with the custom parameter group). This moves the stack to UPDATE_ROLLBACK_COMPLETE, after which you can apply a change set with the desired parameter change. This approach avoids manual intervention or stack deletion while preserving the modified DB instance.

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.

  • Run 'aws cloudformation update-stack' again with the original template to revert the changes.

    Why it's wrong here

    You cannot update a stack that is in 'UPDATE_ROLLBACK_FAILED' state; you must first complete the rollback.

  • Use the 'aws cloudformation continue-update-rollback' command with the '--resources-to-skip' parameter to skip the DB instance, allowing the stack to reach 'UPDATE_ROLLBACK_COMPLETE'. Then apply a change set with the desired parameter change.

    Why this is correct

    This is the recommended approach to recover from a failed rollback without deleting the stack.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Revert the parameter value manually in the RDS console and then resume the rollback.

    Why it's wrong here

    Manual intervention may work, but the stack remains in 'UPDATE_ROLLBACK_FAILED' state; it is better to use CloudFormation's built-in recovery.

  • Delete the stack and recreate it with the updated template.

    Why it's wrong here

    Deleting a production stack with a Multi-AZ DB instance is risky and may cause data loss.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may think manual reversion or stack deletion is required, but CloudFormation provides a built-in recovery mechanism (`continue-update-rollback`) that avoids downtime and data loss.

Detailed technical explanation

How to think about this question

CloudFormation's `continue-update-rollback` with `--resources-to-skip` is designed for scenarios where a resource's state cannot be reverted (e.g., a DB parameter group change that is irreversible). Under the hood, CloudFormation marks the skipped resource as successfully rolled back and updates the stack status accordingly, allowing subsequent updates. This is critical in production environments where RDS Multi-AZ instances must remain available and data integrity is paramount.

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?

Configuration Management and IaC — This question tests Configuration Management and IaC — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use the 'aws cloudformation continue-update-rollback' command with the '--resources-to-skip' parameter to skip the DB instance, allowing the stack to reach 'UPDATE_ROLLBACK_COMPLETE'. Then apply a change set with the desired parameter change. — Option B is correct because when a CloudFormation stack is in UPDATE_ROLLBACK_FAILED state, the `continue-update-rollback` command with `--resources-to-skip` allows you to skip the resource that cannot be rolled back (the RDS DB instance with the custom parameter group). This moves the stack to UPDATE_ROLLBACK_COMPLETE, after which you can apply a change set with the desired parameter change. This approach avoids manual intervention or stack deletion while preserving the modified DB instance.

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

Keep practising

More DOP-C02 practice questions

Last reviewed: Jun 11, 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.