1V0-71.21 Question #37: Real Exam Question with Answer & Explanation

The correct answer is B. Event. When a Pod cannot be scheduled, Kubernetes emits an Event object describing why - for example, "Insufficient memory" or "No nodes match node selector." Events capture cluster-level actions and failures that occur before a Pod is running, making them the right place to look for sc

Explain Container and Kubernetes Concepts

Question

If a Kubernetes Pod cannot be scheduled, where can the reason be found?

Options

APod Spec
BEvent
CContainer logs
DPod Status

Explanation

When a Pod cannot be scheduled, Kubernetes emits an Event object describing why - for example, "Insufficient memory" or "No nodes match node selector." Events capture cluster-level actions and failures that occur before a Pod is running, making them the right place to look for scheduling failures (visible via kubectl describe pod <name>).

Why the distractors are wrong:

A. Pod Spec - defines what you want (resources, tolerations, selectors), not what went wrong at runtime.
C. Container logs - only exist once a container is actually running; a Pod stuck in Pending has no container to log from.
D. Pod Status - shows the current state (e.g., Pending) but not the detailed reason the scheduler rejected it; that narrative lives in Events.

Memory tip: Think of Events as Kubernetes' "complaint log." When something can't even start, check Events - when something started but misbehaves, check logs.

Topics

#Kubernetes Scheduling#Events#Pod Status#Troubleshooting

Community Discussion

No community discussion yet for this question.

Full 1V0-71.21 Practice