CloudFormation Stack Recovery: Multi-Region, Nested Stacks, and Change Sets
A company is using AWS CloudFormation to deploy a critical application stack. The company wants to ensure that the stack can be recovered quickly in case of a failure. Which THREE strategies should the company implement? (Choose THREE.)
Quick Answer
The correct answer includes using change sets to review changes before updating the stack, as this directly prevents misconfigurations that could trigger a failure during updates. This strategy is part of a broader CloudFormation stack recovery approach that also leverages StackSets for multi-region deployment and nested stacks for modular, reusable templates. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this question tests your ability to combine preventive controls (change sets) with recovery mechanisms (multi-region failover and stack isolation). A common trap is focusing only on reactive recovery, like backups, while ignoring proactive validation. Remember the mnemonic “C-N-R”: Change sets for review, Nested stacks for isolation, and Regional replication via StackSets for failover.
⚠ Common exam trap
A common mix-up: candidates confuse 'recovery' with 'debugging' and select disabling rollback (Option A) thinking it helps preserve resources, but it actually hinders recovery by leaving failed resources in place.
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 StackSets to deploy the stack across multiple Regions.
AWS CloudFormation StackSets allow you to deploy stacks across multiple AWS Regions and accounts from a single template, enabling multi-Region disaster recovery. By deploying the critical application stack in multiple Regions, you can quickly fail over to a secondary Region if the primary fails, meeting the requirement for rapid recovery.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Disable rollback on stack creation failure to preserve resources for debugging.
Why it's wrong here
Disabling rollback can leave resources in an inconsistent state; rollback is safer.
- ✓
Use StackSets to deploy the stack across multiple Regions.
Why this is correct
StackSets enable multi-Region deployment for resilience.
- ✗
Define the entire application in a single CloudFormation template.
Why it's wrong here
A single template is harder to manage and recover; modular approach is better.
- ✓
Use nested stacks to separate components into reusable templates.
Why this is correct
Nested stacks allow independent recovery of components.
- ✓
Use change sets to review changes before updating the stack.
Why this is correct
Change sets allow validation and reduce the risk of failed updates.
Go deeper
Related to this question
About these practice questions
One of 251 original DOP-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on DOP-C02
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 deploy a multi-tier application. During an update, the stack fails and rolls back. The rollback also fails, leaving the stack in UPDATE_ROLLBACK_FAILED state. The operations team needs to resolve this with minimal disruption. What is the MOST efficient approach?
hard- ✓ A.Use the 'ContinueUpdateRollback' API or AWS Management Console to retry the rollback.
- B.Manually modify the resources to match the previous stack state.
- C.Delete the stack and recreate it from the original template.
- D.Execute a change set to update the stack to the desired configuration.
Why A: 'ContinueUpdateRollback' is designed to retry a failed rollback, often fixing transient issues and bringing the stack to a consistent state. Option B is wrong because manually modifying resources is error-prone and not recommended; AWS provides automated rollback tools. Option C is wrong because deleting a stack in UPDATE_ROLLBACK_FAILED state can be problematic and may cause resource loss; it is not the most efficient approach. Option D is wrong because change sets are for updates, not for resolving rollback failures; a change set cannot be applied to a stack in UPDATE_ROLLBACK_FAILED state without first continuing the rollback.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.