DOP-C02 Question 67
Select 2A company is building a multi-tier web application. The frontend UI is deployed on Amazon EC2 instances, the backend microservices are containerized and deployed on Amazon ECS, and the serverless components are implemented using AWS Lambda. As a DevOps Engineer, you need to design a CI/CD pipeline for seamless deployment across all these platforms. Which combination of deployment strategies should you choose to ensure minimal downtime and rollback support?
- A
Use a rolling deployment strategy for Amazon EC2 instances, a blue/green deployment strategy for Amazon ECS, and a canary deployment for AWS Lambda.
- B
Use a canary deployment strategy for Amazon EC2 instances, a rolling update strategy for Amazon ECS, and an all-at-once deployment for AWS Lambda.
- C
Use a blue/green deployment strategy for Amazon EC2 instances, a rolling deployment strategy for Amazon ECS, and a gradual deployment for AWS Lambda using AWS CodeDeploy.
- D
Use an all-at-once deployment strategy for Amazon EC2 instances, a blue/green deployment strategy for Amazon ECS, and a linear deployment for AWS Lambda.
- E
Use a rolling deployment strategy for Amazon EC2 instances, a canary deployment strategy for Amazon ECS, and a blue/green deployment for AWS Lambda.
Show answer and explanation
Correct answers: A, C
Explanation
The correct answer includes deployment strategies that align with best practices for each platform. Rolling deployments are ideal for EC2 instances as they ensure minimal downtime by upgrading instances in batches. Blue/green deployments for ECS allow safe rollback by routing traffic between old and new environments. For Lambda, canary or gradual deployments are recommended as they provide traffic-shifting capabilities and help test changes incrementally in production.
- A. Correct.
This option is correct because rolling deployments minimize downtime for Amazon EC2, blue/green provides a safe rollback mechanism for Amazon ECS, and canary deployment for Lambda ensures changes are gradually tested.
- B. Incorrect.
This option is incorrect because a canary deployment for Amazon EC2 is uncommon and lacks the efficiency of rolling deployments for EC2, and an all-at-once deployment for Lambda can lead to potential issues in production.
- C. Correct.
This option is correct because blue/green deployment for EC2 ensures safe rollbacks, rolling updates for ECS are efficient for containerized workloads, and gradual deployment for Lambda via AWS CodeDeploy is a best practice.
- D. Incorrect.
This option is incorrect because an all-at-once strategy for EC2 introduces high risk, and linear deployment for Lambda lacks the gradual traffic-shifting benefits of canary or gradual deployments.
- E. Incorrect.
This option is incorrect because canary deployment for ECS is less commonly used compared to rolling or blue/green, and rolling deployment for Lambda is not supported natively.