easyMultiple ChoiceObjective-mapped
Google ACE Practice Question: A developer wants to see the details of a…
A developer wants to see the details of a specific GKE Pod including its events, container status, and resource requests/limits. Which kubectl command provides this?
⚠ Common exam trap
Google Cloud often tests the distinction between `get` and `describe`, where candidates mistakenly think `-o wide` or `-o json` provides the same event and status detail, but only `describe` automatically includes pod events and presents container status in a human-readable summary.
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 describe pod [POD_NAME]
B is correct because `kubectl describe pod` provides a comprehensive view of a pod, including its events (e.g., scheduling, pulling images), container status (e.g., waiting, running, terminated with reasons), and resource requests/limits (CPU and memory). This command aggregates detailed information from the Kubernetes API, making it the standard tool for debugging pod issues.
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 [POD_NAME] -o wide
Why it's wrong here
The -o wide flag adds the worker node and Pod IP to the default summary table, but it omits the diagnostics needed for troubleshooting: container state reasons, exit codes, image details, resource limits/requests, probe results, and lifecycle Events. It is best used for a quick inventory lookup, not for investigating why a Pod is CrashLoopBackOff or Pending. For that level of detail, kubectl describe retrieves the events and full container status.
- ✓
kubectl describe pod [POD_NAME]
Why this is correct
kubectl describe pod is the correct diagnostic command because it produces a categorized, human-readable report: Pod conditions, init-container and container states (including last terminated reason and exit code), resource requests and limits, QoS class, probe configuration, tolerations, volumes, and a dedicated Events section. That Events section is usually the fastest way to identify why a Pod cannot start—for example, image pull failures, unschedulable nodes, or liveness probe failures—making it the go-to first step in troubleshooting.
- ✗
kubectl inspect pod [POD_NAME]
Why it's wrong here
kubectl inspect is not a real kubectl verb; standard Kubernetes tooling has no such subcommand. Attempting it will produce an error like 'unknown command' and it will not show any Pod information. The analogous detail command is kubectl describe, which renders a human-readable summary of the Pod and its related events, while kubectl get -o yaml/json gives the raw API object for programmatic parsing.
- ✗
kubectl get pod [POD_NAME] -o json
Why it's wrong here
kubectl get pod -o json returns the entire Pod API object as JSON, including metadata, spec, and status fields. It does not aggregate related Event objects, so you miss the chronological list of scheduler, kubelet, and container runtime actions that explain a failure. While valid for automation, its verbose output is less practical than describe for interactive root-cause analysis because describe formats conditions and recent events with context.
Go deeper
Related to this question
Learn chapter
Google Kubernetes Engine (GKE)
Key term
GKE
GKE is Google's managed Kubernetes service that automates deploying, scaling, and managing containerized applications in the cloud.
Key term
Anthos
Anthos is a Google Cloud platform that lets you run applications consistently across different computing environments, like on-premises data centers and multiple public clouds.
About these practice questions
Courseiva writes every ACE question from scratch — 769 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 ACE practice question is part of Courseiva's free Google Cloud 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 ACE exam.