Elastic Beanstalk Rolling Deployment: Zero Downtime Updates
A developer is using AWS Elastic Beanstalk to deploy a web application. The developer needs to update the environment's configuration to use a larger instance type. What is the most efficient way to apply this change with minimal 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
✓
Update the environment configuration through the Elastic Beanstalk console or CLI, and use a rolling update strategy to apply the change to instances in batches.
Elastic Beanstalk supports rolling updates, which allow you to change the instance type by updating instances in batches, minimizing downtime. Options B, C, and D are incorrect: B involves blue/green deployment, which is more complex and not the most efficient for a simple configuration change; C is wrong because directly modifying the Auto Scaling group launch configuration may be overwritten by Elastic Beanstalk and does not leverage Elastic Beanstalk's managed rolling update; D causes full downtime by terminating and recreating the environment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Update the environment configuration through the Elastic Beanstalk console or CLI, and use a rolling update strategy to apply the change to instances in batches.
Why this is correct
This is the recommended and most efficient method for updating configuration parameters like instance types. Elastic Beanstalk manages the underlying infrastructure, and a rolling update strategy ensures that instances are replaced in batches, maintaining application availability throughout the process. The environment remains operational, serving traffic from the healthy instances while others are updated.
- ✗
Perform a blue/green deployment by creating a new environment with the larger instance type, then swap the environment URLs.
Why it's wrong here
While technically feasible to achieve the desired instance type change, blue/green deployments are primarily designed for deploying new application versions with zero downtime. Using it for a simple instance type configuration change is overkill and less efficient, as it involves provisioning an entirely new, duplicate environment and then swapping DNS, incurring unnecessary resource costs and management overhead compared to an in-place rolling update.
- ✗
Modify the Auto Scaling group launch configuration directly to use the larger instance type, then manually terminate each instance.
Why it's wrong here
Directly modifying the Auto Scaling group's launch configuration or template outside of Elastic Beanstalk's control is highly discouraged. Elastic Beanstalk maintains a desired state for its environments, and manual changes to underlying resources like the Auto Scaling group can lead to configuration drift, inconsistencies, and unexpected behavior, potentially causing the environment to become unstable or revert to its previous state.
- ✗
Terminate the current environment and create a new one with the larger instance type.
Why it's wrong here
Terminating the existing Elastic Beanstalk environment completely removes all running instances and associated resources, resulting in significant application downtime. Creating a new environment from scratch, even with the desired instance type, requires a full redeployment and re-initialization, which is an unacceptable approach for production applications where continuous availability is critical.
Go deeper
Related to this question
About these practice questions
One of 1,135 original DVA-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 DVA-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 web application. The developer has updated the application code and wants to deploy the new version with a rolling deployment strategy to minimize downtime. Which configuration should the developer use?
medium- ✓ A.Set the deployment policy to 'Rolling'
- B.Set the deployment policy to 'Immutable'
- C.Set the deployment policy to 'All at once'
- D.Set the deployment policy to 'Blue/green'
Why A: The 'Rolling' deployment policy in AWS Elastic Beanstalk updates instances in batches, moving the new application version into a subset of instances while keeping the rest serving traffic, which minimizes downtime by ensuring capacity is never fully reduced. This is the correct choice for a rolling update that balances speed and availability without requiring a full parallel environment.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DVA-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 DVA-C02 exam.