Your company's product team has a new requirement based on customer demand to autoscale your stateless and distributed service running in a Google Kubernetes Engine (GKE) duster. You want to find a so

Question

Options

• ADeploy a Vertical Pod Autoscaler, and scale based on the CPU load.
• BDeploy a Vertical Pod Autoscaler, and scale based on a custom metric.
• CDeploy a Horizontal Pod Autoscaler, and scale based on the CPU toad.
• DDeploy a Horizontal Pod Autoscaler, and scale based on a custom metric.

• A
  14% (6)
• B
  7% (3)
• C
  76% (32)
• D
  2% (1)

Explanation

A Horizontal Pod Autoscaler (HPA) is the correct choice for a stateless, distributed service because it scales by adding or removing pod replicas - the natural fit for horizontal scaling of stateless workloads. A Vertical Pod Autoscaler (VPA) adjusts CPU/memory resources per pod, which is more complex and better suited for stateful or single-instance workloads. CPU-based scaling (not a custom metric) is the simplest and most widely supported trigger, requires no additional configuration, and minimizes changes - which aligns with the two-week deadline constraint. Custom metrics require additional instrumentation and setup time, making them a poor fit here.

No community discussion yet for this question.