DOP-C02 Practice Question: Match AWS services to SDLC automation descriptions

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 CodeCommit

  Why this is correct

  AWS CodeCommit is a fully managed source-control service that hosts private Git repositories, supporting branches, commits, pull requests, and merge operations with IAM-based access control. It matches the description of a source-control service because it is the central repository where developers store, version, and collaborate on code. Its native Git compatibility and tight AWS integration enable seamless use with other DevOps services, but its core identity is version control, not building or deploying.

• ✗

  AWS CodeBuild

  Why it's wrong here

  AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces build artifacts, but it does not provide version control. It requires source code to be pulled from a repository such as CodeCommit, S3, or GitHub, and then executes build commands in a temporary environment. The act of managing commits, branches, and history is outside CodeBuild's responsibility; it only consumes code from a source-control service.

• ✗

  AWS CodeDeploy

  Why it's wrong here

  AWS CodeDeploy automates the deployment of application code to EC2 instances, Lambda, or on-premises servers, but it does not manage source repositories. It relies on revision locations, such as S3 buckets or GitHub, and coordinates rollout strategies like blue/green or in-place updates. While deployment is a critical SDLC automation stage, the service that holds and versions the code itself is CodeCommit, not CodeDeploy.

• ✗

  AWS CodePipeline

  Why it's wrong here

  AWS CodePipeline is a continuous delivery service that orchestrates the build, test, and deployment stages of an SDLC pipeline, but it does not store or version source code. It references source locations as pipeline stages and passes artifacts between actions, relying on services like CodeCommit for actual source control. CodePipeline’s value is in coordinating the flow from commit to release, not in acting as the repository; that distinction belongs to CodeCommit.

• ✗

  AWS CloudFormation

  Why it's wrong here

  AWS CloudFormation is an infrastructure-as-code service that provisions and manages AWS resources through declarative templates, but it does not manage application source code or version control. While it automates environment creation, it operates at the infrastructure layer, not the SDLC source-control layer. Its purpose is to eliminate manual resource provisioning, not to store or track code changes.

• ✗

  Amazon EventBridge

  Why it's wrong here

  Amazon EventBridge is a serverless event bus that routes events from sources to targets, enabling event-driven architectures, but it has no role in source control or CI/CD execution. It does not store code, build artifacts, or deployment definitions; it merely reacts to state changes. Even when used to trigger pipelines, the actual source-control function is performed by a separate service like CodeCommit, not by EventBridge.

Go deeper

Related to this question