Question 320
A server operations team encounters the following situation: A SQL workload is moved to a storage tier with sufficient TB capacity but low random IOPS, causing slow transaction commits. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Storage provisioning ignores the workload's performance profile. It builds validation into the affected workflow and supports the expected recovery result: Peak commit latency and storage queue depth meet the application baseline.
Incorrect Answers
This control addresses a different scenario: An administrator rotates a Linux service log by renaming its file while the daemon continues writing to the old inode and disk space never frees. That event's root mechanism was the process retains an open file handle after a path-level rotation. The described incident instead arises from: Storage provisioning ignores the workload's performance profile.
This control addresses a different scenario: A file server stores archived reports for seven years, but a default quota deletes data once the shared disk reaches 85% use. That event's root mechanism was capacity controls and legal retention obligations were configured independently. The described incident instead arises from: Storage provisioning ignores the workload's performance profile.
This control addresses a different scenario: An enterprise's print server stores all spool files on the nearly full OS partition and printing stops during a seasonal billing run. That event's root mechanism was the spooler depends on temporary disk capacity that is exhausted. The described incident instead arises from: Storage provisioning ignores the workload's performance profile.