KCNA Kubernetes Fundamentals Practice Question
You run 'kubectl logs my-pod' and see: "Error from server (BadRequest): container "my-container" in pod "my-pod" is waiting to start: PodInitializing". What does this mean?
⚠ Common exam trap
It's easy for candidates to confuse 'PodInitializing' with a container runtime failure or crash loop, when in fact it is a normal waiting state caused by init containers or pod initialization, not an error condition.
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
✓
The Pod is in the process of initializing and logs are not yet available
The error 'PodInitializing' indicates that the pod's init containers are still running or the main container is waiting for init containers to complete. During this phase, the container has not started, so logs are not yet available. Option D correctly identifies that the pod is initializing and logs cannot be retrieved until the container enters the 'Running' state.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The container is running but producing no output
Why it's wrong here
PodInitializing means init containers are still running, so the main container has not started and has produced no log output at all. It is tempting because a started container with a silent application also returns no lines, which would be the correct reading once the pod reaches Running state.
- ✗
The container runtime is failing to start the container
Why it's wrong here
The BadRequest arises because the container is waiting on init containers, not because the runtime failed; a genuine runtime failure surfaces as ImagePullBackOff, CrashLoopBackOff or a create-container error. It is tempting because waiting states often accompany start failures, which would be the right diagnosis if the status showed a runtime error rather than PodInitializing.
- ✗
The container has crashed and is restarting
Why it's wrong here
PodInitializing means init containers or image pulls are still completing, so the main container has not started at all; a crash-restart loop would instead show CrashLoopBackOff with a non-zero exit code. Restarting is the right diagnosis when logs reveal repeated container exits, not a pod still in its initialisation phase.
- ✓
The Pod is in the process of initializing and logs are not yet available
Why this is correct
The BadRequest arises because the container is still in the PodInitializing phase, so its log stream does not exist yet. Init containers or image pulls must finish before the kubelet starts the main container, at which point 'kubectl logs' will return output.
Go deeper
Related to this question
About these practice questions
Courseiva writes every KCNA question from scratch — 930 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 KCNA 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 KCNA exam.