Question 180
A Splunk Enterprise administrator is investigating this situation: While evaluating a payment services team in an approved staging exercise, operations report: A team configures a one-time batch upload but expects Splunk to tail future additions forever. Which corrective action is the best next step?
Explanation
Correct Answer
Use a supported ongoing monitor input when continuous file updates are required. It is preferable to the other interventions because one-time upload and continuous file monitoring have different acquisition behavior. The operational acceptance evidence is two separate appended entries arrive without repeating the import job.
Incorrect Answers
The option would apply to “An application writes a rolling audit log directory but the forwarder has no monitor stanza for it”. Create a monitor input for the correct file or directory path in inputs.conf. This question instead requires “Use a supported ongoing monitor input when continuous file updates are required”.
Although relevant when A service adds nested subdirectories with new logs, and only the top-level file is monitored., it leaves the current failure mode unresolved. One-time upload and continuous file monitoring have different acquisition behavior. The appropriate check is Two separate appended entries arrive without repeating the import job.
That action is aimed at another operational symptom: A directory monitor should ignore stale historical files but the current deployment reads all backlogged data. The reported issue instead depends on this requirement: One-time upload and continuous file monitoring have different acquisition behavior. The expected validation is Two separate appended entries arrive without repeating the import job.