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
It's easy for candidates to confuse OOMKilled with a CPU-related issue or think that simply restarting the pod will fix the problem, but the OOMKilled status explicitly indicates memory exhaustion, requiring a resource limit adjustment.
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 pod is in CrashLoopBackOff with an OOMKilled message, which means the container was terminated by the Linux kernel's Out-Of-Memory (OOM) killer because it exceeded its memory limit. The correct fix is to increase the memory limit in the container's resource specification, allowing the container to use more memory without being killed. Simply deleting and recreating the pod would not resolve the underlying memory constraint, and adjusting CPU or deleting the namespace are irrelevant actions.
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 CPU request for the container
Why it's wrong here
A `CrashLoopBackOff` status often indicates a container is repeatedly failing to start or stay running. If the underlying cause is `OOMKilled` (Out Of Memory Killed), it signifies the container attempted to use more memory than its configured limit. Increasing the CPU request only allocates more CPU resources, which is unrelated to memory consumption and will not resolve a memory exhaustion issue. The container will still be killed by the kernel when it exceeds its memory limit.
- ✓
Increase the memory limit in the pod's container resource specification
Why this is correct
When a pod's container enters `CrashLoopBackOff` due to an `OOMKilled` event, it means the container tried to consume memory beyond its defined `limits.memory` in the pod specification. By increasing this memory limit, you provide the container with more available RAM, preventing the operating system's OOM killer from terminating the process. This allows the application to run stably without memory exhaustion, resolving the crash loop.
- ✗
Delete and recreate the pod to clear the crash loop
Why it's wrong here
Simply deleting and recreating the pod will not resolve the `CrashLoopBackOff` if the root cause is an `OOMKilled` event. The new pod will be scheduled with the exact same resource specifications, including the insufficient memory limit. Consequently, the container will again attempt to allocate more memory than permitted, leading to another `OOMKilled` event and perpetuating the crash loop. A configuration change is required.
- ✗
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 single pod's `CrashLoopBackOff` issue. This operation would permanently remove all resources, including deployments, services, and persistent volumes, within that namespace, causing significant downtime and data loss for all affected applications. A targeted adjustment to the specific pod's resource limits is the correct and least disruptive approach.
Visual reference
Go deeper
Related to this question
Learn chapter
Configuring Storage Classes and Dynamic Provisioning
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.
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.
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.