A nightly GIS tile rebuild must run to completion and then exit. Which workload is appropriate?
Select an answer to reveal the explanation.
Short Explanation
Batch work is a to-do list item, not a 24/7 receptionist. A Job runs the rebuild, counts success, and stops—unlike a Deployment that would keep restarting the "finished" process forever.
Full Explanation
Jobs track successful completions for finite work. When the GIS rebuild finishes, the Job should complete rather than be restarted as a long-running Deployment replica. DaemonSets and Always-restart bare Pods fight the run-to-completion model.