KCNA Container Orchestration Practice Question
Which of the following correctly describes the concept of 'immutable infrastructure' in the context of container orchestration?
⚠ Common exam trap
The trap is confusing immutability with 'never changing' or 'never rebooting' — candidates may pick option C because they think immutable means static, but the correct definition is about replacement rather than in-place modification.
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
✓
Infrastructure components are recreated from a known good state rather than modified
Immutable infrastructure means that instead of modifying running servers or containers, you replace them entirely with new instances built from a known good image. In container orchestration, this is achieved by building a new container image, deploying it as a new pod/replica set, and tearing down the old ones. This eliminates configuration drift and makes rollbacks deterministic.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Infrastructure components are recreated from a known good state rather than modified
Why this is correct
Immutable infrastructure replaces servers and containers wholesale from a versioned image rather than patching running instances. In orchestration, this means pods are destroyed and rescheduled from a known good artefact, so configuration drift cannot accumulate and rollbacks are simply redeployments.
- ✗
Configuration changes are applied via SSH into running containers
Why it's wrong here
Applying changes via SSH mutates running containers in place, directly contradicting immutability, where any change requires rebuilding and redeploying a fresh image. SSH patching is tempting for legacy pet servers needing live fixes, but orchestration replaces containers rather than editing them.
- ✗
Servers are never rebooted
Why it's wrong here
Immutable infrastructure is about configuration, not reboots.
- ✗
Container images are updated in-place by patching existing layers
Why it's wrong here
Immutability means replacing container instances rather than mutating running ones; patching existing layers in place is the mutable model. It is tempting because layer caching makes incremental rebuilds cheap, and in-place patching would suit long-lived pet servers that cannot be recreated.
Go deeper
Related to this question
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 →
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.