KCNA Container Orchestration Practice Question
What is the difference between a liveness probe and a readiness probe?
⚠ Common exam trap
It's easy for candidates to confuse the purpose of liveness and readiness probes, often thinking liveness controls traffic routing or that readiness triggers restarts, when in fact liveness governs restarts and readiness governs traffic inclusion.
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
✓
Liveness probe indicates if the container is alive; if it fails, the container is restarted
A liveness probe determines if a container is still running (alive). If the liveness probe fails, Kubernetes restarts the container based on the `restartPolicy`. This is distinct from a readiness probe, which checks if a container is ready to accept traffic and removes it from Service endpoints if it fails.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Liveness probe checks if the container is ready to serve traffic
Why it's wrong here
Readiness determines whether the container receives traffic; liveness determines whether the container is restarted. The option swaps these roles. It is tempting because both probes use the same handler mechanisms, and readiness would be the answer if the question asked which probe removes a pod from service endpoints.
- ✗
Readiness probe indicates if the container is healthy; liveness indicates if it should be restarted
Why it's wrong here
Readiness probes govern Service endpoint membership, not health reporting; liveness probes detect deadlocks and restart containers. This option swaps those roles, so it misstates which probe removes a Pod from load balancing. It is tempting because both probes run commands against containers, and readiness failures do precede restarts when liveness is also misconfigured.
- ✓
Liveness probe indicates if the container is alive; if it fails, the container is restarted
Why this is correct
The liveness probe checks whether the container is running; failure triggers a restart to recover from deadlocks or crashes. This differs from the readiness probe, which controls traffic routing, so the stated restart behaviour correctly describes liveness.
- ✗
Both probes serve the same purpose but with different endpoints
Why it's wrong here
Liveness and readiness probes differ in mechanism and consequence: liveness restarts a container when it fails, while readiness removes the Pod from Service endpoints without restarting it. Claiming identical purpose with different endpoints collapses that distinction. Endpoint variation alone is tempting because both probes use HTTP, TCP or exec handlers, but handler choice never determines probe behaviour.
Go deeper
Related to this question
About these practice questions
One of 930 original KCNA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.