Question 510
A Splunk platform team observes this behavior: At a national retailer during an access-control audit, reviewers observe the following: An engineer edits a configuration under the shipped default directory and later loses it during an upgrade. Which technical principle best explains the issue?
Explanation
Correct Answer
Vendor default files are upgrade-managed, while local overrides are the intended customization layer. This explains why the administrator should place supported custom settings in an appropriate local configuration directory rather than changing packaged defaults. A direct test would be: After an upgrade rehearsal the custom setting persists and the shipped default stays intact.
Incorrect Answers
This alternative addresses the separate case “A forwarder has configuration in its app tree and its system tree, and an operator assumes only one inputs.conf can exist”. Multiple same-named .conf files are merged into an effective configuration rather than universally replacing one another. The deciding requirement here is “Vendor default files are upgrade-managed, while local overrides are the intended customization layer”.
The option would apply to “An app administrator cannot tell where to find a custom inputs.conf after installing an add-on”. Splunk organizes app-level configuration separately from system-wide overrides and packaged defaults. This question instead requires “Vendor default files are upgrade-managed, while local overrides are the intended customization layer”.
The related but distinct situation is “An operator wants to disable one stanza but duplicates the entire vendor-supplied default file into local”. Layering lets local settings override selected keys without freezing every other vendor default. For the stated problem, “Vendor default files are upgrade-managed, while local overrides are the intended customization layer” addresses the central condition.