Skip to main content
🔒 Preview mode. The first 15 Foundations lessons are free; this one is Pro. Start a 7-day trial to unlock the editor, AI hints and the rest of the curriculum. Card required, cancel any time in Dashboard.
Start 7-day trial →
⚡
← Courses
›
DevOps for Python services
›
Module 5 · Cloud, IaC, Secrets, Cost · Recap
›
Cost: rightsizing autoscalers
quiz
102 / 104
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Pods consistently use 200m CPU, request is 1 CPU. Effect? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Pods consistently use 200m CPU, request is 1 CPU. Effect? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
The pod gets faster scheduling — kube-scheduler prefers larger requests so it lands on nodes with spare headroom first.
B
Cluster reserves 5× the CPU it needs → nodes scale up too aggressively → 5× the bill. Right-size via VPA recommendations.
C
It saves money — kubelet only bills for actual CPU usage and the unused 800m reservation is freed back to the cluster pool.
D
It doesn't matter — Cluster Autoscaler bin-packs based on real usage rather than declared requests on modern node pools.
Submit answer
💬 Discussion
Be the first to ask a question or share a tip.
Sign in
to join the discussion. Reading is free.
Loading discussion…