Question #1037
A company is deploying a new version of their application on AWS Elastic Beanstalk. The deployment must ensure zero downtime and gradually shift a predefined portion of user traffic to the new version over a specified time frame for performance evaluation. Which deployment strategy satisfies these requirements?
Rolling
Traffic-splitting
In-place
Immutable
Explanation
The Traffic-splitting deployment strategy (B) is correct because it allows Elastic Beanstalk to route a predefined portion of user traffic to the new application version using Elastic Load Balancer (ELB). This ensures zero downtime by keeping both old and new instances running simultaneously while gradually shifting traffic over time.
Other options are incorrect because:
- A. Rolling: Replaces instances in batches but does not split traffic between versions; traffic shifts only after batches are updated.
- C. In-place: Updates existing instances, causing downtime during deployment.
- D. Immutable: Deploys new instances alongside old ones but replaces all traffic at once after validation, not gradually.
Key Points:
- Traffic-splitting uses ELB to split traffic between versions.
- Zero downtime is achieved by maintaining both versions during deployment.
- Gradual traffic shift aligns with performance evaluation requirements.
Answer
The correct answer is: B