Question 270
A warehouse uses file monitoring to collect inventory reports. Observed: A rotated file is missed because the new filename does not match the configured monitor input path. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: Controlled file rotation delivers both old and new log segments without repeated ingestion. It provides case-specific verification that the observed behavior (A rotated file is missed because the new filename does not match the configured monitor input path) has changed appropriately.
Incorrect Answers
Option B would be useful evidence if the observed failure were “Directly streaming unreliable UDP syslog to an overloaded indexer causes missing messages”: it checks “A burst test preserves message sequence and reconciles packet counts at source and index” after the action “Deploy a supported syslog collector with persistent queueing before controlled forwarding” addresses “UDP collection lacks the durability and buffering needed for the critical evidence chain”. But the current failure is “A rotated file is missed because the new filename does not match the configured monitor input path”, linked to “File monitor input discovery follows the configured glob and whitelist/blacklist rules”. Here the targeted action is “Update the monitor path and file-selection patterns for the rotated naming scheme”, and the required proof is “Controlled file rotation delivers both old and new log segments without repeated ingestion”.
This result checks another issue, for which the observed symptom is: Archived rotations are reprocessed every day because the same filenames are copied into a watched staging folder. It does not verify recovery for this situation: A rotated file is missed because the new filename does not match the configured monitor input path. The relevant success check is: Controlled file rotation delivers both old and new log segments without repeated ingestion.
The proposed signal relates to: Events arrive with the relay host as source identity instead of the original field device. The evidence for this Splunk source case must instead show: Controlled file rotation delivers both old and new log segments without repeated ingestion.