During traffic peaks, your Horizontal Pod Autoscaler (HPA) scales out replicas rapidly. However, when traffic dips briefly, the HPA immediately scales down, causing resource thrashing. How can you configure HPA to delay scaling down and stabilize replica count?

Direct Answer (Verified)Reviewed by Sunny (Senior Cloud Engineer)

Correct Answer: Configure the behavior.scaleDown.stabilizationWindowSeconds block in the HPA spec

The HPA behavior specification allows you to configure stabilization windows for scaling actions. Setting stabilizationWindowSeconds for scaleDown specifies how long the autoscaler...

Real Exam ScenarioKubernetes Autoscaling

During traffic peaks, your Horizontal Pod Autoscaler (HPA) scales out replicas rapidly. However, when traffic dips briefly, the HPA immediately scales down, causing resource thrashing. How can you configure HPA to delay scaling down and stabilize replica count?

✓ Correct Answer & ExplanationKubernetes Autoscaling

Correct Answer

Configure the behavior.scaleDown.stabilizationWindowSeconds block in the HPA spec

Why This Answer Is Correct

The HPA behavior specification allows you to configure stabilization windows for scaling actions. Setting stabilizationWindowSeconds for scaleDown specifies how long the autoscaler must wait after calculating a target scale-down before actually executing it, helping to prevent rapid fluctuation or thrashing.

📚 What This Question Tests

This question evaluates your knowledge of Kubernetes Autoscaling — a core concept tested in cloud certification exams. Understanding Kubernetes Autoscaling is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.

More Kubernetes Autoscaling Practice Questions

What does a HorizontalPodAutoscaler (HPA) do when CPU utilization exceeds the defined target?

You want to scale the number of replicas in your frontend deployment based on custom metrics retrieved from Prometheus, rather than standard CPU or Memory utilization. Which Kubernetes autoscaling component should you use?

A DevOps team is running a microservice deployment and wants to configure both Horizontal Pod Autoscaler (HPA) to scale out based on CPU usage and Vertical Pod Autoscaler (VPA) to scale resources up/down. What is the recommended practice when using both autoscalers on the same deployment?

You are running a stateful pod that performs long-running computations. You want to ensure that the Cluster Autoscaler (CA) does not terminate the node hosting this specific pod during a cluster scale-down event. Which annotation should you apply to the pod?