Question 60
A public transport operator is documenting availability targets. Observed: The design promises no data gaps without specifying forwarder queues, replication state, and recovery tests. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (The acceptance report records recovery objectives and demonstrates them under a controlled outage) to the original warning (The design promises no data gaps without specifying forwarder queues, replication state, and recovery tests). 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: The architecture measures only average daily ingest and ignores short peak rates and forwarder buffering. The present source situation requires: The acceptance report records recovery objectives and demonstrates them under a controlled outage.
The proposed check applies to: A validated architecture selection depends on workload and availability constraints rather than one universal diagram. The current failure was: The design promises no data gaps without specifying forwarder queues, replication state, and recovery tests. Its validation must test: The acceptance report records recovery objectives and demonstrates them under a controlled outage.
That gate watches a different case: The design treats a single server with a backup disk as continuous search high availability. It does not detect the current warning: The design promises no data gaps without specifying forwarder queues, replication state, and recovery tests. The necessary confirmation is: The acceptance report records recovery objectives and demonstrates them under a controlled outage.