Question 390
A travel booking app ingests compressed archived logs. Observed: Archived rotations are reprocessed every day because the same filenames are copied into a watched staging folder. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: Indexed event identifiers remain unique after repeated staging cycles. It provides case-specific verification that the observed behavior (Archived rotations are reprocessed every day because the same filenames are copied into a watched staging folder) has changed appropriately.
Incorrect Answers
This result checks another issue, for which the observed symptom is: Events arrive with the relay host as source identity instead of the original field device. It does not verify recovery for this situation: Archived rotations are reprocessed every day because the same filenames are copied into a watched staging folder. The relevant success check is: Indexed event identifiers remain unique after repeated staging cycles.
The proposed signal relates to: A rotated file is missed because the new filename does not match the configured monitor input path. The evidence for this Splunk source case must instead show: Indexed event identifiers remain unique after repeated staging cycles.
In the alternative case “Some API pages are missing because the collector treats each response as the final page”, the outcome “A fixture spanning multiple API pages ingests every expected event exactly once” is a useful test of “Implement page-token handling with durable checkpoints and rate-limit backoff”, because that case involves “Paginated API data collection must follow continuation cursors and retry safely”. The present case instead has the warning “Archived rotations are reprocessed every day because the same filenames are copied into a watched staging folder” and the failure mechanism “Replaying completed archives without unique ingestion controls duplicates indexed history”. Its remediation is “Use controlled one-time backfill and an exclusion strategy for already processed archives”; the matching acceptance observation is “Indexed event identifiers remain unique after repeated staging cycles”.