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
Candidates often confuse resource requests and limits in Kubernetes. They may mistakenly increase the CPU request instead of the memory limit, or think that simply restarting the pod will resolve an OOMKilled error. However, the root cause is an exceeded memory limit, so the correct fix is to increase the memory limit in the container's resource specification.
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. Increasing the memory limit in the container's resource specification allows the container to use more memory before being killed, directly addressing the root cause.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Delete the namespace and redeploy all workloads
Why it's wrong here
This is a destructive action that would affect all workloads in the namespace. It is not appropriate for resolving a single pod's memory issue.
- ✓
Increase the memory limit in the pod's container resource specification
Why this is correct
OOMKilled indicates the container exceeded its configured memory limit. Increasing the memory limit allows the container to use more memory and prevents the OOM kill.
- ✗
Increase the CPU request for the container
Why it's wrong here
OOMKilled is a memory issue, not a CPU issue. Increasing CPU requests will not prevent the container from being killed due to memory exhaustion.
- ✗
Delete and recreate the pod to clear the crash loop
Why it's wrong here
Deleting and recreating the pod without changing the resource limits will result in the same OOMKilled event.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every KCNA question from scratch — 833 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.