CKA Troubleshooting Practice Question
A pod in the 'production' namespace is in a CrashLoopBackOff state. The pod has been running successfully for several days. You run 'kubectl describe pod app-pod -n production' and see the message: 'OOMKilled'. What is the MOST appropriate action to resolve this issue?
⚠ Common exam trap
Candidates often confuse OOMKilled with a general crash loop and choose to delete/recreate the pod, not realizing that the pod will simply crash again with the same memory limit.
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
✓
Increase the memory limit in the pod's container resource specification
The OOMKilled status indicates the container was terminated by the Linux Out-of-Memory (OOM) killer because it exceeded its memory limit. Increasing the memory limit in the pod's container resource specification allows the container to use more memory without being killed, directly addressing the root cause of the crash loop.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Increase the memory limit in the pod's container resource specification
Why this is correct
A CrashLoopBackOff status frequently indicates that a container is repeatedly crashing and being restarted by Kubernetes. When the underlying cause is an OOMKilled event, it means the container attempted to consume more memory than specified by its configured `resources.limits.memory`. Increasing this memory limit directly addresses the root cause by providing the container with sufficient memory resources, thereby preventing the operating system from terminating the process due to out-of-memory conditions and allowing the pod to stabilize.
- ✗
Increase the CPU request for the container
Why it's wrong here
Increasing the CPU request for a container primarily influences the Kubernetes scheduler's placement decisions and the amount of CPU time guaranteed to the container, but it does not affect its memory allocation or limits. An OOMKilled event, which leads to a CrashLoopBackOff, is specifically triggered when a process exceeds its assigned memory limit. Therefore, modifying CPU resources will not resolve a memory exhaustion issue, as these are distinct resource types managed independently by the kernel and Kubernetes scheduler.
- ✗
Delete and recreate the pod to clear the crash loop
Why it's wrong here
Deleting and recreating a pod merely restarts the container with the exact same configuration, including its insufficient memory limits. Since the CrashLoopBackOff status indicates a recurring problem, such as an OOMKilled event, simply restarting the pod without addressing the underlying resource constraint will inevitably lead to the same memory exhaustion and subsequent crash. This action provides no lasting solution and will only result in the pod returning to the CrashLoopBackOff state.
- ✗
Delete the namespace and redeploy all workloads
Why it's wrong here
Deleting an entire namespace is an extremely destructive and disproportionate action for resolving a CrashLoopBackOff issue affecting a single pod. This operation would indiscriminately terminate all running pods, services, deployments, and other resources within that namespace, causing significant downtime and potential data loss for all applications. A targeted approach, addressing the specific pod's resource configuration, is always preferred over such a broad and impactful intervention.
Visual reference
Go deeper
Related to this question
Learn chapter
Configuring Scheduling and Affinity
Key term
Pod Failure Troubleshooting
Pod failure troubleshooting is the process of identifying and resolving issues that cause Kubernetes pods to crash, restart, or become unavailable.
Key term
kubectl Command Reference
kubectl is the command-line tool used to interact with and manage Kubernetes clusters by sending commands to the Kubernetes API.
About these practice questions
One of 302 original CKA 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CKA 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 CKA exam.