Exam Bundle

Existing workload Pods remain after cordon while a subsequent approved drain moves eligible controller-managed Pods. That observed result would support another specific correction: Distinguish cordon, which prevents new ordinary scheduling, from drain, which initiates managed Pod eviction. The other scenario concerns: An operator expects cordoning a node to evict every Pod immediately and is confused that running Pods remain present. The current Brookside Manufacturing problem is: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The evidence required here is: The replicas appear on separate eligible nodes or zones according to the configured distribution rule.

A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks. That observed result would support another specific correction: Allow the scheduler to choose a healthy eligible node using selectors and affinity unless direct binding is truly justified. The other scenario concerns: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. The current Brookside Manufacturing problem is: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The evidence required here is: The replicas appear on separate eligible nodes or zones according to the configured distribution rule.

The scheduler handles higher-priority workloads according to declared priority and supported preemption policy. That observed result would support another specific correction: Review PriorityClass and scheduling preemption behavior instead of treating every Pending Pod as a node failure. The other scenario concerns: A critical workload cannot preempt lower-priority Pods because the team assigned no appropriate PriorityClass to it. The current Brookside Manufacturing problem is: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The evidence required here is: The replicas appear on separate eligible nodes or zones according to the configured distribution rule.

Align Pod topology and compatible storage volume topology so the scheduler can place the Pod where its volume is usable. That choice addresses a different foundational issue: A StatefulSet workload has a required PersistentVolume node affinity that conflicts with its chosen worker's zone. The issue at Juniper Media is instead: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. It does not establish the required correction; the decisive verification would be: The replicas appear on separate eligible nodes or zones according to the configured distribution rule.

Review PriorityClass and scheduling preemption behavior instead of treating every Pending Pod as a node failure. That choice addresses a different foundational issue: A critical workload cannot preempt lower-priority Pods because the team assigned no appropriate PriorityClass to it. The issue at Juniper Media is instead: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. It does not establish the required correction; the decisive verification would be: The replicas appear on separate eligible nodes or zones according to the configured distribution rule.

Set realistic CPU requests or provide a sufficiently capable node rather than assuming replicas can split one Pod across nodes. That choice addresses a different foundational issue: A Pending Pod cannot fit on any node because its CPU request exceeds the allocatable capacity of each individual worker. The issue at Juniper Media is instead: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. It does not establish the required correction; the decisive verification would be: The replicas appear on separate eligible nodes or zones according to the configured distribution rule.

The Pod binds after the specified peer workload and topology match, with no pending-affinity event. That observed result would support another specific correction: Inspect scheduler events and correct the Pod-affinity label or topology requirement rather than changing unrelated resource limits. The other scenario concerns: A Pod has an unsatisfied required Pod affinity rule and the team increases its CPU limit to solve the Pending condition. The current Juniper Media problem is: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The evidence required here is: The replicas appear on separate eligible nodes or zones according to the configured distribution rule.

The scheduling event clears once an appropriately labeled node can accept the Pod within the resource budget. That observed result would support another specific correction: Inspect the Pod's nodeSelector or node affinity and align it with accurate labels on eligible nodes. The other scenario concerns: A Pod remains Pending despite free resources because it requires a label that no node currently has. The current Juniper Media problem is: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The evidence required here is: The replicas appear on separate eligible nodes or zones according to the configured distribution rule.

The scheduler handles higher-priority workloads according to declared priority and supported preemption policy. That observed result would support another specific correction: Review PriorityClass and scheduling preemption behavior instead of treating every Pending Pod as a node failure. The other scenario concerns: A critical workload cannot preempt lower-priority Pods because the team assigned no appropriate PriorityClass to it. The current Juniper Media problem is: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The evidence required here is: The replicas appear on separate eligible nodes or zones according to the configured distribution rule.

Inspect scheduler events and correct the Pod-affinity label or topology requirement rather than changing unrelated resource limits. That choice addresses a different foundational issue: A Pod has an unsatisfied required Pod affinity rule and the team increases its CPU limit to solve the Pending condition. The issue at Highland Education is instead: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. It does not establish the required correction; the decisive verification would be: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

Use appropriate Pod anti-affinity or topology-spread constraints to distribute replicas across eligible failure domains. That choice addresses a different foundational issue: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The issue at Highland Education is instead: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. It does not establish the required correction; the decisive verification would be: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

