KCNA Kubernetes Fundamentals Practice Question
Which THREE of the following are valid ways to assign a pod to a specific node? (Choose three.)
⚠ Common exam trap
Candidates often confuse direct node assignment (nodeName) with scheduling constraints (nodeSelector, nodeAffinity). ServiceAccount and clusterName do not affect node placement.
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
✓
Setting the 'nodeName' field in the pod spec
Setting the 'nodeName' field in the pod spec directly assigns the pod to a specific node by name. This bypasses the scheduler entirely, as the kubelet on that node will see the pod and attempt to run it. It is a valid, though inflexible, method for node assignment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Setting the 'nodeName' field in the pod spec
Why this is correct
Directly assigns the pod to a node.
- ✓
Using 'affinity' with 'nodeAffinity' rules
Why this is correct
Provides advanced node selection.
- ✓
Using 'nodeSelector' with label matching
Why this is correct
Selects nodes with matching labels.
- ✗
Using a ServiceAccount
Why it's wrong here
ServiceAccounts provide identity for pods, not node assignment.
- ✗
Setting the 'clusterName' field
Why it's wrong here
clusterName is not used for node assignment.
Go deeper
Related to this question
About these practice questions
Courseiva writes every KCNA question from scratch — 833 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 →
Same concept, more angles
2 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. Which TWO of the following are valid ways to assign a pod to a specific node?
medium- ✓ A.nodeSelector
- B.affinity: nodeAntiAffinity
- C.tolerations
- ✓ D.nodeName
- E.podSelector
Why A: `nodeSelector` is a simple, built-in field in the Pod spec that matches the pod to nodes with specific labels. When you add a `nodeSelector` with a key-value pair, the scheduler only places the pod on nodes that have that exact label. This is the most straightforward way to constrain a pod to a subset of nodes.
Variation 2. Which Kubernetes resource can be used to assign a pod to a specific node?
hard- ✓ A.Node affinity rules in the pod spec
- B.A NetworkPolicy
- C.A Service account
- D.A ConfigMap
Why A: Node affinity rules in the pod spec are a set of constraints that define which nodes a pod can be scheduled on, based on node labels. This is a native Kubernetes scheduling feature that allows you to attract pods to specific nodes using required or preferred matching rules, such as `requiredDuringSchedulingIgnoredDuringExecution`. This directly answers the question of assigning a pod to a specific node.
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.