Question 32 of 997

Cloud Native Architecture →mediumMultiple ChoiceObjective-mapped

Horizontal Pod Autoscaler — Cooldown Period Impact | Kubernetes and Cloud Native Associate Explained

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. A key principle to apply: horizontalPodAutoscaler (HPA) Cooldown. 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.

A
The HPA is configured to use a different metric (e.g., memory) instead of CPU.
Why wrong: Incorrect. The HPA is explicitly configured to use CPU utilization based on the stem, so it cannot be using a different metric.
B
The HPA cooldown period of 3 minutes prevents scaling during the short peak duration.
Correct. The 3-minute cooldown prevents scaling during short peak durations, especially if a previous scale event occurred recently.
C
The CPU limit of 1000m restricts the Pods from using more than 1000m, but the HPA bases scaling on requests, not limits.
Why wrong: Incorrect. The HPA bases scaling on resource requests (500m), not limits (1000m). With 800m usage, utilization is 160%, which should trigger scaling. The limit does not restrict scaling.
D
The cluster does not have enough nodes to schedule additional Pods.
Why wrong: Incorrect. The stem states the cluster has ample capacity, so node availability is not an issue.

Full breakdown with real-world context →

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

✓

The HPA cooldown period of 3 minutes prevents scaling during the short peak duration.

Option B is correct because the HPA cooldown period of 3 minutes prevents scaling during short peak durations. The scenario states 'intermittent slowdowns during peak traffic,' implying the high CPU usage is not sustained long enough to trigger a scale-up event. After a previous scale operation (possibly due to an earlier peak), the cooldown period must elapse before the HPA can initiate another scaling action. Since the peaks are short and intermittent, they may fall within the cooldown window, preventing the HPA from scaling despite high CPU usage.

Key principle: HorizontalPodAutoscaler (HPA) Cooldown

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 it's wrong here
Incorrect. The HPA is explicitly configured to use CPU utilization based on the stem, so it cannot be using a different metric.
✓
The HPA cooldown period of 3 minutes prevents scaling during the short peak duration.
Why this is correct
Correct. The 3-minute cooldown prevents scaling during short peak durations, especially if a previous scale event occurred recently.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
HorizontalPodAutoscaler (HPA) Cooldown
✗
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
Incorrect. The HPA bases scaling on resource requests (500m), not limits (1000m). With 800m usage, utilization is 160%, which should trigger scaling. The limit does not restrict scaling.
✗
The cluster does not have enough nodes to schedule additional Pods.
Why it's wrong here
Incorrect. The stem states the cluster has ample capacity, so node availability is not an issue.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap is that while the HPA is configured for CPU, the scaling is based on utilization (usage/request), and since CPU usage (800m) is 160% of the request (500m), the HPA should scale. The lack of scaling indicates a configuration issue, such as the HPA targeting a different metric (e.g., memory or a custom metric) or the metrics server not providing the data. Candidates often overlook that the HPA may not be using CPU even if they assume it is.

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

HorizontalPodAutoscaler (HPA) Cooldown
HPA Scaling Threshold

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

HorizontalPodAutoscaler (HPA) Cooldown

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. HorizontalPodAutoscaler (HPA) Cooldown Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Review horizontalPodAutoscaler (HPA) Cooldown, then practise related KCNA questions on the same topic to reinforce the concept.

Related KCNA practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Kubernetes Fundamentals practice questions

Practise KCNA questions linked to Kubernetes Fundamentals.

Container Orchestration practice questions

Practise KCNA questions linked to Container Orchestration.

Cloud Native Architecture practice questions

Practise KCNA questions linked to Cloud Native Architecture.

Cloud Native Observability practice questions

Practise KCNA questions linked to Cloud Native Observability.

Cloud Native Application Delivery practice questions

Practise KCNA questions linked to Cloud Native Application Delivery.

KCNA fundamentals practice questions

Practise KCNA questions linked to KCNA fundamentals.

KCNA scenario practice questions

Practise KCNA questions linked to KCNA scenario.

KCNA troubleshooting practice questions

Practise KCNA questions linked to KCNA troubleshooting.

Practice this exam

Start a free KCNA practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

KCNA practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this KCNA question test?

Cloud Native Architecture — This question tests Cloud Native Architecture — HorizontalPodAutoscaler (HPA) Cooldown.

What is the correct answer to this question?

The correct answer is: The HPA cooldown period of 3 minutes prevents scaling during the short peak duration. — Option B is correct because the HPA cooldown period of 3 minutes prevents scaling during short peak durations. The scenario states 'intermittent slowdowns during peak traffic,' implying the high CPU usage is not sustained long enough to trigger a scale-up event. After a previous scale operation (possibly due to an earlier peak), the cooldown period must elapse before the HPA can initiate another scaling action. Since the peaks are short and intermittent, they may fall within the cooldown window, preventing the HPA from scaling despite high CPU usage.

What should I do if I get this KCNA question wrong?

Review horizontalPodAutoscaler (HPA) Cooldown, then practise related KCNA questions on the same topic to reinforce the concept.

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?

HorizontalPodAutoscaler (HPA) Cooldown

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on KCNA

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A cloud-native application is designed with multiple microservices that need to handle a sudden spike in traffic without manual intervention. Which Kubernetes feature best enables this?

easy

A.VerticalPodAutoscaler
B.Cluster Autoscaler
✓ C.HorizontalPodAutoscaler
D.PodDisruptionBudget

Why C: The HorizontalPodAutoscaler (HPA) automatically scales the number of pod replicas in a deployment based on observed CPU/memory utilization or custom metrics. This directly addresses the need to handle a sudden traffic spike without manual intervention by adding more pod instances to distribute the load.

Keep practising

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.

Loading comments…

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.