Which action could help troubleshoot report failures by reducing load?

Which action could help troubleshoot report failures by reducing load?

• A. Run during peak hours
• B. Consider adjusting the time of day when your report is scheduled to run and select non-peak hours when possible
• C. Do not schedule at all
• D. Export data to CSV

Answer: (B)

Focusing on when the system is least busy helps you isolate problems. Scheduling a report to run during non-peak hours reduces resource contention—less CPU, memory, and I/O pressure—so you can observe how the report behaves in a calmer environment. This makes it easier to tell whether failures come from the report itself or from heavy load on the system. Running during peak hours introduces the very load that can cause timeouts or incomplete results, making diagnosis harder. Not scheduling anything means you won’t get data to analyze, which defeats the purpose. Exporting data to CSV isn’t about reducing system load during execution and can even add more work or load, so it doesn’t help with troubleshooting.

Focusing on when the system is least busy helps you isolate problems. Scheduling a report to run during non-peak hours reduces resource contention—less CPU, memory, and I/O pressure—so you can observe how the report behaves in a calmer environment. This makes it easier to tell whether failures come from the report itself or from heavy load on the system. Running during peak hours introduces the very load that can cause timeouts or incomplete results, making diagnosis harder. Not scheduling anything means you won’t get data to analyze, which defeats the purpose. Exporting data to CSV isn’t about reducing system load during execution and can even add more work or load, so it doesn’t help with troubleshooting.