The answer is to check the kubelet service status on the node using systemctl status kubelet and to inspect the node’s conditions with kubectl describe node <node-name>. These two actions are correct because a kubelet upgrade often introduces version mismatches or configuration drift that prevents the kubelet from reporting its health to the control plane; checking the service status reveals whether the kubelet process is running or has failed, while kubectl describe node surfaces the underlying condition—such as KubeletNotReady or NetworkUnavailable—that explains the NotReady state. On the Certified Kubernetes Administrator CKA exam, this scenario tests your ability to distinguish between control-plane and node-level diagnostics, with a common trap being to restart the kubelet blindly without first verifying its logs or the node’s conditions. Remember the mnemonic: “Service first, describe second” — always confirm the kubelet is alive before digging into node conditions.
CKA Practice Question: Cluster Architecture, Installation and Configuration
This CKA practice question tests your understanding of cluster architecture, installation and configuration. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
You have a multi-node Kubernetes cluster. After upgrading the kubelet on a worker node, the node remains in 'NotReady' state. Which TWO actions should you take to troubleshoot? (Choose TWO.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Check the node conditions using 'kubectl describe node <node-name>'
Option A is correct because 'kubectl describe node <node-name>' shows node conditions, including the 'Ready' status and any underlying issues like 'NetworkUnavailable', 'MemoryPressure', or 'KubeletNotReady'. This command provides a high-level view of why the node is NotReady, such as a kubelet version mismatch or resource exhaustion. It is the standard first step in diagnosing node health.
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.
✓
Check the node conditions using 'kubectl describe node <node-name>'
Why this is correct
This provides details on node status, including conditions like Ready.
Related concept
Read the scenario before looking for a memorised answer.
✗
Check the pod logs on the node
Why it's wrong here
Pod logs are not relevant to node-level readiness.
✓
Check the kubelet service status on the node using 'systemctl status kubelet'
Why this is correct
This shows if kubelet is running and any errors.
Related concept
Read the scenario before looking for a memorised answer.
✗
Check the kube-apiserver logs on the control plane
Why it's wrong here
This is not directly related to a single worker node's readiness.
✗
Reboot the node
Why it's wrong here
Rebooting may be a last resort but not a troubleshooting step.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often jump to checking the kube-apiserver logs (Option D) or rebooting (Option E) instead of focusing on the node's local kubelet service, which is the direct source of the NotReady state.
Detailed technical explanation
How to think about this question
The kubelet is the primary node agent that registers the node with the API server and reports its status via periodic heartbeats (node-status-update-frequency, default 10s). After an upgrade, the kubelet may fail to start due to incompatible configuration flags, missing dependencies, or a version skew that violates the supported skew policy (e.g., kubelet version must be within one minor version of kube-apiserver). Checking 'systemctl status kubelet' reveals the exact error from the kubelet's systemd unit, such as a failed TLS bootstrap or a missing CNI plugin.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CKA question in full detail.
Cluster Architecture, Installation and Configuration — This question tests Cluster Architecture, Installation and Configuration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Check the node conditions using 'kubectl describe node <node-name>' — Option A is correct because 'kubectl describe node <node-name>' shows node conditions, including the 'Ready' status and any underlying issues like 'NetworkUnavailable', 'MemoryPressure', or 'KubeletNotReady'. This command provides a high-level view of why the node is NotReady, such as a kubelet version mismatch or resource exhaustion. It is the standard first step in diagnosing node health.
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 →
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.
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.