An admin runs 'kubectl get pods' and sees a pod in 'CrashLoopBackOff' state. The pod's containers have a restart policy of 'Always'. What is the most likely cause?
Correct. A failing command causes the container to exit, and with Always restart policy, it restarts and fails again, leading to CrashLoopBackOff.
Why this answer
CrashLoopBackOff indicates the container keeps crashing after starting. The restart policy 'Always' causes the kubelet to restart it, but if the crash persists, the backoff delay increases. The most likely cause is the application itself failing (e.g., error on startup).