Question 80
A food distributor expects to monitor index throughput spikes. Observed: A daily aggregate dashboard masks hourly ingestion stalls during batch uploads. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (A simulated ingest peak is visible with corresponding throughput and queue metrics) to the original warning (A daily aggregate dashboard masks hourly ingestion stalls during batch uploads). 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: Operators attribute receiver-port closures to firewall policy despite corresponding blocked internal queues. The present source situation requires: A simulated ingest peak is visible with corresponding throughput and queue metrics.
The proposed check applies to: KV store component health requires the relevant search-tier monitoring views. The current failure was: A daily aggregate dashboard masks hourly ingestion stalls during batch uploads. Its validation must test: A simulated ingest peak is visible with corresponding throughput and queue metrics.
That gate watches a different case: The health-check alert thresholds are copied from a significantly larger Splunk deployment. It does not detect the current warning: A daily aggregate dashboard masks hourly ingestion stalls during batch uploads. The necessary confirmation is: A simulated ingest peak is visible with corresponding throughput and queue metrics.