This KCNA practice question tests your understanding of container orchestration. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which of the following is a benefit of using an orchestrator like Kubernetes?
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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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
Containers share the host kernel but do not provide direct access for tuning in a typical orchestration context.
✗
Guaranteed zero downtime for all updates
Why it's wrong here
Kubernetes provides strategies for zero-downtime updates but does not guarantee it in all scenarios.
✓
Automatic scaling based on CPU utilization
Why this is correct
Horizontal Pod Autoscaler can automatically scale pods based on CPU or custom metrics.
Related concept
Read the scenario before looking for a memorised answer.
✗
Manual scaling based on traffic spikes
Why it's wrong here
Kubernetes supports automatic scaling, not just manual.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates 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.
Trap categories for this question
Scenario analysis trap
Kubernetes provides strategies for zero-downtime updates but does not guarantee it in all scenarios.
Detailed technical explanation
How to think about this question
Under the hood, Kubernetes HPA uses the metrics-server to collect resource usage from kubelet's cAdvisor, then calculates the desired replica count using the formula: desiredReplicas = ceil[currentReplicas * (currentMetricValue / desiredMetricValue)]. This allows for proactive scaling, but note that HPA has a cooldown period (default 5 minutes for scale-up, 3 minutes for scale-down) to avoid thrashing, which can cause delayed response to sudden spikes in real-world scenarios.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the KCNA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this KCNA question in full detail.
Container Orchestration — This question tests Container Orchestration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: 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.
What should I do if I get this KCNA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.