Bird
0
0

You notice your Kubernetes cluster is overspending because pods are not scaling down after load decreases. Which is the most likely cause?

medium📝 Troubleshoot Q14 of 15
Kubernetes - Production Best Practices
You notice your Kubernetes cluster is overspending because pods are not scaling down after load decreases. Which is the most likely cause?
ACPU requests are set higher than limits
BResource <code>limits</code> are set too low
CPods have no <code>readinessProbe</code> configured
DThe Horizontal Pod Autoscaler has a high <code>minReplicas</code> value
Step-by-Step Solution
Solution:

  1. Step 1: Analyze autoscaling parameters

    A high minReplicas prevents scaling below that number, causing overspending.

  2. Step 2: Evaluate other options

    Low limits or readiness probes don't directly prevent scaling down; CPU requests > limits is invalid.

  3. Final Answer:

    The Horizontal Pod Autoscaler has a high minReplicas value -> Option D

  4. Quick Check:

    High minReplicas blocks scale down = A [OK]
Quick Trick: Check minReplicas to allow scaling down [OK]
Common Mistakes:
  • Confusing limits with requests
  • Ignoring minReplicas effect
  • Assuming readinessProbe affects scaling

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Advanced Deployment Patterns - FluxCD for continuous delivery - Quiz 13medium Helm Package Manager - Why Helm simplifies deployments - Quiz 1easy Monitoring and Logging - Why cluster monitoring matters - Quiz 4medium Operators and Custom Resources - Custom resources concept - Quiz 6medium Production Best Practices - Why production readiness matters - Quiz 1easy Production Best Practices - Multi-cluster management concept - Quiz 15hard RBAC and Security - RoleBindings and ClusterRoleBindings - Quiz 11easy RBAC and Security - Secrets encryption at rest - Quiz 4medium Troubleshooting - Node troubleshooting - Quiz 5medium Troubleshooting - Debugging with kubectl debug - Quiz 7medium