SAP-C02 Question 167
Single answerYour company is developing a serverless application that uses AWS Lambda and Amazon API Gateway. The development team wants to implement a CI/CD pipeline to automate the deployment process while ensuring each deployment is validated in a staging environment before going to production. The pipeline must minimize manual steps and support rollback in case of failed deployments. Which solution would best meet these requirements?
- A
Use AWS CodePipeline with separate stages for staging and production, and integrate manual approval steps between the stages.
- B
Use AWS CodePipeline with separate stages for staging and production, and implement automated tests in the staging stage to validate the deployment.
- C
Use AWS Elastic Beanstalk with a single environment to automate the deployment process.
- D
Use AWS CloudFormation with nested stacks to deploy directly to production without a staging environment.
Show answer and explanation
Correct answer: B
Explanation
AWS CodePipeline is the ideal choice for implementing a CI/CD pipeline in this scenario. By creating separate stages for staging and production, and incorporating automated tests in the staging stage, the pipeline ensures deployments are validated before moving to production. CodePipeline also supports rollback mechanisms in case of deployment failures, making it a robust solution for the given requirements.
- A. Incorrect.
This option introduces manual approval steps, which is not aligned with minimizing manual intervention. While it could work, it does not fully meet the requirement of automating the validation process in staging.
- B. Correct.
This option meets all requirements: AWS CodePipeline supports automated deployment, allows separate stages for staging and production, and can run automated tests in the staging environment to validate the deployment. Rollbacks can also be implemented in case of failures.
- C. Incorrect.
AWS Elastic Beanstalk automates deployments but does not natively provide a multi-stage pipeline with automated validation in a separate staging environment. This does not fully meet the requirements of the scenario.
- D. Incorrect.
Deploying directly to production without a staging environment violates the requirement to validate deployments in a staging environment. Additionally, using nested stacks does not provide a CI/CD pipeline with automation or rollback support.