200-901 Application Deployment and Security Practice Question
In a CI/CD pipeline using Jenkins, which stage is typically executed immediately after the build stage to ensure code quality before deployment?
⚠ Common exam trap
Cisco often tests the distinction between unit tests and integration tests in a CI/CD pipeline, where candidates mistakenly think integration tests come immediately after build because they involve 'testing code' broadly, but the correct order is unit tests first to validate individual modules before combining them.
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
✓
Unit test
In a Jenkins CI/CD pipeline, the build stage compiles the code and produces artifacts. Immediately after the build, unit tests are executed to validate individual components in isolation, catching defects early before proceeding to integration or deployment stages. This aligns with the principle of 'shift-left' testing, where quality gates are applied as early as possible.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Unit test
Why this is correct
Unit tests execute immediately after the build stage, validating individual code units before the artefact progresses toward deployment. This enforces the code-quality gate described in the stem, catching defects earlier than integration or deployment stages would.
- ✗
Deploy to production
Why it's wrong here
Deploying to production releases the build to end users, skipping any quality gate, which contradicts the requirement to validate code before deployment. It is tempting as the pipeline's end goal, and it is correct only after testing stages have passed.
- ✗
Integration test
Why it's wrong here
Integration tests exercise assembled components against dependencies, not the static code quality checks the stem asks for immediately after build. It is tempting because it is a verification stage, but it is correct when validating component interactions rather than inspecting source quality.
- ✗
Artifact publication
Why it's wrong here
Artifact publication archives the built output for later retrieval; it performs no code inspection, so it cannot verify quality. It is tempting because it follows the build naturally, and it is correct when the pipeline must persist binaries for downstream deployment stages.
Go deeper
Related to this question
About these practice questions
One of 975 original 200-901 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 200-901 practice question is part of Courseiva's free Cisco 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 200-901 exam.