KCNA Kubernetes Fundamentals Practice Question
Which Kubernetes command displays the current state of a pod, including its IP address, node, and container statuses?
⚠ Common exam trap
Test-takers frequently assume `kubectl get pod` alone shows all relevant pod details, but Kubernetes tests the specific requirement for the `-o wide` flag to expose the pod IP and node fields, which are hidden in the default output.
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 pod -o wide
`kubectl get pod -o wide` extends the default output to include additional columns such as the pod's IP address, the node it is scheduled on, and the container statuses (e.g., READY state). This command queries the Kubernetes API server for the pod's current state and formats the response with extra details, making it the most direct way to view the pod's IP and node assignment in a single line.
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 pod -o wide
Why this is correct
The -o wide output flag extends the default pod listing with the pod IP and node name, alongside status and container readiness. Plain kubectl get pod omits those columns, and describe or logs show different detail.
- ✗
kubectl describe pod
Why it's wrong here
This provides detailed information but is more verbose; the question asks for a command that 'displays' (implying get).
- ✗
kubectl logs pod
Why it's wrong here
Logs return container stdout and stderr output, not pod metadata such as IP address, node assignment or container statuses. It is the right command for debugging application errors, but inspecting pod state requires kubectl get pod with wide or JSON output.
- ✗
kubectl get pod
Why it's wrong here
Plain `kubectl get pod` lists only NAME, READY, STATUS, RESTARTS and AGE; the pod IP, node and per-container states require `-o wide` or `kubectl describe`. It is tempting because it is the standard quick inventory command for listing pods across a namespace, which suits checking existence or restart counts rather than inspecting a single pod's full runtime detail.
Go deeper
Related to this question
About these practice questions
Courseiva writes every KCNA question from scratch — 930 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This KCNA 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 KCNA exam.