- A
Implement image vulnerability scanning in the CI/CD pipeline
Scanning can fail the build if critical vulnerabilities are found, preventing deployment.
- B
Regularly update base images
Why wrong: Updating is important but does not prevent use of out-of-date or vulnerable images if not enforced.
- C
Only allow signed images to be pulled from a trusted registry
Image signing ensures integrity and authenticity; only approved images are deployed.
- D
Use network segmentation to isolate production containers
Why wrong: Network isolation limits blast radius but does not prevent vulnerable images from being deployed.
- E
Run all containers as non-root users
Why wrong: This is a defense-in-depth measure but does not prevent deployment of vulnerable images.
CCSP Cloud Application Security Practice Question
This CCSP practice question tests your understanding of cloud application security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
During a security audit, a cloud application is found to have numerous container images with critical vulnerabilities. The DevOps team wants to prevent vulnerable images from being deployed to production. Which two controls should be implemented? (Select TWO)
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
Implement image vulnerability scanning in the CI/CD pipeline
Option A is correct because integrating image vulnerability scanning into the CI/CD pipeline ensures that every container image is automatically checked for known Common Vulnerabilities and Exposures (CVEs) before it can be promoted to production. This shift-left approach blocks vulnerable images at build time, preventing them from ever reaching the production environment. Option C is correct because enforcing signed images from a trusted registry (e.g., using Docker Content Trust or Notary) cryptographically verifies the image's integrity and origin, ensuring only authorized, non-tampered images are deployed.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Implement image vulnerability scanning in the CI/CD pipeline
Why this is correct
Scanning can fail the build if critical vulnerabilities are found, preventing deployment.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Regularly update base images
Why it's wrong here
Updating is important but does not prevent use of out-of-date or vulnerable images if not enforced.
- ✓
Only allow signed images to be pulled from a trusted registry
Why this is correct
Image signing ensures integrity and authenticity; only approved images are deployed.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use network segmentation to isolate production containers
Why it's wrong here
Network isolation limits blast radius but does not prevent vulnerable images from being deployed.
- ✗
Run all containers as non-root users
Why it's wrong here
This is a defense-in-depth measure but does not prevent deployment of vulnerable images.
Common exam traps
Common exam trap: answer the scenario, not the keyword
ISC2 often tests the distinction between preventive controls (like scanning and signing) that stop vulnerable images from being deployed versus mitigative controls (like network segmentation or non-root users) that reduce the impact after deployment, leading candidates to select the latter as a substitute for prevention.
Detailed technical explanation
How to think about this question
Image vulnerability scanning tools like Trivy, Clair, or Anchore compare the package manifests (e.g., dpkg, RPM, Alpine APK) against CVE databases (e.g., NVD, Red Hat OVAL) to identify known vulnerabilities. Signed images leverage cryptographic signatures (e.g., using TUF/The Update Framework) where the registry stores a signature manifest; the container runtime (e.g., Docker Engine with content trust enabled) will refuse to pull unsigned images, providing a non-repudiation guarantee. In a real-world scenario, a CI/CD pipeline with scanning can fail the build if a critical CVE (e.g., CVE-2024-21626 in runc) is found, while signed images prevent supply-chain attacks like the 2021 Codecov breach.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Cloud Application Security — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Application Security practice questions
Targeted practice on this topic area only
- →
All CCSP questions
504 questions across all exam domains
- →
Certified Cloud Security Professional CCSP study guide
Full concept coverage aligned to exam objectives
- →
CCSP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CCSP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cloud Application Security practice questions
Practise CCSP questions linked to Cloud Application Security.
Cloud Security Operations practice questions
Practise CCSP questions linked to Cloud Security Operations.
Legal, Risk and Compliance practice questions
Practise CCSP questions linked to Legal, Risk and Compliance.
Cloud Concepts, Architecture and Design practice questions
Practise CCSP questions linked to Cloud Concepts, Architecture and Design.
Cloud Platform and Infrastructure Security practice questions
Practise CCSP questions linked to Cloud Platform and Infrastructure Security.
Cloud Data Security practice questions
Practise CCSP questions linked to Cloud Data Security.
CCSP fundamentals practice questions
Practise CCSP questions linked to CCSP fundamentals.
CCSP scenario practice questions
Practise CCSP questions linked to CCSP scenario.
CCSP troubleshooting practice questions
Practise CCSP questions linked to CCSP troubleshooting.
Practice this exam
Start a free CCSP practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CCSP question test?
Cloud Application Security — This question tests Cloud Application Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Implement image vulnerability scanning in the CI/CD pipeline — Option A is correct because integrating image vulnerability scanning into the CI/CD pipeline ensures that every container image is automatically checked for known Common Vulnerabilities and Exposures (CVEs) before it can be promoted to production. This shift-left approach blocks vulnerable images at build time, preventing them from ever reaching the production environment. Option C is correct because enforcing signed images from a trusted registry (e.g., using Docker Content Trust or Notary) cryptographically verifies the image's integrity and origin, ensuring only authorized, non-tampered images are deployed.
What should I do if I get this CCSP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 30, 2026
This CCSP practice question is part of Courseiva's free ISC2 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 CCSP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.