KCNA Kubernetes Fundamentals Practice Question
An operator needs a workload that runs exactly one Pod on every node in the cluster, including nodes added later, to collect host-level logs. Which Kubernetes resource should be used?
⚠ Common exam trap
The trap here is assuming a Deployment with a replica count matching the number of nodes will spread Pods evenly, when the scheduler actually offers no such per-node guarantee.
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
✓
A DaemonSet
Per-node agents such as log shippers, node exporters, and CNI components are implemented as DaemonSets. The DaemonSet controller creates one Pod per eligible node and reacts to cluster membership changes by adding Pods on new nodes, which no replica-count-based controller can guarantee. Deployments, StatefulSets, and Jobs lack that node-scoped placement semantics.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A Job with a high parallelism value
Why it's wrong here
A Job runs Pods to completion and is designed for batch work, not for long-running per-node agents. It has no node affinity or per-node placement guarantee, so its Pods could all land on a single node and would terminate once their task finishes, making it unsuitable for continuous host log collection.
- ✗
A StatefulSet with podManagementPolicy set to Parallel
Why it's wrong here
StatefulSets provide stable identities and ordered or parallel management for stateful workloads, but they do not tie Pods to specific nodes or guarantee one Pod per node. Parallel pod management only changes startup ordering, so host-level coverage across every node, including newly added ones, would not be achieved.
- ✓
A DaemonSet
Why this is correct
A DaemonSet ensures that a copy of a Pod runs on every eligible node and automatically schedules new Pods onto nodes that join the cluster later. That matches the requirement of one log-collector Pod per node, including future nodes, without manual intervention or node-specific manifests.
- ✗
A Deployment with replicas equal to the node count
Why it's wrong here
A Deployment with a fixed replica count only guarantees the total number of Pods, not their placement. The scheduler may place several replicas on the same node and leave others empty, and when a node is added the Deployment does not automatically add a Pod for it, so per-node coverage is not assured.
Go deeper
Related to this question
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 →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CNCF exam blueprint
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.