Courseiva

KCNA Cloud Native Application Delivery Practice Question

What is the purpose of container image scanning in a CI/CD pipeline?

⚠ Common exam trap

KCNA often tests the confusion between image scanning (security vulnerability detection) and other pipeline steps like image optimization, tagging, or registry storage — candidates may pick a plausible-sounding but non-security answer.

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

✓

To identify security vulnerabilities in the image

Container image scanning in a CI/CD pipeline analyzes the image layers for known security vulnerabilities (CVEs) in OS packages, libraries, and application dependencies. It is a core DevSecOps practice that shifts security left, catching issues before the image is deployed to production.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    To ensure the image is stored in a registry

    Why it's wrong here

    Registry storage is handled by push and pull operations, not scanning; scanning inspects layers for known vulnerabilities and misconfigurations. It is tempting because scanning occurs around image publication, but its purpose is identifying security flaws before deployment, not confirming registry presence.

  • ✗

    To measure the image size and optimize it

    Why it's wrong here

    Scanning inspects packages and layers for known vulnerabilities; size measurement is a separate build-metric concern. It is tempting because both run during pipeline stages, but scanning's purpose is detecting exploitable components so vulnerable images are blocked before reaching production.

  • ✗

    To verify the image tag follows naming conventions

    Why it's wrong here

    Tag naming conventions are enforced by policy or linting rules, not scanning. Image scanning inspects layer contents for known CVEs and misconfigurations, so a compliant tag name passes regardless of embedded vulnerabilities. Naming validation would be the right control when governance requires standardised tags before registry push.

  • ✓

    To identify security vulnerabilities in the image

    Why this is correct

    Scanning inspects image layers and installed packages against vulnerability databases, flagging known CVEs before deployment. This directly satisfies the pipeline's need to catch insecure dependencies and base images early, preventing vulnerable artefacts from reaching the cluster.

About these practice questions

One of 930 original KCNA 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 →

How Courseiva writes practice questions · Editorial policy

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 CNCF exam blueprint

This KCNA practice question is part of Courseiva's free CNCF 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 KCNA exam.