XK0-006 Automation, Orchestration, and Scripting Practice Question
An administrator is troubleshooting a Kubernetes deployment that is not receiving traffic. The deployment has one replica and the pod is running. The service is of type ClusterIP. Which command would help verify that the service endpoints are correctly associated with the pod?
⚠ Common exam trap
XK0-006 often tests whether candidates know that 'kubectl get svc' shows the selector but not the resolved endpoints, trapping those who assume the service output confirms pod association.
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
✓
kubectl get endpoints
The 'kubectl get endpoints' command lists the Endpoints object for a service, showing the IP addresses and ports of the pods that back it. If the service selector does not match the pod labels, the endpoints list will be empty, immediately revealing the misconfiguration. This is the fastest way to verify service-to-pod association.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
kubectl describe pod
Why it's wrong here
'kubectl describe pod' shows the pod's status, events and container details but not the Service's endpoint list, so it cannot confirm that the pod is registered as an endpoint. It is tempting because it is the standard first step for pod faults, and it would be correct for diagnosing image pull, scheduling or readiness probe failures.
- ✗
kubectl get pods -o wide
Why it's wrong here
Listing pods with wide output shows pod IPs and nodes, not whether the Service's EndpointSlice has registered the pod as a ready backend. It is tempting because it confirms the pod runs, but endpoint association is verified with kubectl get endpoints or describe service, which reveal the selected addresses.
- ✗
kubectl get svc
Why it's wrong here
'kubectl get svc' lists services and their cluster IPs but not the endpoint objects mapping those services to pod IPs, so it cannot confirm endpoint association. It is tempting because it is the quickest way to inspect a service, and it would be correct for checking service type, ports or cluster IP allocation.
- ✓
kubectl get endpoints
Why this is correct
`kubectl get endpoints` lists each Service's backing pod IPs and ports, directly confirming whether the ClusterIP Service's selector actually matched the running pod. Since the stem's constraint is a ClusterIP Service with no external exposure, endpoint association is the failure point to verify, and this command exposes an empty or mismatched endpoint list immediately.
Go deeper
Related to this question
About these practice questions
One of 781 original XK0-006 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This XK0-006 practice question is part of Courseiva's free CompTIA 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 XK0-006 exam.