DOP-C02 SDLC Automation 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.

• ✗

  Use Amazon CloudWatch Events to detect new commits and invoke a Lambda function to validate the commit message.

  Why it's wrong here

  While CloudWatch Events (now EventBridge) can be configured to match CodeCommit repository events and route them to Lambda, this approach requires you to manually define an event pattern, set up the rule, and attach the necessary IAM permissions for the rule to invoke the function. CodeCommit's native trigger capability is more direct because it is configured at the repository level specifically for push actions, eliminating the need to parse event envelopes or write custom matching logic. Because the requirement is to validate on every push, using CloudWatch Events adds unnecessary complexity and is not the most efficient solution.

• ✗

  Implement a pre-commit hook in each developer's local repository.

  Why it's wrong here

  Pre-commit hooks are client-side scripts that run only on a developer's local machine before a commit is created; they are not distributed or enforced by CodeCommit. Developers can easily bypass them by using `git commit --no-verify`, and the hooks only exist if each developer manually installs and maintains them. Since the team needs to enforce validation on all pushed commits centrally, this approach provides no guarantee and does not protect the repository from non-compliant messages.

• ✗

  Configure a branch policy on the repository that requires commit message format.

  Why it's wrong here

  CodeCommit branch policies are designed to govern pull requests, such as requiring a minimum number of approvals or restricting who can merge, and they do not inspect the format of commit messages themselves. Commit messages are written at the time of commit and are immutable once pushed; branch policies only act on the PR lifecycle, not on individual commit objects. Therefore, configuring a branch policy will not enforce a commit message format on direct pushes or on commits within a PR.

• ✓

  Create a CodeCommit trigger that invokes an AWS Lambda function on every push to validate commit messages.

  Why this is correct

  A CodeCommit trigger can be set up to invoke an AWS Lambda function whenever a push event occurs, and the event payload includes the full commit list with metadata such as the commit message and author. The Lambda function can programmatically validate each commit message against a required format or regex, and then take action such as sending an alert or invoking a rollback if validation fails. This is a serverless, centrally managed approach that runs on every push and cannot be bypassed by developers, making it the correct solution.