Master the IT-English vocabulary of Kubernetes pod troubleshooting: CrashLoopBackOff, ImagePullBackOff, OOMKilled, events and logs.
0 / 10 completed
1 / 10
A pod is stuck in 'CrashLoopBackOff'. What does that indicate?
CrashLoopBackOff means the container repeatedly crashes on start; Kubernetes waits longer between restarts.
2 / 10
A pod shows 'ImagePullBackOff'. What is the likely cause?
ImagePullBackOff means the image couldn't be pulled — often a bad tag, private registry, or auth issue.
3 / 10
A container was 'OOMKilled'. What happened?
OOMKilled means the container used more memory than allowed and was killed (out of memory).
4 / 10
To investigate, an engineer runs 'kubectl describe pod' to read the 'Events'. What do events show?
The Events section lists recent lifecycle messages (scheduled, pulled, failed) useful for diagnosis.
5 / 10
Which sentence correctly uses 'liveness probe'?
A liveness probe checks if a container is healthy; repeated failures trigger a restart.
6 / 10
During a code review of a new feature for the 'Phoenix' service, Sarah notices a comment from David: 'The pod is stuck in CrashLoopBackOff. It's restarting but failing to start.' What does this message primarily suggest about the pod's state? CrashLoopBackOff
CrashLoopBackOff indicates that the container within the pod is repeatedly crashing. This isn't simply a restart; it means the application inside the container is encountering an error that prevents it from initializing or running correctly. It's a strong signal to investigate the application logs for clues about the root cause.
7 / 10
Mark is troubleshooting a deployment of the 'Hydra' service. He receives a message in Slack from another developer: 'The pod keeps showing ImagePullBackOff. I've checked my registry credentials and they seem correct.' What is the most likely reason for this error? ImagePullBackOff
ImagePullBackOff almost always points to a problem with pulling the container image from its source. Even if credentials seem correct, there could be network connectivity issues between the Kubernetes cluster and the registry, or transient problems within the registry itself. It's crucial to verify network access and registry status.
8 / 10
During a standup meeting, Alex reports: 'We killed one of our 'Orion' pods with an OOMKilled event. It was consuming excessive memory.' What did the OOMKilled event signify? OOMKilled
OOMKilled (Out Of Memory Killed) is a Kubernetes signal that the container within the pod exhausted its allocated memory resources. This often happens when an application has a memory leak or consumes more memory than it's supposed to. It's a direct indication of a resource constraint issue.
9 / 10
You're investigating an unresponsive pod named 'Nova'. You run kubectl describe pod nova and examine the Events section. The events show: 'Failed to create endpoint'. What is the likely cause of this issue? Failed to create endpoint
'Failed to create endpoint' indicates a problem establishing communication between the Kubernetes service and the pods it manages. This usually means the application within the pod isn't configured to listen on the port specified in the service definition or there's an issue with DNS resolution preventing the service from finding its targets.
10 / 10
Which of the following statements accurately describes the purpose of a liveness probe in Kubernetes? liveness probe
A liveness probe periodically assesses whether a container is running and healthy. If the probe fails, Kubernetes automatically restarts the container, attempting to recover from the error. This ensures that unhealthy containers are replaced with new ones, maintaining application availability.
What will I practise in "Pod Troubleshooting Vocabulary"?
Master the IT-English vocabulary of Kubernetes pod troubleshooting: CrashLoopBackOff, ImagePullBackOff, OOMKilled, events and logs.
How many exercises are in this module?
This module has 10 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Kubernetes Operations exercises?
Browse the full Kubernetes Operations hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.