A cloud administrator has implemented a cost-savings policy to reduce the number of servers running at a given time. This policy will shut down all servers at 3:30 a.m. and restart them at 8:30 a.m. e

Adding more resources to reduce batch job duration might help if the jobs are taking too long when the servers are running, but the core issue here is that the servers are shut down during the critical processing window.

Changing the shutdown policy to begin at 4:00 a.m. (or later) would ensure that the servers are running for a longer period after the 8:30 a.m. restart, providing more time for the financial_summary batch job to complete before the 9:00 a.m. meeting. This preserves the cost-savings while addressing the report availability issue.

Rescheduling the financial_summary batch job to run at 9:00 a.m. would not resolve the issue, as the servers would have only been running for 30 minutes at that point, which might still be insufficient or too late for the 9:00 a.m. meeting.

Disabling the policy entirely would solve the report issue but would negate the cost-savings objective, which is explicitly stated as the purpose of the policy.