Question 410
An e-commerce startup upgrades a heavy forwarder. Observed: The new version fails to parse known sourcetypes because app-level props.conf was not migrated. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: Post-upgrade fixtures match historical sourcetype and field extraction behavior. It provides case-specific verification that the observed behavior (The new version fails to parse known sourcetypes because app-level props.conf was not migrated) has changed appropriately.
Incorrect Answers
The proposed signal relates to: Forwarder inputs collect the wrong Windows Event Log channel and omit required security audit records. The evidence for this Splunk source case must instead show: Post-upgrade fixtures match historical sourcetype and field extraction behavior.
This result checks another issue, for which the observed symptom is: One client's HEC token defaults to an index not included in its role's write authorization. It does not verify recovery for this situation: The new version fails to parse known sourcetypes because app-level props.conf was not migrated. The relevant success check is: Post-upgrade fixtures match historical sourcetype and field extraction behavior.
In the alternative case “An upstream collector rewrites packet source addresses and loses essential device provenance”, the outcome “Indexed flow records retain the original sender and normalized collector identity” is a useful test of “Preserve original endpoint fields alongside normalized routing metadata”, because that case involves “Pre-ingest normalization can erase information required for investigative correlation”. The present case instead has the warning “The new version fails to parse known sourcetypes because app-level props.conf was not migrated” and the failure mechanism “Effective parsing settings are layered across deployment apps and local configurations”. Its remediation is “Inventory and transfer supported parsing configuration with precedence checks”; the matching acceptance observation is “Post-upgrade fixtures match historical sourcetype and field extraction behavior”.