A pod can resolve external DNS names, but it cannot resolve a Service name like `my-service.default.svc.cluster.local`. `kubectl get svc` shows the Service exists. What is the most likely cause?

The Service's ClusterIP is incorrect.

The pod's `/etc/resolv.conf` is missing the cluster DNS server.

The CoreDNS pod is not running or is misconfigured.

Pods can communicate with each other across nodes, but a pod cannot reach an external IP address (e.g., 8.8.8.8). The node's iptables NAT table has a MASQUERADE rule for the pod CIDR. What is the most likely cause?

The CoreDNS is not resolving external names.

The node's default gateway is not configured or is unreachable.

The CNI plugin is misconfigured.

The kubelet on a worker node is in a failed state. What is the safest way to restart it without affecting running workloads?

systemctl stop kubelet && systemctl start kubelet

Certified Kubernetes Administrator (CKA)

Domain 2Objective 2

Troubleshoot Cluster Components CKA Practice Questions (Page 3)

Part of the Troubleshooting domain, which accounts for 30% of the CKA exam. Linux Foundation does not publish an official question count, but from its 120-minute exam (~50–80 total, ~15–24 in this domain), expect 3–5 from this objective — we provide 23 practice questions to prepare you well beyond it. (estimate)

23questions here

5free pages

6concepts

30%of the exam

Questions 11–15

11foundation · easy
Pods are not being scheduled to a worker node, and the node is Ready. Which component's logs would you inspect to determine if the node is tainted?
Select an answer first
12application · medium
A pod can resolve external DNS names, but it cannot resolve a Service name like `my-service.default.svc.cluster.local`. `kubectl get svc` shows the Service exists. What is the most likely cause?
Select an answer first
13expert · hard
Pods can communicate with each other across nodes, but a pod cannot reach an external IP address (e.g., 8.8.8.8). The node's iptables NAT table has a MASQUERADE rule for the pod CIDR. What is the most likely cause?
Select an answer first
14foundation · easy
You need to see the recent events for a pod that is CrashLoopBackOff. Which kubectl command provides a list of events related to that pod?
Select an answer first
15foundation · easy
The kubelet on a worker node is in a failed state. What is the safest way to restart it without affecting running workloads?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CKA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Foundation. “CKA” is a trademark of its owner, used for identification only.

Troubleshoot Cluster Components CKA Practice Questions (Page 3)

Questions 11–15

Pods are not being scheduled to a worker node, and the node is Ready. Which component's logs would you inspect to determine if the node is tainted?

A pod can resolve external DNS names, but it cannot resolve a Service name like `my-service.default.svc.cluster.local`. `kubectl get svc` shows the Service exists. What is the most likely cause?

Pods can communicate with each other across nodes, but a pod cannot reach an external IP address (e.g., 8.8.8.8). The node's iptables NAT table has a MASQUERADE rule for the pod CIDR. What is the most likely cause?

You need to see the recent events for a pod that is CrashLoopBackOff. Which kubectl command provides a list of events related to that pod?

The kubelet on a worker node is in a failed state. What is the safest way to restart it without affecting running workloads?

Keep studying — Troubleshooting