KCNA Container Orchestration Practice Question
Which of the following is a benefit of using container orchestration platforms like Kubernetes?
⚠ Common exam trap
CNCF often tests the misconception that container orchestration platforms like Kubernetes increase complexity and latency, but the correct answer highlights that they actually automate recovery and improve resilience, not degrade performance.
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
✓
Self-healing (automatic restart of failed containers)
Kubernetes includes a built-in controller (the kubelet and ReplicaSet controller) that continuously monitors the desired state of pods. If a container fails or its process crashes, the kubelet automatically restarts it based on the pod's restart policy (e.g., Always), ensuring high availability without manual intervention. This self-healing capability is a core benefit of container orchestration, reducing downtime and operational overhead.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increased network latency
Why it's wrong here
Orchestration abstracts pod networking through Services, CNI plugins and kube-proxy load balancing; it does not add latency as a designed benefit. It is tempting because overlay networking and extra hops can introduce overhead, and it would be correct when describing a cost of encapsulation rather than an advantage of adopting Kubernetes.
- ✗
Manual scaling of applications
Why it's wrong here
Kubernetes scales workloads automatically via the Horizontal Pod Autoscaler and Cluster Autoscaler reacting to metrics; manual scaling is the pre-orchestration baseline it replaces. It is tempting because operators can still set replica counts by hand, and it would be correct for workloads with predictable, fixed capacity needs where autoscaling is deliberately disabled.
- ✓
Self-healing (automatic restart of failed containers)
Why this is correct
Kubernetes continuously reconciles desired state against actual state via its control loop; when a container or node fails, the ReplicaSet controller recreates the pod automatically. This self-healing restarts failed containers without human intervention, directly delivering the availability benefit the question asks about.
- ✗
Tighter coupling between microservices
Why it's wrong here
Orchestration decouples services through declarative APIs, service discovery and independent deployment lifecycles; tighter coupling contradicts that model. It is tempting because Kubernetes does bind pods to services and ingress, and it would be correct where co-located components genuinely must share fate, such as a sidecar container in the same pod.
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.