AWS Certified Developer – Associate (DVA-C02) — Question 339

A developer is building a new containerized application by using AWS Copilot. The developer uses the AWS Copilot command line interface (CLI) to deploy the application during development. The developer committed the application code to a new AWS CodeCommit repository. The developer must create an automated deployment process before releasing the new application to production.

What should the developer do to meet these requirements in the MOST operationally efficient way?

Answer options

• A. Create a buildspec file that invokes the AWS Copilot CLI commands to build and deploy the application. Use the AWS Copilot CLI to create an AWS CodePipeline that uses the CodeCommit repository in the source stage and AWS CodeBuild in the build stage.
• B. Use the AWS Serverless Application Model (AWS SAM) CLI to bootstrap and initialize an AWS CodePipeline configuration. Use the CodeCommit repository as the source. Invoke the AWS Copilot CLI to build and deploy the application.
• C. Use the AWS Copilot CLI to define the AWS Copilot pipeline and to deploy the AWS CodePipeline. Select CodeCommit as the source for the AWS CodePipeline.
• D. Define an AWS CloudFormation template for an AWS CodePipeline with CodeCommit as the source. Configure the template as an AWS Copilot CLI add-on. Use the AWS Copilot CLI to deploy the application.

Correct answer: C

Explanation

AWS Copilot natively supports the creation and deployment of continuous delivery pipelines through commands like 'copilot pipeline init' and 'copilot pipeline deploy', making Option C the most operationally efficient approach. Other options like using AWS SAM (Option B) or writing custom CloudFormation templates (Option D) introduce unnecessary complexity and overhead. Option A is incorrect because AWS Copilot handles the generation of the buildspec and pipeline configuration automatically without requiring manual buildspec creation.