KCNA Kubernetes Fundamentals Practice Question
You need to run a one-time batch job that processes data and then exits. The job should run to completion and not be restarted. Which Kubernetes resource should you use?
⚠ Common exam trap
CNCF often tests the distinction between a Job and a CronJob, where candidates might mistakenly choose a CronJob for a one-time task, or confuse a Job's restart behavior with that of a Deployment's rolling update.
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
✓
Job
A Kubernetes Job is designed for one-time batch processing tasks that run to completion and are not restarted. It creates one or more Pods and ensures they successfully terminate, making it the correct choice for a non-repeating, finite workload.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
DaemonSet
Why it's wrong here
A DaemonSet schedules one pod per node to provide continuous node-level services, so it never reaches a completed state and restarts pods when they exit. It is tempting because it runs workloads automatically across nodes; it would be correct for log shippers, monitoring agents or CNI components on every node.
- ✓
Job
Why this is correct
A Kubernetes Job creates pods that run until successful completion, then stops — exactly matching the one-time batch requirement. Unlike a Deployment or ReplicaSet, which maintain a desired replica count and restart pods indefinitely, a Job's controller tracks completion and does not restart finished pods, satisfying the "run to completion and not be restarted" constraint.
- ✗
Deployment
Why it's wrong here
A Deployment maintains a desired replica count and restarts pods indefinitely, so the container would be relaunched after completing rather than running once to termination. It is tempting because Deployments are the default way to run containers; they would be correct for a long-running stateless service that must stay available.
- ✗
StatefulSet
Why it's wrong here
A StatefulSet also keeps pods running and restarts them, and its stable identities and persistent volume claims serve stateful workloads, not one-shot completion. It is tempting because it runs containers like other controllers; it would be correct for databases or clustered applications needing stable network names and ordered scaling.
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.