Question 1
The production review includes this finding: At a cloud migration program during a verification workshop, reviewers observe the following: A high-volume site needs failover across three indexers but outputs.conf specifies one fixed destination. What principle should guide the diagnosis?
Explanation
Correct Answer
The controlling mechanism is that redundant forwarding destinations can provide capacity sharing and recoverability when configured correctly. Resolve the problem by configure supported forwarder output groups and target balancing rather than a single hard-coded receiver. Then validate with: A planned target outage still allows ingestion through the remaining destinations.
Incorrect Answers
This option serves the scenario “A forwarding project needs intermediate routing for one sensitive sourcetype and a universal forwarder is assumed to perform arbitrary parsing”. The controlling mechanism is that lightweight and heavy forwarders differ in their processing capabilities and appropriate deployment roles. This question instead requires “Redundant forwarding destinations can provide capacity sharing and recoverability when configured correctly”.
This alternative addresses the separate case “A team configures acknowledgment behavior but does not test how a forwarder handles receiver backpressure”. Delivery assurance depends on both forwarder and receiving pipeline behavior, not one checkbox. For the stated problem, “Redundant forwarding destinations can provide capacity sharing and recoverability when configured correctly” addresses the central condition.
The option would apply to “A host forwards to an invalid DNS alias after a migration, and an admin edits parsing rules to compensate”. A bad route prevents delivery before parsing properties on the receiver matter. The present scenario is distinguished by “Redundant forwarding destinations can provide capacity sharing and recoverability when configured correctly”.