Question 340
An online banking application forwards audit logs to two data centers. Observed: Outputs use only one destination without a load-balancing or failover strategy. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (A receiver outage redirects new events without exceeding the allowed loss window) to the original warning (Outputs use only one destination without a load-balancing or failover strategy). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
That gate watches a different case: Events are visible but their environment field is absent because metadata extraction was expected at indexing without configuration. It does not detect the current warning: Outputs use only one destination without a load-balancing or failover strategy. The necessary confirmation is: A receiver outage redirects new events without exceeding the allowed loss window.
The proposed check applies to: Per-container ephemeral files are unsuitable as the only durable collection checkpoint. The current failure was: Outputs use only one destination without a load-balancing or failover strategy. Its validation must test: A receiver outage redirects new events without exceeding the allowed loss window.
This is an unrelated recovery test. It is connected to: Forwarders connect over TCP without TLS despite the contract requiring encrypted transport. The present source situation requires: A receiver outage redirects new events without exceeding the allowed loss window.