This KCNA practice question tests your understanding of cloud native architecture. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
Your organization runs a multi-service application on a Kubernetes cluster. Each service is deployed as a set of Pods managed by a Deployment. The application experiences intermittent slowdowns during peak traffic. Monitoring shows that the database service Pods have high CPU usage, but the HorizontalPodAutoscaler (HPA) configured for the database Deployment does not scale. The HPA is based on average CPU utilization across Pods, with target 70%. The database Deployment has resource requests and limits set: requests.cpu: 500m, limits.cpu: 1000m. During peak, CPU usage reaches 800m per Pod. The HPA has a cooldown period of 3 minutes. The cluster has ample capacity. What is the most likely reason the HPA is not scaling?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The HPA is configured to use a different metric (e.g., memory) instead of CPU.
Option A is correct because the scenario states that CPU usage reaches 800m per Pod, which is 160% of the requested 500m, well above the HPA's 70% target. If the HPA were correctly configured for CPU, it would have triggered scaling. The fact that it does not scale despite high CPU usage indicates the HPA is likely configured to use a different metric (e.g., memory or custom metrics), not CPU. This mismatch between the metric the HPA monitors and the actual resource bottleneck prevents scaling.
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.
✓
The HPA is configured to use a different metric (e.g., memory) instead of CPU.
Why this is correct
If the HPA is mistakenly using memory metric, it would not scale based on CPU spikes.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The HPA cooldown period of 3 minutes prevents scaling during the short peak duration.
Why it's wrong here
Cooldown delays but does not prevent scaling; if peak persists beyond cooldown, scaling would occur.
✗
The CPU limit of 1000m restricts the Pods from using more than 1000m, but the HPA bases scaling on requests, not limits.
Why it's wrong here
Limits do not affect HPA calculations; HPA uses requests to compute utilization.
✗
The cluster does not have enough nodes to schedule additional Pods.
Why it's wrong here
The scenario states the cluster has ample capacity, so this is not the issue.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume the HPA is always configured for CPU by default, but the KCNA exam tests whether you recognize that an HPA can be configured for any metric, and a mismatch between the monitored metric and the actual bottleneck will prevent scaling.
Trap categories for this question
Scenario analysis trap
The scenario states the cluster has ample capacity, so this is not the issue.
Detailed technical explanation
How to think about this question
The Kubernetes HorizontalPodAutoscaler calculates the desired replica count using the formula: desiredReplicas = ceil(currentReplicas * (currentMetricValue / targetMetricValue)). For CPU, the currentMetricValue is the average CPU utilization across all Pods, computed as the average of (current CPU usage / Pod's CPU request). If the HPA is configured for a different metric, such as memory or a custom metric from Prometheus, it will ignore CPU entirely, even if CPU is the bottleneck. In real-world scenarios, misconfigured HPA metrics are a common cause of scaling failures, especially when teams assume default CPU-based autoscaling without verifying the HPA specification.
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.
Cloud Native Architecture — This question tests Cloud Native Architecture — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The HPA is configured to use a different metric (e.g., memory) instead of CPU. — Option A is correct because the scenario states that CPU usage reaches 800m per Pod, which is 160% of the requested 500m, well above the HPA's 70% target. If the HPA were correctly configured for CPU, it would have triggered scaling. The fact that it does not scale despite high CPU usage indicates the HPA is likely configured to use a different metric (e.g., memory or custom metrics), not CPU. This mismatch between the metric the HPA monitors and the actual resource bottleneck prevents scaling.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.