Back to AWS Elastic Beanstalk

Application Versions

5 minutes 5 Questions

Application versions are archives comprising of source codes, dependencies, configuration files, and other components necessary for deploying an application in Elastic Beanstalk. They serve as a snapshot of the app’s state, making it easy to track, manage, and switch between multiple versions. Than…

Test mode:
Start practice test
AWS Certified Solutions Architect - Application Versions Example Questions

Test your knowledge of Application Versions

Question 1

A company wants to test their new application code in Elastic Beanstalk without impacting their production environment. Which deployment policy should the solutions architect select?

Correct Answer: AllAtOnce

The AllAtOnce deployment policy updates all instances simultaneously, which is suitable for testing new application code in a non-production environment. The other policy options are used for controlled, gradual deployments and to avoid downtime in production environments.

Question 2

A company is deploying a new application version to Elastic Beanstalk. They need the ability to rollback quickly to the previous version in case there is a problem with the new release. Which of the following options is the best solution?

Correct Answer: Create a new application version in Elastic Beanstalk and deploy it to the existing environment, allowing for easy rollback.

Creating a new application version in Elastic Beanstalk and deploying it to the existing environment retains the old version, allowing for easy rollback in case of any issues. All the other methods involve manual steps, disrupt the existing environment, or are not suitable for quick rollback.

Question 3

An application runs on AWS Elastic Beanstalk. The team must perform a blue/green deployment with near-zero downtime and fast rollback using native Elastic Beanstalk capabilities. What should the solutions architect do?

Correct Answer: Create a new environment with the new application version, then swap CNAMEs between environments.

Blue/green deployment on Elastic Beanstalk is implemented by running two parallel environments: the current (blue) and a new one (green). You deploy and validate the new version in the green environment and then use Elastic Beanstalk's built-in CNAME swap to shift production traffic instantly with minimal downtime. This also enables immediate rollback by swapping back if needed. Deploying directly to the production environment is an in-place update, not blue/green, and risks downtime. Creating a new application and manually redirecting traffic bypasses Elastic Beanstalk's native CNAME swap and is more error-prone. Using CodeDeploy to update instances behind the load balancer is an in-place deployment approach and not the standard Elastic Beanstalk blue/green pattern.

More Application Versions questions
18 questions (total)
Start 18 question test