Question 590
Which verification result most directly demonstrates recovery for this case? A busy database has tail latency problems hidden by average IOPS.
Explanation
Correct Answer
The evidence matches the reported storage problem: The workload meets its percentile latency objectives. It confirms the remediation: Size using peak IOPS bandwidth queue depth and latency percentiles. Underlying rule: Average utilization cannot predict worst-case application response.
Incorrect Answers
That alternative could help with the separate condition: A distant SAN is specified for millisecond database writes without WAN analysis. It would be checked by actual service timing meets the approved budget. For the described case, the necessary correction is size using peak IOPS bandwidth queue depth and latency percentiles.
This choice concerns Planning storage for typical workloads, for example: A shared document application is assigned uncoordinated raw block storage. The current storage issue instead hinges on average utilization cannot predict worst-case application response. The appropriate evidence is the workload meets its percentile latency objectives.
The choice tests a neighboring capability: Sharing storage resources can produce cross-workload contention. The proposed correction would apply to 'Mixed workloads have no service-level separation under peak load.' but this incident needs size using peak IOPS bandwidth queue depth and latency percentiles. and a successful test that the workload meets its percentile latency objectives.