Back to AWS Elastic Beanstalk

Deployment Strategies

5 minutes 5 Questions

AWS Elastic Beanstalk provides different deployment strategies that enable businesses to deploy their applications efficiently and with minimal downtime. These deployment strategies are designed to cater to various requirements, such as Blue/Green deployments, in-place updates, and rolling deployme…

Test mode:
Start practice test
AWS Certified Solutions Architect - Deployment Strategies Example Questions

Test your knowledge of Deployment Strategies

Question 1

A team needs an out-of-the-box blue/green deployment feature that lets them clone an environment and swap the production CNAME between environments to minimize downtime. Which AWS service provides this natively?

Correct Answer: AWS Elastic Beanstalk

AWS Elastic Beanstalk natively supports blue/green deployments by allowing you to clone an environment and perform a CNAME (URL) swap to shift production traffic between the blue and green environments with minimal downtime. This is an out-of-the-box capability in Elastic Beanstalk. By contrast, Amazon ECS and AWS Lambda can perform blue/green style deployments but typically rely on AWS CodeDeploy or alias routing for traffic shifting, and Amazon EC2 Auto Scaling is not a deployment service and does not provide a built-in blue/green mechanism.

Question 2

You need to deploy a serverless application consisting of multiple functions based on event triggers. What deployment strategy should you use?

Correct Answer: AWS Lambda with Amazon API Gateway

AWS Lambda provides serverless infrastructure and can be triggered through Amazon API Gateway, making it the most suitable option for serverless applications with event-based functions. The other options are either not serverless or do not address the event-based nature of the application.

Question 3

A company is deploying a traditional web application that runs on Amazon EC2 instances and cannot be refactored to serverless at this time. The application must be highly available within a single AWS Region, remain accessible during the loss of an Availability Zone, and scale automatically with demand. Which deployment strategy best meets these requirements?

Correct Answer: Deploy a Multi-AZ architecture with Auto Scaling and an Elastic Load Balancer.

Deploying EC2 instances across multiple Availability Zones behind an Elastic Load Balancer with an Auto Scaling group provides fault tolerance and high availability within a single Region. If an instance or an entire AZ fails, the load balancer routes traffic only to healthy instances in other AZs, and Auto Scaling replaces unhealthy instances and scales capacity based on demand. A single-AZ Elastic Beanstalk deployment is not fault-tolerant. A generic single-Region EC2 deployment that does not explicitly span multiple AZs does not meet the AZ-failure tolerance requirement. Using AWS Lambda behind a load balancer can provide high availability, but it does not meet the stated constraint that the application must run on EC2 and cannot be refactored to serverless.

More Deployment Strategies questions
18 questions (total)
Start 18 question test