CKA Workloads and Scheduling Practice Question
What is the default pod phase when a pod is first created but not yet running?
⚠ Common exam trap
CNCF often tests the misconception that a newly created Pod immediately enters the Running phase, but the correct initial phase is always Pending until the scheduler assigns a node and the kubelet starts the containers.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Pending
When a Pod is first created, it enters the Pending phase before it is scheduled onto a node and its containers are started. The Pending phase indicates that the Pod has been accepted by the Kubernetes API server but one or more containers are not yet running, often because the image is being pulled or the node is not ready. This is the default initial phase as defined in the Kubernetes Pod lifecycle.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Running
Why it's wrong here
Running is the phase assigned only after the pod has been successfully scheduled and all of its init and regular containers have been started. At the very moment of creation, no kubelet has even claimed the pod, so the API server reports Pending, not Running. Confusing the two ignores the scheduling and container-startup steps that must precede any running workload.
- ✓
Pending
Why this is correct
Pending is the correct phase for a pod immediately after it is created, because the pod object has been persisted in etcd but the scheduler has not yet assigned it to a node. Once scheduled, the phase still stays Pending while the container runtime pulls images, creates containers, and starts processes. Only after those actions complete does the phase transition to Running.
- ✗
Succeeded
Why it's wrong here
Succeeded is a terminal phase that indicates every container in the pod has exited with a zero status, which is typical for one-off Jobs rather than newly created pods. A brand-new pod has containers that have not even begun to execute, so a success exit is impossible. Treating Succeeded as the initial phase conflates completion with creation.
- ✗
Unknown
Why it's wrong here
The Unknown phase is reported when the kubelet on the pod's node stops responding to the API server, meaning the system cannot determine the actual pod state. A newly created pod is always known to be pending because it resides in the cluster store and can be observed by the control plane. Unknown therefore signals a communication failure, not a definitional starting point.
Go deeper
Related to this question
Learn chapter
Kubernetes Architecture Overview
Key term
Network Policies
A Kubernetes resource that controls how pods communicate with each other and with other network endpoints, acting as a firewall for pod-to-pod traffic.
Key term
Ingress Resources
Ingress Resources are Kubernetes API objects that manage external access to services inside a cluster, typically HTTP and HTTPS traffic, by defining rules for routing requests based on hostnames and paths.
About these practice questions
Courseiva writes every CKA question from scratch — 302 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CKA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKA exam.