DVA-C02 · Question #747
А 3D printing company has developed a proof-of-concept application that is running on AWS Elastic Beanstalk. The application displays a list of products that are available for 3D printing, in…
The correct answer is C. Rolling with additional batch D. Immutable. Rolling with additional batch: Adds an extra batch of instances during deployment, so existing instances continue serving traffic while the new version is deployed and tested. Immutable: Launches a full set of new instances with the new version alongside the existing ones. Only…
Question
А 3D printing company has developed a proof-of-concept application that is running on AWS Elastic Beanstalk. The application displays a list of products that are available for 3D printing, in addition to any available customizations. When the company deploys new versions of the application, the company wants to ensure that there is no application downtime. Additionally, the application must remain at the same level of server capacity throughout the deployment. Which deployment strategies will meet these requirements? (Choose two.)
Options
- AAll-at-once
- BRolling
- CRolling with additional batch
- DImmutable
- EAll-at-once with additional batch
How the community answered
(37 responses)- A3% (1)
- B8% (3)
- C84% (31)
- E5% (2)
Explanation
Rolling with additional batch: Adds an extra batch of instances during deployment, so existing instances continue serving traffic while the new version is deployed and tested. Immutable: Launches a full set of new instances with the new version alongside the existing ones. Only after the new instances pass health checks are they swapped in, ensuring zero downtime and unchanged capacity.
Community Discussion
No community discussion yet for this question.