Question 320
A television broadcaster adds a heavy forwarder tier. Observed: Heavy forwarder parsing workload causes high CPU and increasing upstream latency because it was undersized. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Load tests show stable queues and event latency at the documented peak rate) to the original warning (Heavy forwarder parsing workload causes high CPU and increasing upstream latency because it was undersized). 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: Indexer input sockets show no connections because the configured receiver port differs from the forwarder destination. The present source situation requires: Load tests show stable queues and event latency at the documented peak rate.
That gate watches a different case: A transform attempts to remove secret tokens on a universal forwarder that cannot execute the required parsing transform. It does not detect the current warning: Heavy forwarder parsing workload causes high CPU and increasing upstream latency because it was undersized. The necessary confirmation is: Load tests show stable queues and event latency at the documented peak rate.
The proposed check applies to: Polling collection needs a stable watermark or idempotent deduplication mechanism. The current failure was: Heavy forwarder parsing workload causes high CPU and increasing upstream latency because it was undersized. Its validation must test: Load tests show stable queues and event latency at the documented peak rate.