Question 780
A national bookstore rolls out monitoring rules. Observed: Administrators edit live files on each forwarder rather than maintaining one managed deployment app. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Effective configuration hashes match across the designated forwarder group) to the original warning (Administrators edit live files on each forwarder rather than maintaining one managed deployment app). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
That gate watches a different case: The architecture assumes deployment server can remotely install the initial forwarder binary on machines with no Splunk agent. It does not detect the current warning: Administrators edit live files on each forwarder rather than maintaining one managed deployment app. The necessary confirmation is: Effective configuration hashes match across the designated forwarder group.
The proposed check applies to: Deployment apps can expose embedded configuration to every selected recipient. The current failure was: Administrators edit live files on each forwarder rather than maintaining one managed deployment app. Its validation must test: Effective configuration hashes match across the designated forwarder group.
This is an unrelated recovery test. It is connected to: The app package includes a `local` directory from a test host and overrides production defaults unexpectedly. The present source situation requires: Effective configuration hashes match across the designated forwarder group.