Kubernetes is designed to manage containerized applications at scale. Its core strength lies in orchestrating workloads using various controllers like Deployments, StatefulSets, DaemonSets, and Jobs. Scheduling determines how and where pods run in a cluster, using rules and constraints like node affinity, taints, and tolerations.
Understanding workloads and scheduling is critical for deploying reliable applications that scale and recover effectively. These MCQs will help you assess and strengthen your understanding of Kubernetes workloads and scheduling mechanisms.
1.) Which Kubernetes object ensures that a specified number of pod replicas are running at all times?
2.) What does a DaemonSet ensure?
3.) Which object manages a group of identical pods?
4.) What is the primary function of the Kubernetes scheduler?
5.) Which controller is ideal for batch jobs and one-time tasks?
6.) What is a StatefulSet primarily used for?
7.) What does a CronJob do in Kubernetes?
8.) What happens when a pod fails in a Job?
9.) Which controller should you use for ensuring high availability of a stateless app?
10.) Which field in a PodSpec influences scheduling decisions?