You want to optimize costs by configuring Cluster Autoscaler to remove unused nodes quickly but avoid removing nodes that might be needed soon. Which configuration approach is best?

hard📝 Best Practice Q15 of 15

Kubernetes - Resource Management

ADisable scale-down and manually remove nodes

BSet max nodes equal to min nodes to prevent scaling

CSet a low scale-down delay and enable scale-down of empty nodes

DSet a high scale-down delay and disable scale-down of empty nodes

Step-by-Step Solution

Solution:

Step 1: Understand scale-down delay and empty node removal
Low scale-down delay removes unused nodes faster; enabling empty node scale-down helps remove idle nodes.
Step 2: Avoid preventing scaling or disabling scale-down
Setting max = min or disabling scale-down prevents autoscaler from saving costs.
Final Answer:
Set a low scale-down delay and enable scale-down of empty nodes -> Option C
Quick Check:
Fast scale-down + empty node removal = cost optimization [OK]

Quick Trick: Lower delay + empty node scale-down = save costs fast [OK]

Common Mistakes:

Setting max = min disables scaling
Disabling scale-down wastes resources
Using high delay delays cost savings

Master "Resource Management" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Kubernetes Quizzes

You want to optimize costs by configuring Cluster Autoscaler to remove unused nodes quickly but avoid removing nodes that might be needed soon. Which configuration approach is best?

Step 1: Understand scale-down delay and empty node removal

Step 2: Avoid preventing scaling or disabling scale-down

Final Answer:

Quick Check:

Want More Practice?