Question 630
Which operational action best resolves the following storage situation? A datastore rejects writes when backing blocks are exhausted.
Explanation
Correct Answer
The most focused response is: Inspect physical utilization overcommit and capacity alerts. The implicated technical boundary is that thin provisioned logical size can exceed physical capacity. An integrator can verify the change through the following outcome: Data writes resume with monitored free-space headroom.
Incorrect Answers
The proposed action is relevant when an integrator checks media before host WWPN and masking. Its governing principle is that healthy volumes remain inaccessible with missing access mappings. Here the better diagnosis follows thin provisioned logical size can exceed physical capacity.
This choice concerns Root-cause analysis of storage failures, for example: An incompatible spare is fitted and the array remains unprotected. The current storage issue instead hinges on thin provisioned logical size can exceed physical capacity. The appropriate evidence is data writes resume with monitored free-space headroom.
Although this option is reasonable for 'Hosts report slow I/O while array media response is fast.', it is not the specific dependency in the stem. Its action is correlate SAN link errors with host I/O latency. The stem is resolved more directly by inspect physical utilization overcommit and capacity alerts.