A parks recreation site sets imagePullPolicy to Never for an image that exists only in a private registry, and worker nodes cannot find it locally. Which pull policy fits this situation?
Select an answer to reveal the explanation.
Short Explanation
Never means "I already have this photo on my phone—don't download it." If the photo is only in the cloud gallery (registry), that setting just fails. Let the kubelet pull with Always or IfNotPresent when the node does not already hold the image.
Full Explanation
Parks recreation workloads that set imagePullPolicy to Never tell the kubelet never to contact the registry. That only works when the exact image already exists locally on the scheduled node. If the recreation site image lives only in a private registry, Never yields ErrImageNeverPull. Use Always or IfNotPresent so the kubelet can pull when layers are missing; IfNotPresent is common for tagged releases, while Always is typical with :latest (which you should still avoid for production pinning).
Keeping Never and docker loading only on a control-plane node fails because application Pods usually schedule on workers that never received the load. Switching to a Job with restartPolicy Never confuses Pod restart semantics with image pull policy; Jobs still need pullable images. Raising replicas until a node happens to have layers is nondeterministic and still fails on clean nodes.
Exam caveat: imagePullPolicy interacts with tag mutability. Never is for pre-loaded/air-gapped cases you control, not private registry defaults. CKAD tests whether you pick a policy that allows the kubelet to fetch application images.
Operational check: kubectl describe pod and look for Failed to pull / ErrImageNeverPull; patch imagePullPolicy to IfNotPresent or Always, ensure imagePullSecrets exist for private registries, and recheck events for Successfully pulled image.