Splunk configuration file precedence practice
Free Splunk practice for the Enterprise Admin exam: pick the copy of a .conf file whose value Splunk uses, in the global or the app/user context, or the props.conf stanza that wins for an event. Check my answer names the slip, such as default over local.
Paths start at $SPLUNK_HOME. App names, users and values are made up for practice. The drill leaves out indexer cluster peers, which have their own order.
Splunk exam prep
The Splunk Enterprise Certified Admin blueprint lists configuration layering and configuration precedence under Splunk Configuration Files, and the Architect blueprint lists tuning props.conf. Start with the free real exam questions, then get the full pack.
Precedence FAQ
What is the configuration file precedence order in Splunk?
In the global context, such as indexing and inputs, the order from highest to lowest is system/local, then the local directories of the apps, then the default directories of the apps, then system/default. Every app local directory comes before every app default directory.
How is the app/user context order different?
For search time files the order is the current user's directory, then the app being run (local, then default), then the other apps (local, then default) for exported settings only, then system/local and system/default. So an app default directory beats system/local here.
Does the copy with the highest priority replace the whole file?
No. Splunk merges the settings from all copies of the file. When copies set the same attribute to different values, it uses the value from the copy with the highest priority, and attributes that only a lower copy sets still apply.
How do app directory names change the order?
In the global context apps go in lexicographic order: A beats B, uppercase beats lowercase, and numbers beat letters and compare one digit at a time, so myapp10 beats myapp2. In the app/user context the other apps go in reverse lexicographic order, and the app being run beats all of them whatever its name.
Do settings from another app apply when I search in my app?
Only if that app exports them. In the app/user context Splunk only looks at configuration data for other apps when the data has been exported globally through the app's default.meta file.
Which config files are global and which are app/user?
inputs.conf, outputs.conf, indexes.conf, server.conf and web.conf are among the global files. savedsearches.conf, macros.conf, eventtypes.conf and tags.conf are app/user files. props.conf and transforms.conf can be either, depending on whether Splunk uses them at index time or at search time.
Which props.conf stanza wins: source, host or sourcetype?
For the same setting, a [host::<host>] stanza overrides a [<sourcetype>] stanza, and a [source::<source>] stanza overrides both. The priority key does not change this order across stanza types.
What does priority do in props.conf?
It settles which matching stanza of the same type wins. By default a literal stanza has priority 100 and a pattern 0, so the literal wins, and a pattern with priority above 100 overrides the literal. When two patterns tie, Splunk uses the ASCII order of the patterns.
Is the order different on indexer cluster peers?
Yes. Peer nodes have an expanded order with the peer-app local directories at the top, followed by system/local, app local, peer-app default, app default and system/default. This drill does not cover it.
Sources
- Splunk Enterprise 10.0 Admin Manual, Configuration file precedence: the global and app/user orders, the cluster peer order, lexicographic and reverse lexicographic app names, exported settings, the merge of settings from all copies and the t2rss example.
- Splunk Enterprise 10.0 props.conf spec: [<spec>] stanza precedence, the default priority of literal and pattern stanzas, ASCII order for colliding patterns, the match language for * and ..., [default] settings and KV_MODE at search time.
- Setting names in the problems come from the 10.0 spec files for inputs.conf, outputs.conf, indexes.conf, web.conf, savedsearches.conf and macros.conf.
- Splunk exam blueprints: Enterprise Certified Admin (3.3 Understand configuration precedence) and Enterprise Certified Architect (7.3 Tune props.conf).
- Checked 21 November 2026. The tool's own approach: every problem has four cards, and names and values are made up. It only uses app names whose order the page settles (no name pairs that first differ at a symbol), shows only the current user's directory for the app being run, and states plainly which other apps export. It never asks about two stanzas the spec leaves tied. An independent re-solver, written from the quoted rules, agreed with the drill on 20,000 generated problems.
Checked 21 November 2026 against the Splunk Enterprise 10.0 Admin Manual, the props.conf spec and the Splunk exam blueprints.
- DrillSplunk storage sizing practiceWork out indexer cluster storage from GB per day, retention, replication and search factor, per peer and without a cluster.
- DrillSplunk SPL practiceSay what a search returns from a small event table: NOT and !=, wildcards, where, eval, stats, top, dedup and sort.
- DrillSalesforce record access practiceTap the access a user gets from OWD, roles, sharing rules, teams and View All.