Orchestration Concepts
5 exercises — Master the English vocabulary of container orchestration: scheduler resource requests and limits, QoS classes, node selection (taints, tolerations, affinity), self-healing probes, and autoscaling.
A Pod manifest sets: resources.requests.cpu: "250m" and resources.limits.cpu: "500m". A colleague asks what the difference is between a request and a limit.
Which explanation is correct?
The scheduler reads each Pod's
requests to find a node with enough spare capacity — it never places a Pod on a node that cannot satisfy the request. The limits field is enforced by the kubelet/container runtime at runtime: a container that tries to use more CPU than its limit is throttled, and one that tries to use more memory than its limit is OOM-killed.Setting
requests too low causes over-packing (nodes become noisy and contended); setting limits too low causes throttling or OOM kills under normal load. Setting requests equal to limits (a "Guaranteed" pattern) gives the most predictable performance.Key vocabulary:
• resource request — the minimum amount of CPU/memory the scheduler reserves for a container
• resource limit — the maximum amount a container is allowed to consume at runtime
• throttling — CPU usage capped at the limit rather than terminated
• scheduler — the control-plane component that decides which node runs each Pod
Frequently Asked Questions
What does the "Orchestration Concepts" exercise practise?
Practice Kubernetes orchestration vocabulary in English: scheduler requests and limits, QoS classes, taints and tolerations, liveness/readiness/startup probes, and Horizontal Pod Autoscaler. 5 advanced exercises.
How many questions are in this exercise?
This exercise has 5 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Advanced. If the vocabulary feels difficult, browse the Containers & Virtualization category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Orchestration Concepts" part of a larger series?
Yes — it's one exercise in the Containers & Virtualization category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Containers & Virtualization category page for related exercises, or browse the main Exercises hub for other IT English topics.