CV0-003 · Question #10
A company uses its own private cloud, which has few available resources. Mission-critical systems and other information systems are running on it. A new system will be deployed on the private cloud…
The correct answer is C. 18:00-20:00. To minimize impact on the existing system, the load test must be scheduled during a window with low utilization that does not conflict with other planned tests or nightly batch operations.
Question
A company uses its own private cloud, which has few available resources. Mission-critical systems and other information systems are running on it. A new system will be deployed on the private cloud. The following tests are included in the test plan:
Load test (2h) Backup/restore test (6h) Functional test (8h) Failover test (1h) The work schedule of the existing system is shown below. To minimize the effect to the existing system, which of the following schedules is MOST suitable for the load test?
Options
- A02:00-04:00
- B09:00-12:00
- C18:00-20:00
- D22:00-00:00
How the community answered
(27 responses)- A7% (2)
- B4% (1)
- C85% (23)
- D4% (1)
Why each option
To minimize impact on the existing system, the load test must be scheduled during a window with low utilization that does not conflict with other planned tests or nightly batch operations.
02:00-04:00 likely overlaps with scheduled overnight batch jobs or backup/restore operations that would compete directly for the limited private cloud resources.
09:00-12:00 falls within peak business hours when mission-critical systems are under maximum load, meaning a resource-intensive load test would directly contend for the scarce available resources.
The 18:00-20:00 window falls immediately after business hours when workload on mission-critical systems decreases, providing a quiet two-hour slot for the load test. This window avoids both peak daytime usage and the late-night period when backup/restore jobs and other scheduled maintenance tasks typically run, making it the least disruptive option available.
22:00-00:00 is typically occupied by nightly maintenance or scheduled backups, and other tests in the plan may already be assigned to this window.
Concept tested: Test scheduling to minimize production system impact
Topics
Community Discussion
No community discussion yet for this question.