What happens with a regular pod running in Kubernetes when a node fails?

The correct answer is B. A new, near-identical pod but with different UID is scheduled to another node. When a node fails, Kubernetes does not restore the original pod object - it creates an entirely new pod with a new UID (B). The new pod is near-identical in spec but is a distinct object in the API. Option A is wrong because the UID changes. Option C is incorrect - Kubernetes…

Submitted by fatima_kr· May 4, 2026Kubernetes Fundamentals

Question

Options

AA new pod with the same UID is scheduled to another node after a while.
BA new, near-identical pod but with different UID is scheduled to another node.
CBy default, a pod can only be scheduled to the same node when the node fails.
DA new pod is scheduled on a different node only if it is configured explicitly.

How the community answered

(40 responses)

A
3% (1)
B
93% (37)
C
5% (2)

Explanation

When a node fails, Kubernetes does not restore the original pod object - it creates an entirely new pod with a new UID (B). The new pod is near-identical in spec but is a distinct object in the API. Option A is wrong because the UID changes. Option C is incorrect - Kubernetes does not attempt to reschedule to the same failed node. Option D is misleading; for pods managed by a controller (Deployment, ReplicaSet, etc.), rescheduling happens automatically without explicit per-pod configuration.

Topics

#Pod lifecycle#Node failure#Scheduling#Self-healing

Community Discussion

No community discussion yet for this question.

Full KCNA Practice