Correct Answer: Increases the number of Pod replicas in the Deployment or ReplicaSet
The Horizontal Pod Autoscaler automatically scales the number of Pods in a replication controller, deployment, replica set or stateful set based on observed CPU utilization....
Correct Answer
Increases the number of Pod replicas in the Deployment or ReplicaSet
Why This Answer Is Correct
The Horizontal Pod Autoscaler automatically scales the number of Pods in a replication controller, deployment, replica set or stateful set based on observed CPU utilization.
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.
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?
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?
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?