- A
The new node has a taint that the DaemonSet pod does not tolerate
DaemonSet pods are created on all nodes unless the node has a taint that the pod does not tolerate. Adding a toleration to the DaemonSet pod template would fix this.
- B
The new node does not have enough resources to run the DaemonSet pod
Why wrong: If resources are insufficient, the pod would be in Pending state, not missing. The DaemonSet controller would still create the pod.
- C
The DaemonSet has a nodeSelector that does not match the new node's labels
Why wrong: If a nodeSelector is configured, it would prevent scheduling on any node that doesn't match, not just new nodes. The question says 'configured to run on all nodes', implying no nodeSelector or it matches all.
- D
The DaemonSet's update strategy is set to OnDelete
Why wrong: The update strategy affects how pods are updated, not whether they are created on new nodes. DaemonSet controllers automatically create pods on new nodes regardless of update strategy.
CKA Workloads and Scheduling Practice Question
This CKA practice question tests your understanding of workloads and scheduling. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A DaemonSet named 'fluentd' is configured to run on all nodes. After adding a new node to the cluster, you notice that the DaemonSet pod is not running on the new node. What could be the cause?
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
The new node has a taint that the DaemonSet pod does not tolerate
A DaemonSet ensures that a copy of a pod runs on all (or a subset of) nodes. When a new node is added, the DaemonSet controller automatically schedules a pod on it unless the node has a taint that the pod does not tolerate. By default, the new node may have a taint (e.g., `node.kubernetes.io/unschedulable` or a custom taint) that prevents the DaemonSet pod from being scheduled unless the pod's spec includes a matching toleration.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The new node has a taint that the DaemonSet pod does not tolerate
Why this is correct
DaemonSet pods are created on all nodes unless the node has a taint that the pod does not tolerate. Adding a toleration to the DaemonSet pod template would fix this.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The new node does not have enough resources to run the DaemonSet pod
Why it's wrong here
If resources are insufficient, the pod would be in Pending state, not missing. The DaemonSet controller would still create the pod.
- ✗
The DaemonSet has a nodeSelector that does not match the new node's labels
Why it's wrong here
If a nodeSelector is configured, it would prevent scheduling on any node that doesn't match, not just new nodes. The question says 'configured to run on all nodes', implying no nodeSelector or it matches all.
- ✗
The DaemonSet's update strategy is set to OnDelete
Why it's wrong here
The update strategy affects how pods are updated, not whether they are created on new nodes. DaemonSet controllers automatically create pods on new nodes regardless of update strategy.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse taints/tolerations with nodeSelector or resource constraints, assuming a new node would automatically accept all DaemonSet pods, when in fact taints are a common reason for scheduling failures on new nodes.
Detailed technical explanation
How to think about this question
Taints and tolerations are a Kubernetes scheduling mechanism that allows nodes to repel pods unless the pods explicitly tolerate the taint. When a new node joins the cluster, it may have a taint like `node.kubernetes.io/not-ready` or a custom taint applied by an administrator. The DaemonSet controller uses the default scheduler, which respects taints and tolerations; if the DaemonSet pod does not have a matching toleration, the pod will not be scheduled on that node. This is distinct from node affinity or nodeSelector, which are positive constraints, while taints are negative constraints.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the CKA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Workloads and Scheduling — study guide chapter
Learn the concepts, then practise the questions
- →
Workloads and Scheduling practice questions
Targeted practice on this topic area only
- →
All CKA questions
1,005 questions across all exam domains
- →
Certified Kubernetes Administrator CKA study guide
Full concept coverage aligned to exam objectives
- →
CKA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cluster Architecture, Installation and Configuration practice questions
Practise CKA questions linked to Cluster Architecture, Installation and Configuration.
Services and Networking practice questions
Practise CKA questions linked to Services and Networking.
Workloads and Scheduling practice questions
Practise CKA questions linked to Workloads and Scheduling.
Storage practice questions
Practise CKA questions linked to Storage.
Troubleshooting practice questions
Practise CKA questions linked to Troubleshooting.
Cluster Architecture, Installation & Configuration practice questions
Practise CKA questions linked to Cluster Architecture, Installation & Configuration.
Workloads & Scheduling practice questions
Practise CKA questions linked to Workloads & Scheduling.
Services & Networking practice questions
Practise CKA questions linked to Services & Networking.
CKA fundamentals practice questions
Practise CKA questions linked to CKA fundamentals.
CKA scenario practice questions
Practise CKA questions linked to CKA scenario.
CKA troubleshooting practice questions
Practise CKA questions linked to CKA troubleshooting.
Practice this exam
Start a free CKA practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CKA question test?
Workloads and Scheduling — This question tests Workloads and Scheduling — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The new node has a taint that the DaemonSet pod does not tolerate — A DaemonSet ensures that a copy of a pod runs on all (or a subset of) nodes. When a new node is added, the DaemonSet controller automatically schedules a pod on it unless the node has a taint that the pod does not tolerate. By default, the new node may have a taint (e.g., `node.kubernetes.io/unschedulable` or a custom taint) that prevents the DaemonSet pod from being scheduled unless the pod's spec includes a matching toleration.
What should I do if I get this CKA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
This CKA 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 CKA exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.