Question 400
A telecommunications provider streams records from container workloads. Observed: Container recreation changes ephemeral paths and causes forwarders to lose log continuity. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Container churn leaves no unexplained event gaps or replay duplicates) to the original warning (Container recreation changes ephemeral paths and causes forwarders to lose log continuity). 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: Outputs use only one destination without a load-balancing or failover strategy. The present source situation requires: Container churn leaves no unexplained event gaps or replay duplicates.
That gate watches a different case: An input omits an explicit index setting and uses the installation default instead. It does not detect the current warning: Container recreation changes ephemeral paths and causes forwarders to lose log continuity. The necessary confirmation is: Container churn leaves no unexplained event gaps or replay duplicates.
The proposed check applies to: Splunk-to-Splunk encryption depends on matching sender/receiver SSL configuration and trusted certificates. The current failure was: Container recreation changes ephemeral paths and causes forwarders to lose log continuity. Its validation must test: Container churn leaves no unexplained event gaps or replay duplicates.