Question 740
The Splunk Enterprise administrator is asked to explain: At a healthcare monitoring network during a regulatory evidence review, reviewers observe the following: A rotated log reappears under new names and ingestion duplicates entire files on each rotation. Which statement captures the underlying mechanism?
Explanation
Correct Answer
Splunk's file tracking can mistake rotated copies for new sources when identity settings are unsuitable. The actionable correction is review file identity and crcSalt behavior before adjusting the monitor configuration. Evidence of correct operation is rotation tests collect each newly written line once without replaying earlier content.
Incorrect Answers
The related but distinct situation is “A directory monitor should ignore stale historical files but the current deployment reads all backlogged data”. File age and monitoring settings can bound historical input without changing event index retention. For the stated problem, “Splunk's file tracking can mistake rotated copies for new sources when identity settings are unsuitable” addresses the central condition.
This option serves the scenario “A monitored directory contains debug and production logs, but the ingest plan should read only production patterns”. Monitor filters prevent unintended files from entering the collection path. The present scenario is distinguished by “Splunk's file tracking can mistake rotated copies for new sources when identity settings are unsuitable”.
This alternative addresses the separate case “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”. The controlling mechanism is that one-time upload and continuous file monitoring have different acquisition behavior. The deciding requirement here is “Splunk's file tracking can mistake rotated copies for new sources when identity settings are unsuitable”.