SAP-C02 Question 151
Single answerA company is planning to deploy a mission-critical application on AWS. The application requires zero downtime during updates and must support rollback in case of issues. Additionally, the deployment process should minimize manual intervention. Which deployment strategy should you recommend?
- A
Blue/Green Deployment using AWS CodeDeploy
- B
In-place Deployment using AWS Elastic Beanstalk
- C
Immutable Deployment using AWS CloudFormation
- D
Rolling Deployment using Auto Scaling Groups
Show answer and explanation
Correct answer: A
Explanation
The Blue/Green Deployment strategy is ideal for this scenario because it ensures zero downtime by deploying the new application version in a separate green environment. If any issues occur, traffic can be easily switched back to the blue environment, enabling a quick rollback. This approach also minimizes manual intervention when using AWS CodeDeploy.
- A. Correct.
Blue/Green Deployment using AWS CodeDeploy is the most suitable choice for achieving zero downtime and rollback capabilities. This strategy creates a separate green environment for the new version while keeping the blue environment (current version) intact, allowing seamless switching or rollback.
- B. Incorrect.
In-place Deployment using AWS Elastic Beanstalk requires instances to be updated in place, which may cause application downtime during the update process.
- C. Incorrect.
Immutable Deployment using AWS CloudFormation creates entirely new resources for the stack, which can be used for testing and rollback, but it might not guarantee zero downtime for mission-critical applications.
- D. Incorrect.
Rolling Deployment using Auto Scaling Groups updates instances in batches, which might lead to partial downtime or degraded performance during the deployment process.