Question 420
A financial services provider isolates HEC ingestion traffic. Observed: A network proxy times out long HEC requests and clients silently abandon batches. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Under a controlled proxy delay all events either arrive or are retried and reconciled) to the original warning (A network proxy times out long HEC requests and clients silently abandon batches). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
That gate watches a different case: Receiver throughput drops because event-processing queues are blocked by slow storage writes. It does not detect the current warning: A network proxy times out long HEC requests and clients silently abandon batches. The necessary confirmation is: Under a controlled proxy delay all events either arrive or are retried and reconciled.
The proposed check applies to: Universal forwarders perform limited processing compared with full Splunk Enterprise instances. The current failure was: A network proxy times out long HEC requests and clients silently abandon batches. Its validation must test: Under a controlled proxy delay all events either arrive or are retried and reconciled.
This is an unrelated recovery test. It is connected to: A broad event-filtering transform discards required error records along with verbose debug events. The present source situation requires: Under a controlled proxy delay all events either arrive or are retried and reconciled.