CKA Troubleshooting Practice Question
You create a Deployment with the following YAML:
apiVersion: apps/v1 kind: Deployment metadata: name: myapp spec: replicas: 3 selector: matchLabels: app: myapp template: metadata: labels: app: myapp spec: containers: - name: myapp image: myapp:latest resources: limits: cpu: "500m" memory: "256Mi" requests: cpu: "200m" memory: "128Mi"
After applying it, the pods are in 'CrashLoopBackOff'. You check logs and see 'Error: container process exited with error'. What is the MOST likely cause?
⚠ Common exam trap
The CKA exam often tests the distinction between container startup failures (application errors) and runtime resource issues (OOMKill, CPU throttling). Candidates may mistakenly attribute a generic exit error to resource limits or probes.
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
✓
The application is crashing at startup due to a missing dependency
The error message 'container process exited with error' indicates the application itself is failing to start, not that it is being killed by Kubernetes. Since the container exits immediately after starting, the most likely cause is a missing dependency or misconfiguration in the application code, such as a missing environment variable, database connection, or file. Resource limits and probes affect running containers, not initial startup failures.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The application is crashing at startup due to a missing dependency
Why this is correct
When an application process exits immediately due to a missing dependency, runtime error, or misconfiguration, the container terminates with a non-zero exit code. Kubernetes detects this termination and automatically restarts the container, eventually entering a CrashLoopBackOff state as it backs off exponentially between restart attempts. This is the classic signature of an application-level startup failure.
- ✗
The container is being OOMKilled because memory limit is too low
Why it's wrong here
If a container exceeds its defined memory limit, the Linux kernel Out-Of-Memory (OOM) killer terminates the process with exit code 137. In this scenario, running kubectl describe pod would explicitly show the termination reason as OOMKilled rather than a generic application exit error. This distinct status helps administrators quickly differentiate resource exhaustion from application bugs.
- ✗
The readiness probe is failing
Why it's wrong here
A failing readiness probe indicates that the container is not ready to accept network traffic, which prompts Kubernetes to remove the pod's IP address from associated Service endpoints. It does not trigger a container restart or cause the pod to enter a CrashLoopBackOff state. Only a failing liveness probe or an actual process exit will trigger container restarts.
- ✗
The container has insufficient CPU resources
Why it's wrong here
When a container hits its CPU limit, Kubernetes does not terminate the process or restart the container. Instead, the completely standard behavior of the CFS (Completely Fair Scheduler) is to throttle the container's CPU usage, causing it to run slower. It will not result in a non-zero exit code or trigger a CrashLoopBackOff status.
Go deeper
Related to this question
Learn chapter
Installing Kubernetes with kubeadm
Key term
Ingress Resources
Ingress Resources are Kubernetes API objects that manage external access to services inside a cluster, typically HTTP and HTTPS traffic, by defining rules for routing requests based on hostnames and paths.
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
This CKA question is part of Courseiva's 726-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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 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.