KCNA Kubernetes Fundamentals Practice Question
You have a Pod that needs to run a one-time batch job to completion. Which resource type should you use?
⚠ Common exam trap
It's easy for candidates to confuse a Job with a Deployment, thinking that any workload that runs a container should use a Deployment, but Deployments are designed for long-running services, not ephemeral batch tasks.
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 Job resource is designed for running a finite task to completion, such as a batch job or a one-time computation. Unlike controllers that maintain a desired number of replicas indefinitely, a Job creates one or more Pods and tracks their successful termination. Once the specified number of completions is reached, the Job is considered finished and no further Pods are created.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Job
Why this is correct
Jobs run Pods to completion.
- ✗
StatefulSet
Why it's wrong here
StatefulSet is for stateful applications with stable identities.
- ✗
DaemonSet
Why it's wrong here
DaemonSet runs Pods on all or selected nodes.
- ✗
Deployment
Why it's wrong here
Deployments expect Pods to run continuously.
Go deeper
Related to this question
About these practice questions
One of 833 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 →
Same concept, more angles
6 more ways this is tested on KCNA
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A user wants to run a one-time batch job that runs to completion. Which Kubernetes resource should they use?
medium- ✓ A.Job
- B.StatefulSet
- C.DaemonSet
- D.Deployment
Why A: A Kubernetes Job is the correct resource for a one-time batch job that runs to completion. Unlike controllers designed for long-running processes, a Job creates one or more Pods and ensures they successfully terminate, making it ideal for finite tasks like data processing or backups.
Variation 2. 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?
hard- A.DaemonSet
- ✓ B.Job
- C.Deployment
- D.StatefulSet
Why B: 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.
Variation 3. You need to run a batch job that processes data and then exits. Which Kubernetes resource type is most appropriate for this workload?
medium- A.Deployment
- B.DaemonSet
- ✓ C.Job
- D.StatefulSet
Why C: A Kubernetes Job is designed for workloads that run to completion and then exit, such as batch processing, data transformation, or one-off tasks. Unlike controllers that maintain a desired number of running Pods (like Deployments), Jobs ensure that a specified number of Pods successfully terminate, making them the correct choice for this scenario.
Variation 4. You want to run a batch job that processes data and then terminates. Which Kubernetes resource is best suited for this workload?
medium- A.StatefulSet
- B.DaemonSet
- ✓ C.Job
- D.Deployment
Why C: A Kubernetes Job is designed for batch processing workloads that run to completion and then terminate. Unlike controllers that maintain a desired number of running Pods (like Deployments or StatefulSets), a Job creates one or more Pods and ensures they successfully exit. Once the specified number of successful completions is reached, the Job stops, making it the ideal choice for a one-time data processing task.
Variation 5. A developer wants to run a one-time batch job that processes a queue and then terminates. Which Kubernetes resource should they use?
easy- ✓ A.Job
- B.StatefulSet
- C.Deployment
- D.DaemonSet
Why A: A Kubernetes Job is designed for finite, batch-oriented tasks that run to completion, such as processing a queue and then terminating. Unlike controllers that maintain a desired state (like Deployments or StatefulSets), a Job creates one or more Pods and ensures they successfully exit, making it the correct choice for a one-time batch job.
Variation 6. You need to run a batch job that processes a queue and then terminates. Which Kubernetes resource is most appropriate?
medium- A.StatefulSet
- ✓ B.Job
- C.Deployment
- D.DaemonSet
Why B: A Job is the correct resource because it is designed to run a specified number of pods to completion and then terminate, making it ideal for batch processing tasks like processing a queue. Unlike controllers that maintain a desired state indefinitely, a Job ensures the pod runs successfully to completion, even if the pod fails and needs to be restarted, and then stops.
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.