Question 1020
A server operations team encounters the following situation: A storage pool's rebuild takes days on large slow HDDs, during which application latency spikes and background verification collides with production demand. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Rebuild I/O competes with application I/O on constrained drives. It builds validation into the affected workflow and supports the expected recovery result: The rebuilt array reaches healthy state within tested acceptable performance bounds.
Incorrect Answers
This control addresses a different scenario: A SAN volume disappears intermittently after a fiber patch replacement and port counters show increasing optical receive errors. That event's root mechanism was marginal fiber or optics disrupt block access despite valid array configuration. The described incident instead arises from: Rebuild I/O competes with application I/O on constrained drives.
This control addresses a different scenario: A boot server shows 'OS not found' after a controller repair, even though all disks and logical volumes are healthy in its management console. That event's root mechanism was firmware boot selection was altered independently of array health. The described incident instead arises from: Rebuild I/O competes with application I/O on constrained drives.
This control addresses a different scenario: An administrator expands a virtual disk but the guest still sees the old filesystem capacity, causing an application out-of-space error. That event's root mechanism was increasing virtual block capacity does not automatically resize in-guest structures. The described incident instead arises from: Rebuild I/O competes with application I/O on constrained drives.