Question 777 of 991
Application Observability and MaintenancemediumMultiple ChoiceObjective-mapped

CKAD Application Observability and Maintenance Practice Question

This CKAD practice question tests your understanding of application observability and maintenance. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.

Network Topology
$ kubectl get eventsfield-selector involvedObject.kind=Podsort-by=.metadata.creationTimestampRefer to the exhibit.```

Based on the exhibit, what should you do to determine why the container is failing?

Question 1mediummultiple choice
Full question →
Network Topology
$ kubectl get eventsfield-selector involvedObject.kind=Podsort-by=.metadata.creationTimestampRefer to the exhibit.```

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.

Option D is correct because 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.

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.

  • Run 'kubectl describe pod backend' to see the pod's status.

    Why it's wrong here

    Already saw events; describe may show additional info but logs are more direct.

  • Run 'kubectl get events' with a different filter to capture more details.

    Why it's wrong here

    Events already show BackOff, but not the root cause.

  • Check if the image tag '1.0' exists in the registry.

    Why it's wrong here

    The image is already present on the node, so pulling is not the issue.

  • Run 'kubectl logs backend' to view the container's stdout/stderr.

    Why this is correct

    Logs may show the application error causing the crash.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

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.

Trap categories for this question

  • Command / output trap

    Already saw events; describe may show additional info but logs are more direct.

Detailed technical explanation

How to think about this question

Under the hood, 'kubectl logs' retrieves the container's log stream from the kubelet, which reads from the container runtime's log file (e.g., /var/log/pods/ on the node). In a CrashLoopBackOff scenario, you can use 'kubectl logs --previous backend' to see logs from the last terminated container instance, which is critical when the container restarts too quickly to capture logs. A real-world scenario is a misconfigured database connection string causing the app to crash on startup, which would appear in the logs but not in pod events.

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 CKAD 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.

Related practice questions

Related CKAD practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free CKAD 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 CKAD question test?

Application Observability and Maintenance — This question tests Application Observability and Maintenance — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Run 'kubectl logs backend' to view the container's stdout/stderr. — Option D is correct because 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.

What should I do if I get this CKAD question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 2026

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.

Loading comments…

Sign in to join the discussion.

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.