A city permitting office runs permit-review workers as containers across a pool of hosts. When a reviewer container must start, which orchestration responsibility decides which worker has enough CPU and memory and binds the container there?
Select an answer to reveal the explanation.
Short Explanation
Think of the scheduler as a dispatcher who knows which desk has free space. It matches CPU, memory, and constraints to a worker and seats the container there. You do not keep picking the same hostname out of habit.
Full Explanation
Container orchestration’s scheduler evaluates available capacity and any placement constraints, then binds a container (or Pod) to a suitable worker. Manual host selection and SSH-driven starts defeat that model. Vault and API Gateway address secrets and HTTP front doors, not worker placement.