KCNA Container Orchestration Practice Question
Which of the following is a benefit of using an orchestrator like Kubernetes?
⚠ Common exam trap
Many exam-takers confuse 'automatic scaling' with 'manual scaling' or assume Kubernetes guarantees zero downtime, but the exam tests the specific benefit of automated, policy-driven scaling based on metrics like CPU utilization.
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
✓
Automatic scaling based on CPU utilization
Kubernetes, as a container orchestrator, provides built-in Horizontal Pod Autoscaling (HPA) that automatically adjusts the number of pod replicas based on observed CPU utilization (or custom metrics). This is a core benefit because it allows applications to handle varying load without manual intervention, improving resource efficiency and availability.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Direct access to the host kernel for performance tuning
Why it's wrong here
Kubernetes abstracts the host through containers and the container runtime, deliberately restricting direct kernel access. It is tempting because performance tuning sometimes needs kernel parameters, but that is a node-level administration task, not an orchestration benefit; pods share the kernel without privileged host access.
- ✗
Guaranteed zero downtime for all updates
Why it's wrong here
Kubernetes cannot guarantee zero downtime universally; it only supports it when readiness probes, rolling updates and sufficient replicas are configured. The benefit is declarative orchestration of scheduling, scaling and self-healing across a cluster, which is why it is chosen for managing containerised workloads at scale.
- ✓
Automatic scaling based on CPU utilization
Why this is correct
Kubernetes Horizontal Pod Autoscaler adjusts replica counts based on observed CPU utilisation against defined targets, adding or removing pods automatically. This removes manual capacity intervention, satisfying the benefit of responding to load changes without operator action.
- ✗
Manual scaling based on traffic spikes
Why it's wrong here
Manual scaling requires an operator to react to traffic spikes, whereas Kubernetes performs horizontal pod autoscaling automatically from metrics such as CPU utilisation. Manual intervention is the opposite of the orchestration benefit the question asks for. It would suit a small, static deployment where automation overhead is unjustified and capacity changes are rare and predictable.
Go deeper
Related to this question
Learn chapter
Kubernetes API and Core Objects
Key term
ReplicaSet and Replication
A ReplicaSet ensures a specified number of identical pod instances are running at all times in Kubernetes, using replication to maintain availability and stability.
Key term
Horizontal Pod Autoscaling
Horizontal Pod Autoscaling automatically adjusts the number of pod replicas in a Kubernetes cluster based on observed CPU, memory, or custom metrics.
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.