Your manager asks you to deploy a workload to a Kubernetes cluster. You are not sure of the workload's resource requirements or how the requirements might vary depending on usage patterns, external…

Question

Options

• AConfigure the Horizontal Pod Autoscaler for availability, and configure the cluster autoscaler for
• BConfigure the Horizontal Pod Autoscaler for availability, and configure the Vertical Pod Autoscaler
• CConfigure the Vertical Pod Autoscaler recommendations for availability, and configure the Cluster
• DConfigure the Vertical Pod Autoscaler recommendations for availability, and configure the

• A
  3% (2)
• B
  85% (50)
• C
  3% (2)
• D
  8% (5)

Explanation

Option B is correct because it pairs the right tools for each problem: the Vertical Pod Autoscaler (VPA) analyzes actual resource consumption over time and produces cost-effective CPU/memory recommendations without you needing to know requirements upfront, while the Horizontal Pod Autoscaler (HPA) scales pod replicas based on demand, ensuring the workload remains available and functional regardless of usage patterns.

Option A is wrong because the Cluster Autoscaler manages node scaling (adding/removing VMs), not pod-level CPU/memory sizing - it doesn't produce resource recommendations for workloads.

Options C and D are wrong because they assign VPA the role of ensuring availability, but VPA is not designed for that - it resizes individual pods (which causes restarts), not replica counts. Using VPA alone for availability would cause disruptions, not consistent operation.

Memory tip: Think of it as two separate concerns - "What resources does each pod need?" (VPA recommends) vs. "How many pods do I need?" (HPA scales). VPA = Vertical = tweak the Values (CPU/memory per pod); HPA = Horizontal = add more pods Horizontally.

No community discussion yet for this question.