hardMultiple Select
CV0-004 Practice Question: Which THREE are common tasks in a CI/CD pipeline?…
Which THREE are common tasks in a CI/CD pipeline? (Select THREE.)
⚠ Common exam trap
CompTIA often tests the distinction between manual, human-in-the-loop activities (like code review or handwritten notes) and fully automated, scripted steps that are essential to a CI/CD pipeline, leading candidates to mistakenly include manual tasks as pipeline tasks.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Source code checkout from version control
Option C is correct because a CI/CD pipeline begins by checking out source code from a version control system such as Git, which triggers the automated build and test stages. Option D is correct because the CD portion of the pipeline automates deployment to staging or production environments, often using tools like Jenkins, GitLab CI, or Argo CD. Option E is correct because automated testing (unit, integration, and similar tests) is a core CI activity that validates each code change before it progresses further in the pipeline. Options A and B are not correct: manual code review, while valuable, is a human process rather than an automated pipeline task, and handwritten deployment notes are the opposite of the automation that CI/CD pipelines are designed to provide.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manual code review by a senior developer
Why it's wrong here
Manual review by a person blocks the pipeline and cannot run per commit, so it is not an automated CI/CD task. It is tempting because peer review genuinely improves quality, and it would be correct as a pull-request gate, but pipeline tasks are automated build, test and deployment stages.
- ✗
Handwritten notes for deployment steps
Why it's wrong here
Handwritten notes cannot be executed by automation, so they cannot form a pipeline task; CI/CD requires machine-readable, version-controlled definitions such as pipeline-as-code. Documentation has value for audit trails or runbooks, but it sits outside automated build, test and deploy stages.
- ✓
Source code checkout from version control
Why this is correct
Source code checkout retrieves the repository revision that triggers the pipeline, supplying the artefact for subsequent build and test stages. It is a standard opening task in CI/CD workflows, distinct from deployment, monitoring or infrastructure provisioning activities.
- ✓
Deployment to a staging or production environment
Why this is correct
Publishing built artefacts into a staging or production environment is the delivery stage that closes the CI/CD loop. It satisfies the pipeline's requirement to move validated code toward end users, distinct from build and test stages that precede it.
- ✓
Automated testing (unit, integration, etc.)
Why this is correct
Automated testing executes unit, integration and other suites on every commit, giving fast feedback before artefacts advance. It satisfies the pipeline's need to validate code changes continuously, catching regressions early rather than after deployment. This makes it a standard CI/CD task alongside building and deploying.
Go deeper
Related to this question
About these practice questions
One of 834 original CV0-004 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CV0-004 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CV0-004 exam.