Certified Kubernetes Application Developer (CKAD) Practice Test

A DaemonSet in Kubernetes is designed to ensure that a specific pod runs on all (or a selected subset of) nodes within a cluster. This functionality is typically used for deploying background services that need to be present on every node, such as log collectors or monitoring agents. The DaemonSet controller automatically adds a pod to a node when the node is added to the cluster, ensuring consistency and availability of the designated service across the environment.

This is particularly valuable for tasks that require specific configurations or functionalities to be available on every node, allowing seamless interaction within the cluster. For instance, if you have a monitoring tool that needs to scrape metrics from each node, a DaemonSet would be the ideal resource to deploy this tool on every node.

The other options describe functionalities that are not aligned with what a DaemonSet specifically accomplishes. For example, ensuring that all replicas are running pertains to ReplicaSets, while managing resources for a set of pods is characteristic of controllers like Deployments. Monitoring the health of the cluster is typically the role of health-check tools and not directly managed through a DaemonSet.