A 24×7 municipal payments microservice must keep a declared replica count and roll out image changes safely on OKE. Which Kubernetes object should the team kubectl apply as the everyday service controller?
Select an answer to reveal the explanation.
Short Explanation
For a long-running service, Deployment is the daily driver. It keeps the replica count, owns ReplicaSets, and rolls out Pod template changes. A lone Pod has no rollout brain for 24×7 care.
Full Explanation
A Deployment is the standard Kubernetes object for long-running microservices: it maintains desired replicas, manages ReplicaSets, and executes rolling updates when the Pod template (image, env, probes) changes. Naked Pods lack that controller behavior. ConfigMaps and Ingress objects do not create or roll application replicas by themselves.