CKAD Application Observability and Maintenance Practice Question
Network Topology
Based on the exhibit, what should you do to determine why the container is failing?
⚠ Common exam trap
CNCF often tests the distinction between pod-level metadata (describe/events) and application-level output (logs), and the trap here is that candidates may choose 'kubectl describe pod' thinking it shows all failure details, but it does not include the container's stdout/stderr logs.
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
✓
Run 'kubectl logs backend' to view the container's stdout/stderr.
The container is failing, and the most direct way to determine why is to inspect its stdout/stderr logs using 'kubectl logs backend'. This command retrieves the container's log output, which typically contains error messages, stack traces, or application-level failure reasons. In CKAD scenarios, when a pod is in CrashLoopBackOff or Error state, logs are the first diagnostic step to identify the root cause.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Run 'kubectl describe pod backend' to see the pod's status.
Why it's wrong here
kubectl describe pod backend aggregates pod metadata, status conditions, and recent events, but because you have already inspected events and seen the CrashLoopBackOff state, it will likely repeat the same backoff/restart information without exposing the process-level failure. The describe output does not include the container's application stdout/stderr, so it cannot reveal why the process inside the container exits non-zero. Logs are the direct source for the crash reason.
- ✗
Run 'kubectl get events' with a different filter to capture more details.
Why it's wrong here
kubectl get events with a different filter, such as --field-selector involvedObject.name=backend or --watch, can surface additional Event objects, yet the existing event stream already identified the symptom as BackOff/restarting, not the underlying cause. Event objects are generated by the kubelet and contain only high-level warnings such as failed health checks or image pull failures; they do not capture the application's own error output. Thus re-filtering events merely changes the view, not the diagnostic depth.
- ✗
Check if the image tag '1.0' exists in the registry.
Why it's wrong here
Checking the registry for whether the image tag '1.0' exists assumes a pull problem, but the exhibit indicates the image is already present on the node and the pod is stuck in a restart loop, not ImagePullBackOff. Since the kubelet has already pulled the image successfully, verifying the tag's existence in the registry would not explain an application crash after container start. The relevant failure occurs in the container's runtime process, not during image resolution.
- ✓
Run 'kubectl logs backend' to view the container's stdout/stderr.
Why this is correct
kubectl logs backend fetches the container's captured stdout/stderr streams, which is exactly where a typical application writes its error, panic, or stack trace before exiting. For a pod in CrashLoopBackOff, kubectl logs with --previous can show the logs from the crashed container instance, revealing the root cause of the non-zero exit. This is the most direct way to determine why the process terminates.
Go deeper
Related to this question
Learn chapter
Multi-Container Pods and Sidecar Patterns
Key term
Metrics Server
The Metrics Server is a cluster-wide aggregator of resource usage data in Kubernetes, collecting CPU and memory metrics from nodes and pods for autoscaling and monitoring.
Key term
Container Logs
Container logs are records of output generated by applications running inside a container, showing what the application did, errors it encountered, or status updates it produced.
About these practice questions
This CKAD question is part of Courseiva's 826-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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 CKAD 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 CKAD exam.