- A
Configure an 'UpdateWaitCondition' in the CloudFormation template to pause the stack update until a healthy signal is received from the new instances.
Wait conditions allow you to verify that new instances are healthy before proceeding.
- B
Add a custom resource that triggers an AWS Lambda function to take a snapshot of the database before the update.
Why wrong: Database snapshotting is not directly related to application downtime during a stack update.
- C
Ensure that the Auto Scaling group spans at least three Availability Zones to distribute instances.
Why wrong: Multiple AZs improve fault tolerance but do not directly control update behavior.
- D
Set the Auto Scaling group's UpdatePolicy to 'AutoScalingRollingUpdate' with a 'BatchSize' of 1 and 'MinInstancesInService' equal to the desired capacity.
This ensures only one instance is replaced at a time, maintaining capacity.
- E
Define a lifecycle hook for the Auto Scaling group that delays instance termination until the new instance is fully registered and healthy with the load balancer.
Lifecycle hooks allow you to perform custom actions before termination, ensuring no traffic loss.
Quick Answer
The answer is to define a lifecycle hook for the Auto Scaling group that delays instance termination until the new instance is fully registered and healthy with the load balancer. This works because the lifecycle hook pauses the termination of the old instance during a rolling update, giving the new instance time to pass the Application Load Balancer’s health checks and begin receiving traffic before the old one is removed. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this concept tests your understanding of how to orchestrate zero-downtime CloudFormation updates for Auto Scaling behind an ALB, often paired with an UpdateWaitCondition to signal CloudFormation to proceed only after healthy registration. A common trap is assuming that simply updating the launch configuration or using a shorter health check interval alone prevents downtime, but without the lifecycle hook, the old instance can be terminated before the new one is ready, causing a gap in service. Memory tip: think “hook before you cook” — the lifecycle hook keeps the old instance “on the hook” until the new one is fully cooked and serving traffic.
DOP-C02 Configuration Management and IaC Practice Question
This DOP-C02 practice question tests your understanding of configuration management and iac. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
Which THREE actions should be taken to ensure that an AWS CloudFormation stack update does not cause downtime for a production application that runs on an Auto Scaling group behind an Application Load Balancer? (Select THREE.)
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
Configure an 'UpdateWaitCondition' in the CloudFormation template to pause the stack update until a healthy signal is received from the new instances.
Option A is correct because an 'UpdateWaitCondition' in a CloudFormation template can pause the stack update until a healthy signal is received from the new instances. This ensures that the update proceeds only after the new instances have passed health checks, preventing premature traffic routing and potential downtime.
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.
- ✓
Configure an 'UpdateWaitCondition' in the CloudFormation template to pause the stack update until a healthy signal is received from the new instances.
Why this is correct
Wait conditions allow you to verify that new instances are healthy before proceeding.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Add a custom resource that triggers an AWS Lambda function to take a snapshot of the database before the update.
Why it's wrong here
Database snapshotting is not directly related to application downtime during a stack update.
- ✗
Ensure that the Auto Scaling group spans at least three Availability Zones to distribute instances.
Why it's wrong here
Multiple AZs improve fault tolerance but do not directly control update behavior.
- ✓
Set the Auto Scaling group's UpdatePolicy to 'AutoScalingRollingUpdate' with a 'BatchSize' of 1 and 'MinInstancesInService' equal to the desired capacity.
Why this is correct
This ensures only one instance is replaced at a time, maintaining capacity.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Define a lifecycle hook for the Auto Scaling group that delays instance termination until the new instance is fully registered and healthy with the load balancer.
Why this is correct
Lifecycle hooks allow you to perform custom actions before termination, ensuring no traffic loss.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse general high-availability practices (like multi-AZ distribution) with specific update-time actions that prevent downtime, or they may think database snapshots are relevant to instance-level availability during a stack update.
Detailed technical explanation
How to think about this question
The 'AutoScalingRollingUpdate' policy with 'BatchSize' of 1 and 'MinInstancesInService' equal to desired capacity ensures that only one instance is replaced at a time, and the desired number of instances remain in service throughout the update. Lifecycle hooks, combined with a 'CONTINUE' or 'ABANDON' action, can delay instance termination until the new instance is fully registered and healthy with the ALB, preventing traffic gaps. Under the hood, CloudFormation uses the Auto Scaling group's health check grace period and ELB health checks to coordinate the rolling update, and lifecycle hooks integrate with Amazon SNS or SQS to signal completion.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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.
- →
Configuration Management and IaC — study guide chapter
Learn the concepts, then practise the questions
- →
Configuration Management and IaC practice questions
Targeted practice on this topic area only
- →
All DOP-C02 questions
1,740 questions across all exam domains
- →
AWS Certified DevOps Engineer Professional DOP-C02 study guide
Full concept coverage aligned to exam objectives
- →
DOP-C02 practice test guide
How to use practice tests most effectively before exam day
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.
Configuration Management and IaC practice questions
Practise DOP-C02 questions linked to Configuration Management and IaC.
Resilient Cloud Solutions practice questions
Practise DOP-C02 questions linked to Resilient Cloud Solutions.
Monitoring and Logging practice questions
Practise DOP-C02 questions linked to Monitoring and Logging.
Incident and Event Response practice questions
Practise DOP-C02 questions linked to Incident and Event Response.
Security and Compliance practice questions
Practise DOP-C02 questions linked to Security and Compliance.
SDLC Automation practice questions
Practise DOP-C02 questions linked to SDLC Automation.
DOP-C02 fundamentals practice questions
Practise DOP-C02 questions linked to DOP-C02 fundamentals.
DOP-C02 scenario practice questions
Practise DOP-C02 questions linked to DOP-C02 scenario.
DOP-C02 troubleshooting practice questions
Practise DOP-C02 questions linked to DOP-C02 troubleshooting.
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: Configure an 'UpdateWaitCondition' in the CloudFormation template to pause the stack update until a healthy signal is received from the new instances. — Option A is correct because an 'UpdateWaitCondition' in a CloudFormation template can pause the stack update until a healthy signal is received from the new instances. This ensures that the update proceeds only after the new instances have passed health checks, preventing premature traffic routing and potential downtime.
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 →
Keep practising
More DOP-C02 practice questions
- A company uses AWS CodePipeline with a multi-branch strategy. A new feature branch triggers a pipeline that runs unit te…
- A development team uses AWS CodeBuild to compile a Java application and run unit tests. The build takes 30 minutes, but…
- A company uses AWS CodePipeline with multiple stages: Source (Amazon S3), Build (AWS CodeBuild), and Deploy (AWS CodeDep…
- A company uses AWS CodeCommit for source control. Developers frequently push large binary files (e.g., compiled JARs) to…
- An organization uses AWS CodePipeline to orchestrate deployments to multiple environments (dev, test, prod). Each enviro…
- A company uses AWS Key Management Service (KMS) to encrypt data at rest in Amazon S3. The security team wants to ensure…
Last reviewed: Jun 24, 2026
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.