KCNA Container Orchestration Practice Question
Which of the following is a key benefit of container orchestration?
⚠ Common exam trap
KCNA often tests the contrast between orchestration's automated, declarative model and manual/imperative alternatives, so distractors describing manual scaling or manual failure recovery are designed to catch candidates who don't internalize the 'automated + declarative' framing.
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
✓
Automated scaling, self-healing, and declarative management
Container orchestration platforms like Kubernetes provide automated scaling (HPA/VPA/cluster autoscaler), self-healing (restarting failed containers, rescheduling pods, replacing unhealthy nodes), and declarative management (desired-state YAML reconciled by controllers). These three capabilities are the defining value proposition that distinguishes orchestration from manually running `docker run` commands.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manual scaling of applications
Why it's wrong here
Manual scaling is the pre-orchestration baseline; orchestrators automate replica adjustment from declared metrics or desired state. It is tempting because operators can still scale by hand, but that forfeits the automatic reconciliation the question asks about as a benefit.
- ✗
Requires manual intervention for pod failures
Why it's wrong here
Orchestrators restart or reschedule failed pods automatically via controllers and health probes, so requiring manual intervention describes the absence of the benefit. It is tempting because operators can intervene manually, but that is an operational fallback, not the orchestration advantage.
- ✗
Only supports monolithic applications
Why it's wrong here
Orchestration platforms schedule and scale many independent containers, including microservices, so restricting support to monolithic applications contradicts the scenario's requirement for distributed workloads. It is tempting because a single container can host a monolith, but that is packaging, not an orchestration benefit.
- ✓
Automated scaling, self-healing, and declarative management
Why this is correct
Orchestrators such as Kubernetes continuously reconcile observed state against declared manifests, automatically restarting failed containers and scaling replicas to match load. This declarative control loop delivers self-healing and elastic scaling, which are the defining operational benefits over manually managed containers.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.