Question 1,092 of 247
Elastic Beanstalk Rolling Update for Instance Type — Minimize Downtime
A company uses AWS Elastic Beanstalk for application deployments. The administrator needs to update the environment's configuration to use a larger instance type. Which method should be used to minimize downtime?
Quick Answer
The answer is to perform a rolling update based on health. This method minimizes downtime by replacing instances in batches, only moving to the next batch after the new instances pass health checks, ensuring the application remains available throughout the elastic beanstalk instance type update. For the AWS Certified SysOps Administrator Associate SOA-C02 exam, this question tests your understanding of deployment policy trade-offs: rolling updates prioritize availability over speed, while immutable updates launch a full new environment and swap, which can cause a brief cutover gap. A common trap is choosing immutable updates because they are faster, but they introduce a momentary outage during the DNS swap. Remember the mnemonic "Roll for Reliability, Immutable for Speed" — when the question explicitly says "minimize downtime," always choose the rolling update based on health.
⚠ Common exam trap
Candidates often confuse 'immutable update' (Option B) as the best minimal-downtime method, but for a simple instance type change, a rolling update based on health is more appropriate because it avoids the overhead of provisioning a full parallel environment and the potential for brief traffic interruption during the swap.
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
✓
Perform a rolling update based on health.
A rolling update based on health (Option D) is the correct method to minimize downtime when updating an instance type in Elastic Beanstalk. This approach updates instances in batches, replacing them with the new instance type only after the previous batch passes health checks, ensuring application availability throughout the process. Elastic Beanstalk's rolling update with health-based batching terminates and launches instances incrementally, avoiding full environment disruption.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Terminate all instances and let the Auto Scaling group launch new ones.
Why it's wrong here
This causes full downtime.
- ✗
Perform an immutable update.
Why it's wrong here
Immutable update is used for environment configuration changes? Actually, for configuration changes, rolling updates are recommended. Immutable updates are for application versions.
- ✗
Clone the environment with the new configuration and swap URLs.
Why it's wrong here
Cloning creates a new environment, not an update.
- ✓
Perform a rolling update based on health.
Why this is correct
Rolling updates replace instances in batches, minimizing downtime.
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 →
Same concept, more angles
1 more way this is tested on SOA-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 Elastic Beanstalk to deploy a Python web application. The administrator needs to update the environment's configuration to use a larger instance type. What is the correct way to perform this update with minimal downtime?
easy- ✓ A.Use the Elastic Beanstalk console to change the instance type and select a rolling update policy.
- B.Create a new Elastic Beanstalk environment with the larger instance type and swap the environment URLs.
- C.Use the Elastic Beanstalk console to change the instance type and apply the change immediately.
- D.Terminate all instances and launch new ones with the larger instance type.
Why A: Elastic Beanstalk supports rolling updates, which allow you to change the instance type without downtime by updating instances in batches. Option B is incorrect because creating a new environment and swapping URLs is more complex and can still cause disruption. Option C is incorrect because applying the change immediately without a rolling update policy would cause downtime. Option D is incorrect because terminating all instances would cause downtime.
Last reviewed: Jul 4, 2026
This SOA-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 SOA-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.