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.

• ✗

  Add a 'post_build' phase that fails the build if tests fail.

  Why it's wrong here

  CodeBuild's post_build phase executes only after the build phase has already completed, so placing test failure detection there cannot prevent the build phase from completing. More importantly, if tests run in post_build and fail, the build will still fail overall, but you have already executed packaging/artifact steps that depend on a successful build. Tests should run in the build phase (or pre_build) so their non-zero exit status aborts the build as early as possible.

• ✗

  Add a 'test' phase in the buildspec before the 'build' phase.

  Why it's wrong here

  CodeBuild currently only supports the lifecycle phases install, pre_build, build, and post_build; a custom 'test' phase is not a valid buildspec phase and will cause a validation/build failure or be ignored, not run your tests. Even if you inserted test commands in pre_build or build before the compile step, moving them earlier does not automatically make failures fatal — the shell command still needs to return a non-zero exit code. The 'test' phase is a concept from other CI systems (e.g., Travis CI), not CodeBuild.

• ✓

  Ensure the buildspec's 'build' phase includes the test command and that the command returns a non-zero exit code on failure.

  Why this is correct

  The correct approach is to run the test command (for example, mvn test or gradle test) inside the build phase of the buildspec. CodeBuild executes each command in a shell where a non-zero exit code causes that phase to be marked failed and the overall build to be FAILED. Because Maven/Gradle test goals already return non-zero when tests fail, this single change ensures the build pipeline stops immediately. Any subsequent build phases, such as post_build artifact packaging, still run, but the final build status will reflect the failure.

• ✗

  Configure the build project to use batch builds.

  Why it's wrong here

  Batch builds are a CodeBuild feature for running multiple builds concurrently — often called build groups — to speed up execution; they do not alter the exit-code semantics of any individual command in the buildspec. Simply enabling batch builds will not run your Java unit tests automatically, nor will it fail the build when tests fail. Each build in a batch still needs an explicit test command in its buildspec that returns non-zero, and a batch can even succeed at the batch level while an individual build fails, depending on the batch configuration.

Go deeper

Related to this question