What should you consider to determine the best time to run a report?

• A. The weather
• B. The file format
• C. The size of the report, who will use it, and other system workloads
• D. The color theme of the UI

Answer: (C)

Timing a report is about balancing performance and usefulness. You should consider the size of the report, who will use it, and the other workloads the system is handling. A larger report consumes more CPU, memory, and I/O, so it will take longer to run and can compete with other processes. Knowing who needs the report and how quickly they need the data helps you pick a time that fits their workflow—some users require near real-time access, while others are fine with a scheduled batch. Finally, the current system workload matters: if many jobs run at once, resources get crowded, and performance can degrade or jobs can queue up. Scheduling large reports during off-peak times or staggering heavy jobs helps ensure faster, more reliable results without impacting other users. The weather, file format, or UI color theme don’t determine when a report should run, though those items might affect how you export or present the results after the run.