Courseiva
Container Orchestration →mediumMultiple Choice

KCNA Container Orchestration Practice Question

A pod is in CrashLoopBackOff. You check the logs and see 'Error: container process not found'. What is the most likely cause?

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's entrypoint or command is incorrect

The container's entrypoint or command may be misconfigured, causing the container to exit immediately.

Answer analysis

Option-by-option breakdown

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

  • ✗

    The pod has insufficient memory

    Why it's wrong here

    Memory exhaustion triggers OOMKilled and exit code 137, not a missing process; the kubelet would report the container terminated by the kernel. Requests and limits tuning is the right fix when pods are repeatedly killed after starting, which is why it tempts. Here the image's entrypoint binary itself cannot be located.

  • ✗

    The liveness probe is misconfigured

    Why it's wrong here

    A misconfigured liveness probe causes restarts after the process starts, producing probe failure events rather than 'process not found'. Probe tuning is correct when containers run briefly then get killed by the kubelet. Here the runtime cannot locate the entrypoint binary at all, so the container never starts.

  • ✓

    The container's entrypoint or command is incorrect

    Why this is correct

    An incorrect entrypoint or command means the runtime cannot locate the executable to start, so the container exits immediately and Kubernetes restarts it repeatedly, producing CrashLoopBackOff. The log message 'container process not found' directly indicates the specified binary is missing or misnamed.

  • ✗

    The container image is missing

    Why it's wrong here

    A missing image yields ImagePullBackOff or ErrImagePull, since the kubelet cannot fetch it; the container never runs and no process error appears. Verifying image names and registry credentials is right for pull failures. Here the image pulled successfully but its entrypoint binary is absent.

About these practice questions

One of 930 original KCNA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This KCNA 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 KCNA exam.