KCNA Cloud Native Application Delivery Practice Question
In a CI/CD pipeline, what is the difference between continuous delivery and continuous deployment?
⚠ Common exam trap
KCNA often tests the delivery-vs-deployment distinction by swapping their definitions — the key discriminator is the manual approval gate in continuous delivery, which candidates frequently misattribute to continuous deployment.
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
✓
Continuous delivery requires manual approval for production deployment; continuous deployment automates it
Continuous delivery automates the build, test, and staging deployment so that every change is release-ready, but the final push to production requires a manual approval or button click. Continuous deployment goes one step further and automatically releases every validated change to production without human intervention. The distinction is purely about whether production deployment is gated by a human.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Continuous delivery requires manual approval for production deployment; continuous deployment automates it
Why this is correct
Continuous delivery stops short of production, requiring a manual approval gate before release; continuous deployment removes that gate and pushes every passing change automatically. This distinction satisfies the stem's requirement to differentiate the two practices by their production approval step.
- ✗
Continuous delivery automatically deploys to production; continuous deployment does not
Why it's wrong here
This reverses the definitions: continuous delivery stops short of production, requiring manual approval, while continuous deployment releases automatically. It is tempting because both terms sound similar, and continuous delivery would be correct where a human gate before production release is mandated.
- ✗
There is no difference; the terms are used interchangeably
Why it's wrong here
Continuous delivery leaves the final production release as a manual approval gate, whereas continuous deployment automates that promotion once automated tests pass. Treating them as synonyms ignores that distinction, which the exam tests directly. The terms overlap in tooling, which is why the confusion arises, but the deployment trigger differs.
- ✗
Continuous deployment runs tests; continuous delivery does not
Why it's wrong here
Both models run automated tests; the difference lies in whether production promotion is automatic or gated by human approval. Continuous deployment pushes every passing build to production, while continuous delivery stops short of that. Testing is common to both, so attributing test execution to only one misstates the pipeline design.
Visual reference
About these practice questions
Courseiva writes every KCNA question from scratch — 930 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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 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.