KCNA Kubernetes Fundamentals Practice Question
A container in a pod has been restarted multiple times with 'CrashLoopBackOff' state. What does this indicate?
⚠ Common exam trap
A common trap in the CNCF exam is the distinction between 'CrashLoopBackOff' (container exits immediately) and 'ImagePullBackOff' (image cannot be pulled), so candidates mistakenly choose the image pull failure option when they see 'BackOff' in the state name.
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 container exits with a non-zero exit code soon after starting
The 'CrashLoopBackOff' state indicates that a container in a pod repeatedly starts, exits with a non-zero exit code, and is then restarted by the kubelet. This loop triggers an exponential backoff delay, preventing the container from staying up. The core issue is that the container process fails almost immediately after starting, not that it is resource-constrained or unresponsive.
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 using too much memory
Why it's wrong here
Memory exhaustion produces OOMKilled termination, not the crash-restart backoff cycle itself; CrashLoopBackOff only reports that a container repeatedly exits and Kubernetes delays restarts. It is tempting because resource limits do cause crashes, but that diagnosis requires inspecting exit codes and events, not the pod status alone.
- ✓
The container exits with a non-zero exit code soon after starting
Why this is correct
CrashLoopBackOff means the kubelet repeatedly starts the container, sees it terminate, and applies exponential backoff before retrying. A non-zero exit code confirms the process itself fails soon after launch, satisfying the stem's repeated-restart condition rather than an image pull or scheduling fault.
- ✗
The container is running but not responding to health checks
Why it's wrong here
Liveness probe failures eventually trigger restarts, yet the container is not running and responding — it has exited, and the kubelet is backing off before retrying. It is tempting because probe misconfiguration is a common restart cause, but that scenario shows a running container being killed, not repeated crash exits.
- ✗
The container image cannot be pulled
Why it's wrong here
CrashLoopBackOff means the container starts then exits repeatedly, so the process itself is failing; an unpullable image yields ImagePullBackOff or ErrImagePull instead. It is tempting because both states block startup, and it would be correct when the kubelet cannot fetch the image from the registry.
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.