1V0-71.21 · Question #45
Which state is invalid in a Pod's lifecycle?
The correct answer is D. Setup. "Setup" is not a valid phase in the Kubernetes Pod lifecycle - it was never part of the spec and doesn't exist in the API. The five valid Pod phases are Pending (E), Running (B), Succeeded (C), Failed (A), and Unknown (not listed here), making all other options legitimate…
Question
Which state is invalid in a Pod’s lifecycle?
Options
- AFailed
- BRunning
- CSucceeded
- DSetup
- EPending
How the community answered
(38 responses)- A3% (1)
- D95% (36)
- E3% (1)
Explanation
"Setup" is not a valid phase in the Kubernetes Pod lifecycle - it was never part of the spec and doesn't exist in the API. The five valid Pod phases are Pending (E), Running (B), Succeeded (C), Failed (A), and Unknown (not listed here), making all other options legitimate states you'd encounter in a real cluster.
- Pending: Pod accepted by the cluster but containers not yet started (e.g., waiting on scheduling or image pull).
- Running: At least one container is running or starting.
- Succeeded: All containers exited with code 0 and won't restart.
- Failed: At least one container exited with a non-zero code and won't restart.
Memory tip: Think of the acronym PRFSPU - Pending → Running → Failed/Succeeded. If you can't map a state name to one of those transitions, it's not real. "Setup" sounds plausible but is a trap word - Kubernetes never uses it.
Topics
Community Discussion
No community discussion yet for this question.