- A
kubectl get svc <service-name> -o yaml
Why wrong: This shows service spec, but endpoints are managed separately.
- B
kubectl get pods -l <selector>
Why wrong: This shows pods but not whether they are correctly targeted by the service.
- C
kubectl describe service <service-name>
Why wrong: This shows service details but not necessarily endpoint issues; endpoints command is more direct.
- D
kubectl get endpoints <service-name>
This command shows the endpoints (pod IPs) associated with the service.
How to Verify NodePort Service Endpoints with kubectl
This CKS practice question tests your understanding of monitoring, logging and runtime security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 NodePort service is not accessible from outside the cluster. Which command should you use to check if the service's endpoints are correctly populated?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"which command"Why it matters: Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
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 <service-name>
Option D is correct because `kubectl get endpoints <service-name>` directly shows the IP addresses and ports of the Pods that the Service is routing traffic to. If the endpoints list is empty, the Service has no healthy Pods backing it, which explains why the NodePort is unreachable from outside the cluster. This command is the most direct way to verify that the Service's selector matches running Pods and that the endpoints controller has populated the Endpoints object.
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.
- ✗
kubectl get svc <service-name> -o yaml
Why it's wrong here
This shows service spec, but endpoints are managed separately.
- ✗
kubectl get pods -l <selector>
Why it's wrong here
This shows pods but not whether they are correctly targeted by the service.
- ✗
kubectl describe service <service-name>
Why it's wrong here
This shows service details but not necessarily endpoint issues; endpoints command is more direct.
- ✓
kubectl get endpoints <service-name>
Why this is correct
This command shows the endpoints (pod IPs) associated with the service.
Clue confirmation
The clue word "which command" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose `kubectl describe service` (Option C) because it shows the selector and port information, but they overlook that it does not display the actual endpoint IPs, which is the critical piece of information needed to diagnose why the NodePort is unreachable.
Trap categories for this question
Command / output trap
This shows service spec, but endpoints are managed separately.
Detailed technical explanation
How to think about this question
Under the hood, the Endpoints controller in kube-controller-manager watches Pods that match a Service's label selector and satisfy readiness gates, then writes the IP:port pairs into the Endpoints object. A NodePort Service relies on kube-proxy to install iptables or IPVS rules that forward traffic to these endpoint IPs; if the Endpoints object is empty, kube-proxy will not install any forwarding rules, making the NodePort unreachable. In real-world scenarios, a common subtlety is that a Service with `externalTrafficPolicy: Local` will only populate endpoints for Pods on the same node, which can cause empty endpoints on nodes without a matching Pod.
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 CKS 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
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Monitoring, Logging and Runtime Security — study guide chapter
Learn the concepts, then practise the questions
- →
Monitoring, Logging and Runtime Security practice questions
Targeted practice on this topic area only
- →
All CKS questions
997 questions across all exam domains
- →
Certified Kubernetes Security Specialist CKS study guide
Full concept coverage aligned to exam objectives
- →
CKS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Monitoring Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring Logging and Runtime Security.
Cluster Setup and Hardening practice questions
Practise CKS questions linked to Cluster Setup and Hardening.
System Hardening practice questions
Practise CKS questions linked to System Hardening.
Minimize Microservice Vulnerabilities practice questions
Practise CKS questions linked to Minimize Microservice Vulnerabilities.
Supply Chain Security practice questions
Practise CKS questions linked to Supply Chain Security.
Monitoring, Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring, Logging and Runtime Security.
Cluster Setup practice questions
Practise CKS questions linked to Cluster Setup.
Cluster Hardening practice questions
Practise CKS questions linked to Cluster Hardening.
CKS fundamentals practice questions
Practise CKS questions linked to CKS fundamentals.
CKS scenario practice questions
Practise CKS questions linked to CKS scenario.
CKS troubleshooting practice questions
Practise CKS questions linked to CKS troubleshooting.
Practice this exam
Start a free CKS practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CKS question test?
Monitoring, Logging and Runtime Security — This question tests Monitoring, Logging and Runtime Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: kubectl get endpoints <service-name> — Option D is correct because `kubectl get endpoints <service-name>` directly shows the IP addresses and ports of the Pods that the Service is routing traffic to. If the endpoints list is empty, the Service has no healthy Pods backing it, which explains why the NodePort is unreachable from outside the cluster. This command is the most direct way to verify that the Service's selector matches running Pods and that the endpoints controller has populated the Endpoints object.
What should I do if I get this CKS question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "which command". Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
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 →
Keep practising
More CKS practice questions
- Which flag is used to restrict the kubelet's ability to modify node status and pods?
- A Falco rule has priority `WARNING` and output: `Sensitive file opened (user=%user.name command=%proc.cmdline file=%fd.n…
- Falco detects a shell being opened inside a container. Which Falco rule field is used to specify the syscall condition f…
- A security audit reveals that a ServiceAccount named 'monitor' has a ClusterRoleBinding to the cluster-admin role. What…
- Match each Kubernetes security component to its description.
- Match each Kubernetes certificate type to its usage.
Last reviewed: Jul 4, 2026
This CKS 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 CKS 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.