Question 540
A government agency tests index performance after a hardware upgrade. Observed: IO latency remains high despite adding CPU because bucket storage remains on a saturated device. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Sustained ingest shows reduced index latency with stable storage utilization) to the original warning (IO latency remains high despite adding CPU because bucket storage remains on a saturated device). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
This is an unrelated recovery test. It is connected to: A maintenance report treats the bucket's time-range values as the time of the last filesystem copy. The present source situation requires: Sustained ingest shows reduced index latency with stable storage utilization.
That gate watches a different case: One indexer uses locally customized paths that override the intended shared index settings. It does not detect the current warning: IO latency remains high despite adding CPU because bucket storage remains on a saturated device. The necessary confirmation is: Sustained ingest shows reduced index latency with stable storage utilization.
The proposed check applies to: A retention audit must trace the actual bucket retirement and archive/delete behavior. The current failure was: IO latency remains high despite adding CPU because bucket storage remains on a saturated device. Its validation must test: Sustained ingest shows reduced index latency with stable storage utilization.