Which statement best describes deployments in Kubernetes?

Which statement best describes deployments in Kubernetes?

• A. They are the recommended object for running applications in a cluster
• B. They are only used for stateful workloads
• C. They replace Pods directly
• D. They are deprecated

Answer: (A)

Deployments provide a declarative, day-to-day way to run applications in a Kubernetes cluster. You specify the desired state—how many replicas you want, the Pod template (containers, images, resources), and how updates should be done. Kubernetes then ensures the actual state matches that desired state by creating and maintaining the necessary ReplicaSets and Pods. When you roll out a change, the Deployment handles a controlled rollout, gradually replacing old Pods with new ones and offering rollback if something goes wrong. It also scales up or down by adjusting the replica count and keeps applications available through self-healing—replacing failed Pods automatically. This is why it’s the recommended object for running applications: it abstracts the low-level Pod management into a stable, scalable workflow. Stateful workloads are better served by StatefulSets, not Deployments, and Deployments don’t directly replace Pods you create by hand—they manage Pods via ReplicaSets. They aren’t deprecated; they remain the standard mechanism for deploying stateless workloads in Kubernetes.

Deployments provide a declarative, day-to-day way to run applications in a Kubernetes cluster. You specify the desired state—how many replicas you want, the Pod template (containers, images, resources), and how updates should be done. Kubernetes then ensures the actual state matches that desired state by creating and maintaining the necessary ReplicaSets and Pods. When you roll out a change, the Deployment handles a controlled rollout, gradually replacing old Pods with new ones and offering rollback if something goes wrong. It also scales up or down by adjusting the replica count and keeps applications available through self-healing—replacing failed Pods automatically.

This is why it’s the recommended object for running applications: it abstracts the low-level Pod management into a stable, scalable workflow. Stateful workloads are better served by StatefulSets, not Deployments, and Deployments don’t directly replace Pods you create by hand—they manage Pods via ReplicaSets. They aren’t deprecated; they remain the standard mechanism for deploying stateless workloads in Kubernetes.