Declare appropriate CPU and memory requests so scheduling decisions reserve the intended resources on eligible nodes. That choice addresses a different foundational issue: A workload owner sets a CPU limit but no request and assumes the scheduler estimates application demand from real CPU usage. The issue at Highland Education is instead: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. It does not establish the required correction; the decisive verification would be: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

The scheduler handles higher-priority workloads according to declared priority and supported preemption policy. That observed result would support another specific correction: Review PriorityClass and scheduling preemption behavior instead of treating every Pending Pod as a node failure. The other scenario concerns: A critical workload cannot preempt lower-priority Pods because the team assigned no appropriate PriorityClass to it. The current Highland Education problem is: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. The evidence required here is: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

Two separately named Pods run on eligible nodes and no single Pod spans two node assignments. That observed result would support another specific correction: Explain that one Pod binds to one node, whereas separate replicas can be scheduled across multiple nodes. The other scenario concerns: An administrator sets a limit of two replicas and assumes the scheduler will launch a single Pod simultaneously on two nodes. The current Highland Education problem is: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. The evidence required here is: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

The Pod schedules on a single node with adequate memory after a capacity or request adjustment. That observed result would support another specific correction: Recognize that a single Pod's resources must fit on one eligible node and resize or add capacity accordingly. The other scenario concerns: A team's large Pod cannot schedule because the remaining cluster capacity is fragmented across nodes with too little individual free memory. The current Highland Education problem is: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. The evidence required here is: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

Use appropriate Pod anti-affinity or topology-spread constraints to distribute replicas across eligible failure domains. That choice addresses a different foundational issue: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The issue at Eastshore Energy is instead: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. It does not establish the required correction; the decisive verification would be: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

Set realistic CPU requests or provide a sufficiently capable node rather than assuming replicas can split one Pod across nodes. That choice addresses a different foundational issue: A Pending Pod cannot fit on any node because its CPU request exceeds the allocatable capacity of each individual worker. The issue at Eastshore Energy is instead: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. It does not establish the required correction; the decisive verification would be: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

Check node cordon state and return approved healthy nodes to schedulable status only after maintenance completion. That choice addresses a different foundational issue: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. The issue at Eastshore Energy is instead: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. It does not establish the required correction; the decisive verification would be: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

The scheduler handles higher-priority workloads according to declared priority and supported preemption policy. That observed result would support another specific correction: Review PriorityClass and scheduling preemption behavior instead of treating every Pending Pod as a node failure. The other scenario concerns: A critical workload cannot preempt lower-priority Pods because the team assigned no appropriate PriorityClass to it. The current Eastshore Energy problem is: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. The evidence required here is: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

The scheduling event clears once an appropriately labeled node can accept the Pod within the resource budget. That observed result would support another specific correction: Inspect the Pod's nodeSelector or node affinity and align it with accurate labels on eligible nodes. The other scenario concerns: A Pod remains Pending despite free resources because it requires a label that no node currently has. The current Eastshore Energy problem is: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. The evidence required here is: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

The Pod mounts its volume on an eligible node in the required zone and stops reporting volume node-affinity conflicts. That observed result would support another specific correction: Align Pod topology and compatible storage volume topology so the scheduler can place the Pod where its volume is usable. The other scenario concerns: A StatefulSet workload has a required PersistentVolume node affinity that conflicts with its chosen worker's zone. The current Eastshore Energy problem is: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. The evidence required here is: A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks.

Review PriorityClass and scheduling preemption behavior instead of treating every Pending Pod as a node failure. That choice addresses a different foundational issue: A critical workload cannot preempt lower-priority Pods because the team assigned no appropriate PriorityClass to it. The issue at Maplewood Schools is instead: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. It does not establish the required correction; the decisive verification would be: The pending Pod schedules after an eligible node is safely uncordoned and available.

Separate workload replica scaling from node autoscaling and verify whether a cluster autoscaler or managed node group is configured. That choice addresses a different foundational issue: An organization expects adding replicas to a Deployment to automatically increase cluster node capacity when all workers are full. The issue at Maplewood Schools is instead: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. It does not establish the required correction; the decisive verification would be: The pending Pod schedules after an eligible node is safely uncordoned and available.

