Academy K8s Quiz
Questions covering the core concepts, tools, and real-world scenarios IT professionals encounter in Academy K8s.
This category currently has 60 questions in the SERVBG quiz bank. Below are a few sample questions — the full interactive quiz shuffles through the whole set with instant scoring.
Sample questions
A pod shows STATUS CrashLoopBackOff in `kubectl get pods`. What does this status actually mean?
- The node the pod is running on is unreachable
- The pod was never scheduled onto any node
- The container starts, then exits, and Kubernetes keeps restarting it with an increasing backoff delay
- The container image could not be downloaded from the registry
- The pod's Service has no matching endpoints
A pod shows STATUS ImagePullBackOff. What is the most direct explanation?
- The kubelet cannot pull the specified container image, e.g. due to a bad tag or missing registry credentials
- The container's liveness probe timed out
- The container started but crashed immediately with a non-zero exit code
- The node has insufficient CPU to run the container
- The container is running but failing its readiness probe
`kubectl logs` on a pod stuck in ImagePullBackOff returns an error instead of any log output. Why?
- The container was never actually started, so there is no log stream to read
- The image itself failed to write to stdout
- The logs exist but were rotated out before the command ran
- ImagePullBackOff pods only expose logs through `kubectl describe`
- Logs are disabled by default and must be enabled per pod
In `kubectl get pods` output, the RESTARTS column for one pod keeps climbing every time you re-run the command. What does that tell you on its own?
- The pod's image is being re-pulled on every restart
- The container inside that pod is repeatedly exiting and being restarted in place
- The Service in front of the pod is load-balancing incorrectly
- A new ReplicaSet revision is being rolled out
- The pod is being rescheduled to a different node each time
A user reports "my pod isn't working." What is the standard first command to run to start diagnosing it?
- kubectl top pod <name>, to check CPU and memory first
- kubectl delete pod <name>, since the ReplicaSet will recreate it correctly
- kubectl edit pod <name>, to directly patch the broken field
- kubectl rollout restart deployment/<name>, to force a fresh pod
- kubectl describe pod <name>, to read its Status, Events, and container state
Related categories
Python (Coding)
Python syntax, standard-library usage, and the language idioms that come up in day-to-day scripting and application work.
JavaScript (Coding)
Core JavaScript language behavior, async patterns, and the quirks that trip up both beginners and experienced developers.
Linux
Linux command-line usage, file permissions, process management, and the everyday admin tasks every sysadmin and developer needs.
Security
General information security concepts — threats, defenses, and the fundamentals every IT professional should know.
Hardware
Computer hardware components, how they interact, and the troubleshooting knowledge behind keeping systems running.