A city finance team needs a report that runs once each night, finishes, and then stops. Which OKE workload object fits that pattern?
Select an answer to reveal the explanation.
Short Explanation
A Job is a sprint that ends when the work is done; a CronJob is the calendar that starts those sprints. A Deployment is for always-on services, so it is the wrong home for a once-a-night report.
Full Explanation
Kubernetes Jobs model run-to-completion work: the Pod runs, succeeds (or fails per policy), and stops. CronJob schedules Jobs on a timetable. Deployments keep Pods running continuously and are wrong for a nightly batch that should exit. StatefulSets and DaemonSets address stable identity and per-node agents, not scheduled batch reports. Choose CronJob → Job for finish-and-stop work.