Distinguish cordon, which prevents new ordinary scheduling, from drain, which initiates managed Pod eviction. That choice addresses a different foundational issue: An operator expects cordoning a node to evict every Pod immediately and is confused that running Pods remain present. The issue at Maplewood Schools is instead: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. It does not establish the required correction; the decisive verification would be: The pending Pod schedules after an eligible node is safely uncordoned and available.

Existing workload Pods remain after cordon while a subsequent approved drain moves eligible controller-managed Pods. That observed result would support another specific correction: Distinguish cordon, which prevents new ordinary scheduling, from drain, which initiates managed Pod eviction. The other scenario concerns: An operator expects cordoning a node to evict every Pod immediately and is confused that running Pods remain present. The current Maplewood Schools problem is: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. The evidence required here is: The pending Pod schedules after an eligible node is safely uncordoned and available.

A replacement Pod receives a scheduler-selected node with available resources and satisfies readiness checks. That observed result would support another specific correction: Allow the scheduler to choose a healthy eligible node using selectors and affinity unless direct binding is truly justified. The other scenario concerns: A Pod is bound to an unavailable worker because an engineer directly sets nodeName instead of letting the scheduler place it. The current Maplewood Schools problem is: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. The evidence required here is: The pending Pod schedules after an eligible node is safely uncordoned and available.

A capacity test shows Pending replicas until new eligible worker capacity is added by the approved mechanism. That observed result would support another specific correction: Separate workload replica scaling from node autoscaling and verify whether a cluster autoscaler or managed node group is configured. The other scenario concerns: An organization expects adding replicas to a Deployment to automatically increase cluster node capacity when all workers are full. The current Maplewood Schools problem is: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. The evidence required here is: The pending Pod schedules after an eligible node is safely uncordoned and available.

Inspect the Pod's nodeSelector or node affinity and align it with accurate labels on eligible nodes. That choice addresses a different foundational issue: A Pod remains Pending despite free resources because it requires a label that no node currently has. The issue at Brookside Manufacturing is instead: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. It does not establish the required correction; the decisive verification would be: The pending Pod schedules after an eligible node is safely uncordoned and available.

Use PodDisruptionBudgets and controlled drain to preserve defined availability during voluntary maintenance. That choice addresses a different foundational issue: A team drains a node without considering PodDisruptionBudgets and disrupts the application's minimum available replica target. The issue at Brookside Manufacturing is instead: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. It does not establish the required correction; the decisive verification would be: The pending Pod schedules after an eligible node is safely uncordoned and available.

Use appropriate Pod anti-affinity or topology-spread constraints to distribute replicas across eligible failure domains. That choice addresses a different foundational issue: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The issue at Brookside Manufacturing is instead: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. It does not establish the required correction; the decisive verification would be: The pending Pod schedules after an eligible node is safely uncordoned and available.

The Pod becomes scheduled on a node with enough allocatable CPU and no longer reports an insufficient CPU scheduling event. That observed result would support another specific correction: Set realistic CPU requests or provide a sufficiently capable node rather than assuming replicas can split one Pod across nodes. The other scenario concerns: A Pending Pod cannot fit on any node because its CPU request exceeds the allocatable capacity of each individual worker. The current Brookside Manufacturing problem is: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. The evidence required here is: The pending Pod schedules after an eligible node is safely uncordoned and available.

The replicas appear on separate eligible nodes or zones according to the configured distribution rule. That observed result would support another specific correction: Use appropriate Pod anti-affinity or topology-spread constraints to distribute replicas across eligible failure domains. The other scenario concerns: Two high-availability service replicas repeatedly land on the same node because no topology preference has been declared. The current Brookside Manufacturing problem is: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. The evidence required here is: The pending Pod schedules after an eligible node is safely uncordoned and available.

The Pod schedules on a single node with adequate memory after a capacity or request adjustment. That observed result would support another specific correction: Recognize that a single Pod's resources must fit on one eligible node and resize or add capacity accordingly. The other scenario concerns: A team's large Pod cannot schedule because the remaining cluster capacity is fragmented across nodes with too little individual free memory. The current Brookside Manufacturing problem is: A new Pod waits indefinitely because all nodes are marked unschedulable after planned maintenance. The evidence required here is: The pending Pod schedules after an eligible node is safely uncordoned and available.