A company has a serverless application that uses Amazon API Gateway and AWS Lambda functions to expose a RESTful API. The company uses a continuous integration and continuous delivery (CI/CD) workflow to deploy the application to multiple environments. The company wants to implement automated integration tests after deployment. A developer needs to set up the necessary infrastructure and processes to automate the deployment and integration tests for the serverless application.

This option presents the most complete and robust solution for automating a CI/CD workflow for a serverless application on AWS. AWS CodePipeline is the service designed to orchestrate the entire workflow, from source control to deployment and testing. Using AWS CloudFormation (or AWS SAM, which is an extension of CloudFormation) is the standard for defining infrastructure as code. API Gateway stages are the correct mechanism for managing different environments (e.g., dev, test, prod). Finally, AWS CodeBuild is the appropriate service to integrate into the pipeline to run automated builds and integration tests against the newly deployed API Gateway stage, providing a fully automated process.

A: This option is incomplete. While it lists correct components like API Gateway stages, SAM, and CodeBuild, it omits AWS CodePipeline, which is essential for orchestrating the CI/CD workflow.

B: Similar to option A, this option is incomplete. It correctly identifies CloudFormation, API Gateway stages, and CodeBuild but fails to include the AWS CodePipeline service needed to automate and connect these steps.

D: This is a less robust and less automated solution. It lacks a pipeline orchestrator (CodePipeline) and suggests using the AWS CLI for testing, which is less manageable and scalable than using a dedicated service like AWS CodeBuild.

1. AWS CodePipeline User Guide: The "Tutorial: Create a pipeline that deploys an AWS SAM application" demonstrates the standard architecture. It shows a pipeline with a source stage

a build stage using AWS CodeBuild

and a deploy stage using an AWS CloudFormation action. This confirms that CodePipeline is the orchestrator for the workflow. (See: AWS CodePipeline User Guide

Tutorials

"Tutorial: Create a pipeline that deploys an AWS SAM application").

2. AWS API Gateway Developer Guide: The section on "Setting up stages for a REST API" states

"An API stage is a logical reference to a lifecycle state of your API (for example

dev

prod

beta

v2)." This validates the use of stages to represent different application environments. (See: API Gateway Developer Guide

"Develop a REST API"

"Deploy a REST API"

"Setting up stages for a REST API").

3. AWS CodeBuild User Guide: The "How CodeBuild works" section explains that a build project contains the commands to run

which can include compiling code

running tests

and packaging software. This confirms its role in running automated tests within a pipeline. (See: AWS CodeBuild User Guide

"What Is CodeBuild?"

"How CodeBuild works").

4. AWS CloudFormation User Guide: The "What is AWS CloudFormation?" section describes it as the service for modeling and setting up your AWS resources (infrastructure as code)

which is the standard for managing the Lambda and API Gateway resources in a repeatable way. (See: AWS CloudFormation User Guide

"Introduction"

"What is AWS CloudFormation?").