Courseiva
Kubernetes Fundamentals →easyMultiple Choice

KCNA Kubernetes Fundamentals Practice Question

A developer wants to run a one-time batch job that processes a queue and then terminates. Which Kubernetes resource should they use?

⚠ Common exam trap

It's easy for candidates to confuse a Job with a Deployment, assuming that any workload that 'runs' must be a Deployment, but Deployments are designed for long-running services and will restart terminated Pods, whereas a Job is the correct resource for workloads that should run to completion and then stop.

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 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.

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

    A Job creates pods that run to completion and then stops, tracking successful finishes rather than maintaining a persistent replica count. That matches a one-time batch process that drains a queue and terminates, unlike a Deployment, which restarts pods indefinitely.

  • ✗

    StatefulSet

    Why it's wrong here

    StatefulSet guarantees stable network identities and persistent per-pod storage for long-running stateful workloads; it restarts pods indefinitely rather than running to completion. It is tempting because it manages pods with ordered lifecycle control, but a queue-processing job needs a finite, terminating run, which is Job's completion semantics.

  • ✗

    Deployment

    Why it's wrong here

    A Deployment maintains a desired replica count continuously, restarting pods so they never terminate permanently; it has no completion tracking. It is tempting because it is the default workload controller for running containers, but a batch queue processor must run once to completion, which is Job's purpose.

  • ✗

    DaemonSet

    Why it's wrong here

    A DaemonSet schedules one pod per node for continuous node-level services such as log shippers or CNI agents; it never completes. It is tempting because it runs pods automatically across the cluster, but a one-time queue-processing task requires Job's run-to-completion behaviour, not per-node persistence.

About these practice questions

This KCNA question is part of Courseiva's 930-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.