CV0-004 Deployment Practice Question
A DevOps team is implementing a CI/CD pipeline using Jenkins. They want to ensure that code is automatically built, tested, and deployed to a staging environment before manual approval for production. Which stage should include the deployment to staging?
⚠ Common exam trap
CV0-004 often tests whether candidates conflate 'Verify' (testing) with 'Deploy' (releasing to an environment), causing them to place staging deployment in the Verify stage because staging is used for verification.
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
✓
Deploy
In a Jenkins CI/CD pipeline, the Deploy stage is responsible for taking the built and verified artifact and releasing it to an environment — in this case, the staging environment. The pipeline flow is typically Source → Build → Test/Verify → Deploy (staging) → Manual Approval → Deploy (production). Placing staging deployment in the Deploy stage correctly separates it from build and test activities.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Build
Why it's wrong here
The Build stage compiles and packages artefacts; it does not deploy them to an environment. Deployment to staging belongs in a later stage after build and test succeed. Build is tempting because it is the first stage that produces a deployable artefact, which in a build-only pipeline would be the endpoint.
- ✓
Deploy
Why this is correct
The Deploy stage performs the actual release of built artefacts to the staging environment, so it is where staging deployment belongs. Build compiles, test validates, and manual approval gates production, matching the pipeline's required sequence.
- ✗
Source
Why it's wrong here
Source-stage triggers merely fetch code from the repository; they execute no build, test or deploy actions, so staging deployment cannot occur there. It is tempting because source checkout is the pipeline's first automated step, and in a build-only job it would correctly precede compilation.
- ✗
Verify
Why it's wrong here
Verify runs tests and quality gates against built artefacts; it does not push them to staging. Staging deployment is a distinct deploy stage occurring after verification. Verify is tempting because testing must precede staging, so it is the last stage before deployment in a test-only pipeline.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
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.