DVA-C02 Development with AWS Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  AWS CodeBuild

  Why this is correct

  AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces deployable artifacts. Within an AWS CodePipeline, CodeBuild is typically configured as a build or test stage, executing unit tests, integration tests, or even security scans defined in a `buildspec.yml` file. This ensures that code quality and functionality are validated thoroughly before the application proceeds to subsequent deployment stages, making it the correct choice for automating the testing phase.

• ✗

  AWS CodeCommit

  Why it's wrong here

  AWS CodeCommit is a secure, highly scalable, and fully managed source control service that hosts private Git repositories. Its primary function is to store and manage source code, binaries, and other development assets, providing robust version control and collaboration features for development teams. While CodeCommit serves as the initial source stage for a CodePipeline, it does not possess any capabilities to execute tests or build processes on the stored code itself.

• ✗

  AWS CloudFormation

  Why it's wrong here

  AWS CloudFormation is an infrastructure as code (IaC) service that enables developers to define and provision AWS infrastructure resources in a declarative manner using templates. It automates the creation, update, and deletion of AWS resources, ensuring consistent and repeatable environment setups. CloudFormation's role is to manage the underlying infrastructure for applications, such as EC2 instances or databases, rather than to execute application-level tests or perform code compilation.

• ✗

  AWS CodeDeploy

  Why it's wrong here

  AWS CodeDeploy is a fully managed deployment service that automates software deployments to various compute services, including Amazon EC2, AWS Fargate, AWS Lambda, and on-premises servers. Its core purpose is to reliably and consistently release application revisions to target environments. Although CodeDeploy can incorporate lifecycle hooks for validation *during* a deployment, it is not designed to run comprehensive pre-deployment unit or integration tests on the application code itself, which is a distinct build and test phase.