Kubernetes - Resource ManagementHow does Cluster Autoscaler decide which nodes to remove during scale-down when multiple nodes are underutilized?AIt removes nodes with the least number of pods firstBIt removes nodes that can be drained without evicting pods that cannot be rescheduledCIt removes nodes randomly to balance the clusterDIt removes the newest nodes firstCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand scale-down node selection criteriaCluster Autoscaler removes nodes that can be safely drained without causing pod scheduling failures.Step 2: Eliminate incorrect optionsIt does not remove nodes randomly or based on pod count alone, nor does it remove newest nodes first.Final Answer:It removes nodes that can be drained without evicting pods that cannot be rescheduled -> Option BQuick Check:Safe node removal avoids unschedulable pods [OK]Quick Trick: Autoscaler removes only safely drainable nodes [OK]Common Mistakes:Assuming random node removalThinking it removes nodes with fewest pods alwaysBelieving newest nodes are removed first
Master "Resource Management" in Kubernetes9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kubernetes Quizzes ConfigMaps - Creating ConfigMaps from literals - Quiz 8hard ConfigMaps - Using ConfigMaps as environment variables - Quiz 13medium Ingress - Ingress resource definition - Quiz 8hard Networking - Service mesh concept overview - Quiz 14medium Persistent Storage - Why persistent storage matters in Kubernetes - Quiz 6medium Resource Management - Memory requests and limits - Quiz 10hard Scheduling - DaemonSets for per-node workloads - Quiz 10hard Secrets - External secret management integration - Quiz 2easy Secrets - Using Secrets as environment variables - Quiz 4medium Secrets - Creating Secrets - Quiz 2easy