A nightly batch process generates accounting reports between two and four o'clock in the morning. The process runs for around forty minutes, completes its work, and is idle for the remainder of the twenty-four-hour cycle. The current deployment is a long-running server that remains powered through the day. The architecture team is reviewing whether the current setup remains the most efficient choice for this workload. The most appropriate option is likely to be:

Question

Accepted Answer

Run the process in a scheduled container that starts each night and stops after completion, since the work runs longer than serverless allows and avoids the day-long idle baseline of an always-on dedicated server.

Answer

Migrate to a serverless function, since the platform handles all idle periods automatically and the cold start cost is negligible for any process that runs longer than a few seconds in total per invocation.

Answer

Keep the current long-running server, since predictable scheduled work performs best on infrastructure that is always available and ready to begin processing without any startup delay during the operational window.

Answer

Continue with the current server but add a second server alongside it for redundancy, since redundant capacity for a nightly batch process improves overall reliability without affecting daytime energy use.

Crowdly

A nightly batch process generates accounting reports between two and four o'cloc...

Want instant access to all verified answers on moodle.polytechnic.bh?