Question 310
A city police department records firewall alerts through syslog. Observed: The log collector truncates long messages before the forwarder reads them. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: Deliberately long test events remain intact end-to-end. It provides case-specific verification that the observed behavior (The log collector truncates long messages before the forwarder reads them) has changed appropriately.
Incorrect Answers
This result checks another issue, for which the observed symptom is: A receiver accepts some senders but rejects agents with untrusted client certificates. It does not verify recovery for this situation: The log collector truncates long messages before the forwarder reads them. The relevant success check is: Deliberately long test events remain intact end-to-end.
The distractor measures “Restart testing shows each source line indexed once and new lines continue”. This verifies a separate correction, “Preserve checkpoint state where supported and adopt a container-safe collection pattern”, for the fault “Forwarders repeatedly re-index old lines because file checkpoints are lost on every container restart” and the cause “File-monitor continuity relies on persisted fishbucket/checkpoint state or appropriate durable log pipelines”. The stated fault, however, is “The log collector truncates long messages before the forwarder reads them”, which points to “Upstream syslog collector settings can damage records prior to Splunk ingestion”. Check “Deliberately long test events remain intact end-to-end” after “Increase the collector's supported message size and validate retention of full records” to determine whether this incident was resolved.
The proposed signal relates to: A collection script sometimes runs longer than its interval, creating overlapping executions and duplicate records. The evidence for this Splunk source case must instead show: Deliberately long test events remain intact end-to-end.