hardMultiple ChoiceObjective-mapped
200-901 Practice Question: A security policy requires that all container…
A security policy requires that all container images in a registry are scanned for vulnerabilities before deployment. Which approach best integrates this into a CI/CD pipeline without slowing down the pipeline?
⚠ Common exam trap
Cisco often tests the concept of 'shifting left' security — candidates mistakenly think scanning after pushing (Option B) is acceptable because it blocks deployment, but the trap is that the policy requires scanning before deployment, not before push, and Option B still allows vulnerable images to reside in the registry.
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
✓
Build the image, scan it locally, and if it passes, push it to the registry; run scans in parallel with the build if possible.
It shifts the vulnerability scan left in the pipeline: the image is built and scanned locally before being pushed to the registry. If the scan passes, the image is pushed; if it fails, the pipeline stops early, avoiding the overhead of pushing a vulnerable image and then rebuilding. This approach minimizes pipeline latency by running scans in parallel with the build where possible, ensuring security without blocking the deployment flow.
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 the image, push it, then scan it, and if vulnerabilities are found, rebuild and repush.
Why it's wrong here
This doubles build time and registry usage; scanning should occur before push.
- ✗
Run the vulnerability scan on the image after pushing to the registry and block deployment if critical vulnerabilities are found.
Why it's wrong here
Post-push scanning delays the pipeline; the image is already in the registry.
- ✓
Build the image, scan it locally, and if it passes, push it to the registry; run scans in parallel with the build if possible.
Why this is correct
Local scanning before push catches vulnerabilities early and does not delay the pipeline if done in parallel.
- ✗
Scan the source code dependencies before building the image, and skip image scanning.
Why it's wrong here
Source scanning does not cover vulnerabilities introduced in the base image or during build.
Go deeper
Related to this question
About these practice questions
One of 989 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.