A developer creates a naked Pod for a production API. Why should they prefer a Deployment instead?
Select an answer to reveal the explanation.
Short Explanation
A lone Pod is a house of cards—knock it over and nothing rebuilds it for you. A Deployment is the contractor on retainer: it replaces failed Pods and rolls out new versions on purpose.
Full Explanation
Controllers such as Deployments maintain desired replica counts and enable rolling updates and rollbacks. A bare Pod that dies is not replaced unless something else recreates it. Bare Pods can still use Services, ConfigMaps, and Secrets; they are not universally rejected by the API—they simply lack controller benefits for production apps.