DOP-C02 Configuration Management and IaC Practice Question
A company uses AWS CloudFormation to manage infrastructure. They have a production stack that creates an Auto Scaling group. They want to update the launch configuration to use a new Amazon Machine Image (AMI) ID without causing downtime. Which update policy should they set on the Auto Scaling group?
⚠ Common exam trap
The trap here is that 'AutoScalingReplacingUpdate' is a valid CloudFormation update policy, but it replaces the entire Auto Scaling group at once, causing downtime. Candidates may mistakenly choose it thinking it's the only policy that updates launch configurations, but 'AutoScalingRollingUpdate' does so gradually, avoiding downtime.
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
✓
AutoScalingRollingUpdate
The AutoScalingRollingUpdate policy allows CloudFormation to update the Auto Scaling group's launch configuration by gradually replacing instances in batches, ensuring that a minimum number of instances remain in service throughout the update. This prevents downtime by terminating old instances and launching new ones with the updated AMI in a controlled, rolling fashion.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
AutoScalingScheduledAction
Why it's wrong here
AutoScalingScheduledAction suspends scaling processes during a scheduled window; it does not roll instances when a launch configuration changes. It is the correct policy when a recurring event, such as a nightly batch cycle, must not trigger scaling activity.
- ✗
AutoScalingReplacingUpdate
Why it's wrong here
AutoScalingReplacingUpdate replaces the entire Auto Scaling group, which requires the group to be recreated and causes the outage the scenario forbids. It suits stacks where wholesale replacement is acceptable, such as non-production environments tolerating brief interruption.
- ✓
AutoScalingRollingUpdate
Why this is correct
AutoScalingRollingUpdate replaces instances in batches, maintaining a minimum number of healthy instances throughout the update. This satisfies the no-downtime constraint by keeping the Auto Scaling group serving traffic while new AMI-based instances launch and old ones terminate, rather than replacing all instances simultaneously.
- ✗
AutoScalingBatchUpdate
Why it's wrong here
AutoScalingBatchUpdate replaces instances in fixed batches with a pause between them, so capacity drops during each batch and the stack update waits on signals. It suits controlled, staged rollouts where partial capacity loss is acceptable. Here, RollingUpdate with a replacement batch preserves capacity while swapping the AMI, avoiding downtime.
Go deeper
Related to this question
About these practice questions
One of 1,298 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 →
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.