KCNA Container Orchestration Practice Question
Which THREE are benefits of using container orchestration platforms like Kubernetes?
⚠ Common exam trap
A common pitfall is the misconception that orchestration platforms like Kubernetes automate everything, including application code changes and monitoring setup, when in reality they only automate operational tasks like scaling and recovery, leaving code adaptation and observability configuration to the user.
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
✓
High availability through automatic container restart and replication
Option A is correct because Kubernetes provides high availability by automatically restarting failed containers and maintaining the desired number of replicas across nodes, ensuring workloads remain available even when individual containers or nodes fail. Option B is correct because Kubernetes supports automatic scaling of container replicas through mechanisms like the Horizontal Pod Autoscaler, which adjusts replica counts based on observed CPU, memory, or custom metrics. Option C is correct because Kubernetes performs self-healing by detecting failed containers, pods, or nodes and replacing or rescheduling them without manual intervention, restoring the declared desired state. Option D is not a benefit of orchestration because Kubernetes manages deployment and runtime concerns, not application source code, so developers still must write and modify code as needed. Option E is incorrect because orchestration platforms do not eliminate monitoring and logging; they integrate with tools like Prometheus, Grafana, and the ELK stack, and observability remains essential for operating containerized workloads.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
High availability through automatic container restart and replication
Why this is correct
Replication controllers and ReplicaSets maintain the declared replica count, and Kubernetes restarts or reschedules failed containers automatically. This delivers high availability without manual intervention, satisfying the benefit of automatic restart and replication across the cluster.
- ✓
Automatic scaling of container replicas based on resource usage
Why this is correct
The Horizontal Pod Autoscaler adjusts replica counts from observed CPU, memory or custom metrics, so capacity tracks demand automatically. This satisfies the benefit of scaling replicas based on resource usage rather than requiring manual intervention.
- ✓
Self-healing by replacing failed containers without manual intervention
Why this is correct
Kubernetes continuously reconciles observed state against desired state, restarting or rescheduling containers when health probes fail or nodes die. This automated remediation satisfies the self-healing benefit, removing manual intervention and maintaining workload availability without operator action.
- ✗
Simplified application development by eliminating the need for code changes
Why it's wrong here
Orchestration manages deployment, scaling and scheduling of existing images; it cannot alter application source code, so development effort continues. It is tempting because declarative manifests and rolling updates remove manual deployment toil, which in a stable, already-containerised application can feel like development work has been eliminated.
- ✗
Elimination of the need for monitoring and logging
Why it's wrong here
Orchestration schedules and restarts containers but exposes no telemetry itself; monitoring and logging remain essential and are typically integrated alongside it. It is tempting because Kubernetes does surface basic liveness and readiness states, which in a minimal single-container test setup can appear to replace dedicated observability tooling.
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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.