Question 280
An online marketplace wants encrypted forwarder traffic. Observed: Forwarders connect over TCP without TLS despite the contract requiring encrypted transport. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Packet inspection and connection logs confirm encrypted Splunk forwarding) to the original warning (Forwarders connect over TCP without TLS despite the contract requiring encrypted transport). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
The proposed check applies to: Forwarding durability depends on explicitly configured destination groups and failover behavior. The current failure was: Forwarders connect over TCP without TLS despite the contract requiring encrypted transport. Its validation must test: Packet inspection and connection logs confirm encrypted Splunk forwarding.
This is an unrelated recovery test. It is connected to: Container recreation changes ephemeral paths and causes forwarders to lose log continuity. The present source situation requires: Packet inspection and connection logs confirm encrypted Splunk forwarding.
That gate watches a different case: Local inputs.conf on one forwarder overrides the distributed app and sends events to the wrong index. It does not detect the current warning: Forwarders connect over TCP without TLS despite the contract requiring encrypted transport. The necessary confirmation is: Packet inspection and connection logs confirm encrypted Splunk forwarding.