Container Orchestration →easyMultiple ChoiceObjective-mapped

KCNA Container Orchestration Practice Question

Exhibit

Refer to the exhibit.

```
$ kubectl describe pod web-pod
...
Events:
  Type     Reason     Age   From               Message
  ----     ------     ----  ----               -------
  Normal   Scheduled  10m   default-scheduler  Successfully assigned default/web-pod to node-1
  Normal   Pulling    10m   kubelet            Pulling image "nginx:latest"
  Warning  Failed     9m58s kubelet            Failed to pull image "nginx:latest": rpc error: code = NotFound desc = image not found
  Warning  BackOff    9m57s kubelet            Back-off pulling image
```

Based on the exhibit, why is the pod web-pod not running?

⚠ Common exam trap

The KCNA exam often tests the distinction between pod scheduling failures (e.g., resource constraints, taints/tolerations) and container runtime failures (e.g., image pull errors), so candidates may confuse a 'Pending' pod with an 'ImagePullBackOff' pod, both of which are not running but have different root causes.

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

✓

The container image is not available in the registry.

The pod's status indicates an ImagePullBackOff error, which occurs when the kubelet fails to pull the specified container image from the registry. This typically means the image name or tag is incorrect, the registry is unreachable, or the image does not exist in the registry. The exhibit shows the pod is stuck in a waiting state with the reason 'ErrImagePull' or 'ImagePullBackOff', directly pointing to a missing or inaccessible image.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
A network policy is blocking the image pull.
Why it's wrong here
The error is 'image not found', not a network timeout or denial.
✓
The container image is not available in the registry.
Why this is correct
The error 'image not found' confirms the image is missing.
✗
The node does not have enough memory.
Why it's wrong here
No resource shortage events are shown.
✗
The pod was not scheduled onto a node.
Why it's wrong here
The event 'Successfully assigned' indicates scheduling succeeded.

Go deeper

KCNA Container Orchestration Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question