KCNA Kubernetes Fundamentals 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
A common trap in the CNCF Kubernetes exams is assuming that CrashLoopBackOff always requires pod deletion or restart, but OOMKilled is a resource limit issue that must be fixed by adjusting the memory limit, not by recreating the pod.
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 due to OOMKilled, meaning the container exceeded its memory limit and was terminated by the Linux kernel's Out-Of-Memory (OOM) killer. Increasing the memory limit in the pod's container resource specification allows the container to allocate more memory without being killed, resolving the crash loop. This directly addresses the root cause—insufficient memory limit—without affecting other resources or requiring full redeployment.
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
OOMKilled means the kernel terminated the container for exceeding its memory limit, so raising that limit gives the process the headroom it needs. The pod ran for days before failing, indicating a genuine memory ceiling rather than a configuration or image fault.
- ✗
Increase the CPU request for the container
Why it's wrong here
OOMKilled means the container exceeded its memory limit, so raising the CPU request leaves the memory constraint untouched and the pod keeps being killed. It is tempting because CPU and memory are both container resources, and increasing CPU request is correct when a pod is throttled rather than terminated.
- ✗
Delete and recreate the pod to clear the crash loop
Why it's wrong here
Deleting and recreating the pod restarts it with the same memory limit, so the container will be OOMKilled again once it exceeds that limit. It is tempting because recreating pods clears many transient crash states, and it would be correct for a stuck pod with no resource-related termination reason.
- ✗
Delete the namespace and redeploy all workloads
Why it's wrong here
Deleting the namespace destroys every workload in production, causing a full outage, while leaving the memory limit unchanged so the OOMKilled condition recurs. It is tempting as a drastic reset when a namespace appears unhealthy, and it would be correct only for a dedicated, disposable environment with no other tenants.
Visual reference
Go deeper
Related to this question
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 →
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.