Container Orchestra (2015) Quiz
Exam-prep questions for the Container Orchestra (2015) track of the Terminal Academy. Drive kubectl against a simulated three-node cluster: pods, deployments, services, namespaces, storage and failure triage.
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 image could not be downloaded from the registry
- The container starts, then exits, and Kubernetes keeps restarting it with an increasing backoff delay
- The pod's Service has no matching endpoints
A pod shows STATUS ImagePullBackOff. What is the most direct explanation?
- The container is running but failing its readiness probe
- The container's liveness probe timed out
- The node has insufficient CPU to run the container
- The kubelet cannot pull the specified container image, e.g. due to a bad tag or missing registry credentials
- The container started but crashed immediately with a non-zero exit code
`kubectl logs` on a pod stuck in ImagePullBackOff returns an error instead of any log output. Why?
- ImagePullBackOff pods only expose logs through `kubectl describe`
- The image itself failed to write to stdout
- The container was never actually started, so there is no log stream to read
- Logs are disabled by default and must be enabled per pod
- The logs exist but were rotated out before the command ran
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
- A new ReplicaSet revision is being rolled out
- The pod is being rescheduled to a different node each time
- 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 user reports "my pod isn't working." What is the standard first command to run to start diagnosing it?
- kubectl delete pod <name>, since the ReplicaSet will recreate it correctly
- kubectl top pod <name>, to check CPU and memory first
- kubectl edit pod <name>, to directly patch the broken field
- kubectl describe pod <name>, to read its Status, Events, and container state
- kubectl rollout restart deployment/<name>, to force a fresh pod
Continue the Container Orchestra (2015) track
Container Orchestra (2015) trains for the Terminal Academy’s Container Orchestra (2015) era.
Terminal Academy: Container Orchestra
Do the hands-on missions this quiz bank is drawn from.
Academy: Kubernetes Self-Assessment
Pair this quiz with the matching skills + personality assessment.
Related categories
Python (Coding)
Python syntax and standard-library usage, from quick scripts to full applications.
JavaScript (Coding)
Core JavaScript behavior and async patterns, including the quirks that trip up beginners and veterans alike.
Linux
Linux command-line usage, file permissions, process management. The daily admin tasks.
Security
General information security concepts: common threats and standard defenses.
Hardware
Hardware components, how they interact, and basic troubleshooting to keep systems running.