This CKA practice question tests your understanding of troubleshooting. 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.
A Node is in NotReady state. Which action should be taken first to diagnose the issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "first"
Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Check kubelet logs on the node
Why wrong: Useful but not the first step; describe node gives overview.
Restart kubelet
Why wrong: Recovery action, not diagnosis.
Check API server logs
Why wrong: Unlikely to show node conditions.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
kubectl describe node <node>
When a node is in NotReady state, the first diagnostic step is to gather information about the node's current status, conditions, and recent events using `kubectl describe node <node>`. This command reveals the node's conditions (e.g., Ready, DiskPressure, MemoryPressure), the last heartbeat timestamp, and any relevant events that may indicate the root cause, such as network issues or kubelet failures. It provides a high-level overview without requiring direct node access, making it the most efficient initial action.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Check kubelet logs on the node
Why it's wrong here
Useful but not the first step; describe node gives overview.
Restart kubelet
Why it's wrong here
Recovery action, not diagnosis.
Check API server logs
Why it's wrong here
Unlikely to show node conditions.
Option-by-option analysis
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CKA exam frequently reuses these exact scenarios with slightly different constraints.
Why this is wrong here
Useful but not the first step; describe node gives overview.
Why this is wrong here
Recovery action, not diagnosis.
Why this is wrong here
Unlikely to show node conditions.
Analysis generated from the official CKAblueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
The trap here is that candidates often jump to checking kubelet logs or restarting the kubelet, forgetting that `kubectl describe node` provides immediate visibility into node conditions and events from the control plane, which is the standard first step in the Kubernetes troubleshooting workflow.
Trap categories for this question
Command / output trap
Unlikely to show node conditions.
Detailed technical explanation
Under the hood, the node controller in the kube-controller-manager monitors node heartbeats via `NodeStatus` updates sent by the kubelet every `--node-status-update-frequency` (default 10s). If no update is received within `--node-monitor-grace-period` (default 40s), the node is marked as NotReady. `kubectl describe node` shows the `LastHeartbeatTime` and `Ready` condition status, helping you determine if the issue is a missed heartbeat or a condition like `DiskPressure` or `PIDPressure`. In a real-world scenario, a node might be NotReady due to a network partition, and checking the node description first avoids unnecessary SSH access to an unreachable node.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Troubleshooting — study guide chapter
Learn the concepts, then practise the questions
Troubleshooting 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise CKA questions linked to Cluster Architecture, Installation and Configuration.
Practise CKA questions linked to Services and Networking.
Practise CKA questions linked to Workloads and Scheduling.
Practise CKA questions linked to Storage.
Practise CKA questions linked to Troubleshooting.
Practise CKA questions linked to Cluster Architecture, Installation & Configuration.
Practise CKA questions linked to Workloads & Scheduling.
Practise CKA questions linked to Services & Networking.
Practise CKA questions linked to CKA fundamentals.
Practise CKA questions linked to CKA scenario.
Practise CKA questions linked to CKA troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Troubleshooting — This question tests Troubleshooting — Read the scenario before looking for a memorised answer..
The correct answer is: kubectl describe node <node> — When a node is in NotReady state, the first diagnostic step is to gather information about the node's current status, conditions, and recent events using `kubectl describe node <node>`. This command reveals the node's conditions (e.g., Ready, DiskPressure, MemoryPressure), the last heartbeat timestamp, and any relevant events that may indicate the root cause, such as network issues or kubelet failures. It provides a high-level overview without requiring direct node access, making it the most efficient initial action.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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 →
Keep practising
Last reviewed: Jun 11, 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.