CKA Troubleshooting Practice Question
A node in your cluster is reporting 'NotReady'. You SSH into the node and run 'systemctl status kubelet'. The output shows 'Active: inactive (dead)'. Which command should you run FIRST to attempt to resolve this?
⚠ Common exam trap
The trap here is that candidates may jump to checking logs (Option A) or rebooting (Option C) without first attempting the simplest corrective action—starting the service—which is the direct fix for an inactive kubelet.
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
✓
systemctl start kubelet
The kubelet service is the primary Kubernetes agent on each node, and when it is 'inactive (dead)', the node cannot report its status to the control plane. The first step to restore the node is to start the kubelet service using 'systemctl start kubelet', which will attempt to bring the kubelet process back online and allow it to reconnect to the API server.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
journalctl -u kubelet
Why it's wrong here
While this command is invaluable for inspecting the systemd journal logs of the kubelet service to diagnose why it failed, it is purely a diagnostic tool. Running it will not change the state of the inactive service or bring the node back to a Ready state.
- ✗
systemctl status kubelet
Why it's wrong here
This command retrieves the current runtime state, process ID, and recent log lines of the kubelet systemd unit. Although it confirms whether the service is inactive or dead, it does not initiate any state transition or start the daemon.
- ✗
reboot
Why it's wrong here
Restarting the entire operating system is an intrusive, heavy-handed action that disrupts all other running node processes and containers. It should only be used as a last resort after targeted service recovery attempts, such as starting the kubelet directly, have failed.
- ✓
systemctl start kubelet
Why this is correct
Since the node is NotReady due to an inactive kubelet daemon, executing this command directly instructs systemd to launch the kubelet process. Once running, the kubelet will resume posting node status updates to the Kubernetes API server, restoring the node to a Ready state.
Visual reference
Go deeper
Related to this question
Learn chapter
Troubleshooting Cluster and Node Issues
Key term
Ingress Resources
Ingress Resources are Kubernetes API objects that manage external access to services inside a cluster, typically HTTP and HTTPS traffic, by defining rules for routing requests based on hostnames and paths.
Key term
Network Policies
A Kubernetes resource that controls how pods communicate with each other and with other network endpoints, acting as a firewall for pod-to-pod traffic.
About these practice questions
One of 726 original CKA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.