Splunk SPLK-1003 Practice Questions with Explanations
Free Splunk SPLK-1003 practice questions. 50 of them, each with the correct answer, a full explanation, and the reason every other option is wrong. These are real questions from the SPLK-1003 exam, not paraphrases, and every explanation is written out rather than just marking the right letter.
They are drawn from the same bank as the full SPLK-1003 pack, which has 209 questions in total.
Get the full SPLK-1003 question bank (209 questions) →
SPLK-1003 practice questions
Question 1
Which setting in indexes.conf allows data retention to be controlled by time?
- A. maxDaysToKeep
- B. moveToFrozenAfter
- C. maxDataRetentionTime
- D. frozenTimePeriodInSecs
Show answer and explanation ▾
Correct answer: D
The frozenTimePeriodInSecs setting in indexes.conf controls data retention by specifying the time period (in seconds) after which buckets are moved to the frozen directory. This is the primary time-based retention control mechanism in Splunk.
Why the other options are wrong:
- A. maxDaysToKeep is not a valid indexes.conf setting for retention control.
- B. moveToFrozenAfter defines when buckets transition to frozen but uses a different naming convention than the actual setting.
- C. maxDataRetentionTime is not the correct setting name used in indexes.conf.
Question 2
In case of a conflict between a whitelist and a blacklist input setting, which one is used?
- A. Blacklist
- B. Whitelist
- C. They cancel each other out.
- D. Whichever is entered into the configuration first.
Show answer and explanation ▾
Correct answer: A
When there is a conflict between whitelist and blacklist settings, the blacklist takes precedence. This means items on the blacklist will be excluded even if they appear on a whitelist, implementing a deny-first security model.
Why the other options are wrong:
- B. The whitelist does not override the blacklist; the opposite is true.
- C. They do not cancel each other out; one has priority over the other.
- D. The order of entry in the configuration file does not determine which takes precedence; blacklist always wins.
Question 3
In which Splunk configuration is the SEDCMD used?
- A. props.conf
- B. inputs.conf
- C. indexes.conf
- D. transforms.conf
Show answer and explanation ▾
Correct answer: A
SEDCMD (Sed Command) is used in props.conf to perform field-level transformations and data substitutions on events during parsing. This is where sed-like regular expression substitutions are configured.
Why the other options are wrong:
- B. inputs.conf is for defining data inputs, not for field transformations.
- C. indexes.conf is for index-level settings and retention policies, not field transformations.
- D. transforms.conf is for defining field transformations but SEDCMD specifically belongs in props.conf.
Question 4
Which parent directory contains the configuration files in Splunk?
- A. $SPLUNK_HOME/etc
- B. $SPLUNK_HOME/var
- C. $SPLUNK_HOME/conf
- D. $SPLUNK_HOME/default
Show answer and explanation ▾
Correct answer: A
The $SPLUNK_HOME/etc directory is the parent directory that contains all configuration files in Splunk. Subdirectories within etc include apps, system, users, and deployment- client, which hold all configuration files.
Why the other options are wrong:
- B. $SPLUNK_HOME/var contains variable data like logs and metadata, not configuration files.
- C. $SPLUNK_HOME/conf is not a standard Splunk directory structure.
- D. $SPLUNK_HOME/default is not a top-level directory; default configurations exist within subdirectories of etc.
Question 5
Which forwarder type can parse data prior to forwarding?
- A. Universal forwarder
- B. Heaviest forwarder
- C. Hyper forwarder
- D. Heavy forwarder
Show answer and explanation ▾
Correct answer: D
The heavy forwarder is the only forwarder type capable of parsing data prior to forwarding. It includes the full Splunk processing pipeline and can perform field transformations, filtering, and other advanced operations before sending data to indexers.
Why the other options are wrong:
- A. The universal forwarder only collects and forwards raw data; it cannot parse.
- B. Heaviest forwarder is not a real Splunk forwarder type.
- C. Hyper forwarder is not a real Splunk forwarder type.
Question 6
Which Splunk component consolidates the individual results and prepares reports in a distributed environment?
- A. Indexers
- B. Forwarder
- C. Search head
- D. Search peers
Show answer and explanation ▾
Correct answer: C
The search head consolidates individual results from multiple search peers and prepares reports in a distributed search environment. It coordinates the distributed search across indexers and manages the final aggregation and presentation of results.
Why the other options are wrong:
- A. Indexers store and index data; they do not consolidate results or prepare reports.
- B. Forwarders send data to indexers; they do not consolidate results.
- D. Search peers are the indexers being searched, not the component that consolidates results.
Question 7
Which Splunk component distributes apps and certain other configuration updates to search head cluster members?
- A. Deployer
- B. Cluster master
- C. Deployment server
- D. Search head cluster master
Show answer and explanation ▾
Correct answer: A
The Deployer is the specific Splunk component responsible for distributing apps and configuration updates to search head cluster members. It manages the distribution of the cluster bundle containing apps and configurations that need to be consistent across all search head cluster members.
Why the other options are wrong:
- B. Cluster master manages indexer clustering, not search head cluster app distribution.
- C. Deployment server distributes configurations to deployment clients (forwarders, indexers), not search head cluster members.
- D. Search head cluster master is not a standard Splunk component; the correct term is Deployer.
Question 8
Where should apps be located on the deployment server that the clients pull from?
- A. $SPLUNK_HOME/etc/apps
- B. $SPLUNK_HOME/etc/search
- C. $SPLUNK_HOME/etc/master-apps
- D. $SPLUNK_HOME/etc/deployment-apps
Show answer and explanation ▾
Correct answer: D
Apps on the deployment server must be placed in $SPLUNK_HOME/etc/deployment-apps directory. This is the designated location where the deployment server expects to find apps that will be pushed to deployment clients. The deployment-apps directory distinguishes server-side app staging from regular local apps.
Why the other options are wrong:
- A. $SPLUNK_HOME/etc/apps is the default location for apps on individual Splunk instances, not the deployment server staging area.
- B. $SPLUNK_HOME/etc/search is not a standard Splunk directory for app storage.
- C. $SPLUNK_HOME/etc/master-apps is used for cluster master app distributions, not deployment server apps.
Question 9
This file has been manually created on a universal forwarder: /opt/splunkforwarder/etc/apps/my_TA/local/inputs.conf [monitor:///var/log/messages] sourcetype=syslog index=syslog A new Splunk admin comes in and connects the universal forwarders to a deployment server and deploys the same app with a new inputs.conf file: /opt/splunk/etc/deployment-apps/my_TA/local/inputs.conf [monitor:///var/log/maillog] sourcetype=maillog index=syslog Which file is now monitored?
- A. /var/log/messages
- B. /var/log/maillog
- C. /var/log/maillog and /var/log/messages
- D. none of the above
Show answer and explanation ▾
Correct answer: B
When a deployment server pushes an app to a deployment client, configurations from the deployment server take precedence over manually created local files on the client. The deployment server's configuration in /opt/splunkforwarder/etc/deployment-apps/my_TA/local/inputs.conf will override the previously manually created /opt/splunkforwarder/etc/apps/my_TA/local/inputs.conf, so /var/log/maillog will be monitored.
Why the other options are wrong:
- A. The manual file is overridden by the deployment server configuration.
- C. Only the deployment server configuration is active; both files are not merged in this scenario.
- D. The deployment server configuration is applied and active.
Question 10
In which phase of the index time process does the license metering occur?
- A. Input phase
- B. Parsing phase
- C. Indexing phase
- D. Licensing phase
Show answer and explanation ▾
Correct answer: C
License metering occurs during the indexing phase of the index-time processing pipeline. At this stage, Splunk measures and tracks the volume of data being indexed to enforce licensing limits. The data has been parsed and is being written to the index when metering takes place.
Why the other options are wrong:
- A. The input phase is when data is initially received but before licensing calculations.
- B. The parsing phase processes the data format but metering happens later.
- D. Licensing phase is not a standard phase in Splunk's index-time processing pipeline.
Question 11
You update a props.conf file while Splunk is running. You do not restart Splunk and you run this command: splunk btool props list `"-debug. What will the output be?
- A. A list of all the configurations on-disk that Splunk contains.
- B. A verbose list of all configurations as they were when splunkd started.
- C. A list of props.conf configurations as they are on-disk along with a file path from which the configuration is located.
- D. A list of the current running props.conf configurations along with a file path from which the configuration was made.
Show answer and explanation ▾
Correct answer: C
The btool command with -debug flag reads configuration files from disk as they currently exist and displays them with their source file paths. Since Splunk was not restarted, btool shows the on-disk configurations in their current state, not what is running in memory. The -debug flag provides file path information for each configuration entry.
Why the other options are wrong:
- A. Btool is more specific than just listing all configurations on disk.
- B. Btool reads current disk state, not the in-memory state from startup.
- D. Without a restart, btool shows disk state, not the running configuration in memory.
Question 12
The priority of layered Splunk configuration files depends on the file's:
- A. Owner
- B. Weight
- C. Context
- D. Creation time
Show answer and explanation ▾
Correct answer: C
The priority of layered Splunk configuration files depends on the file's context, which refers to the directory structure and hierarchy (default, local, app-specific, etc.). Context determines precedence: local overrides default, app contexts override system contexts, and this hierarchy is what determines which configuration value takes effect.
Why the other options are wrong:
- A. File owner does not determine configuration priority in Splunk.
- B. Weight is not a factor in Splunk configuration precedence.
- D. Creation time does not determine configuration file priority in Splunk.
Question 13
When configuring monitor inputs with whitelists or blacklists, what is the supported method of filtering the lists?
- A. Slash notation
- B. Regular expression
- C. Irregular expression
- D. Wildcard-only expression
Show answer and explanation ▾
Correct answer: B
When configuring monitor inputs with whitelists or blacklists in Splunk, the supported method of filtering is regular expressions. Regular expressions provide powerful pattern matching to include or exclude specific files or directories from being monitored.
Why the other options are wrong:
- A. Slash notation is not the supported filtering method for monitor input lists.
- C. Irregular expression is not a valid or supported filtering method.
- D. Wildcard-only expressions are not sufficient; Splunk supports the more powerful regex syntax.
Question 14
What are the minimum required settings when creating a network input in Splunk?
- A. Protocol, port number
- B. Protocol, port, location
- C. Protocol, username, port
- D. Protocol, IP, port number
Show answer and explanation ▾
Correct answer: A
When creating a network input in Splunk, the minimum required settings are Protocol (such as TCP or UDP) and Port Number. These two settings define how Splunk will listen for incoming network data. Location, username, and IP address are either not applicable or optional depending on the input type.
Why the other options are wrong:
- B. Location is not a standard required setting for network inputs.
- C. Username and password are not required for network inputs; authentication applies to other input types.
- D. IP address is not required; network inputs listen on all interfaces by default or can be configured without specifying a specific IP.
Question 15
Which Splunk component requires a Forwarder license?
- A. Search head
- B. Heavy forwarder
- C. Heaviest forwarder
- D. Universal forwarder
Show answer and explanation ▾
Correct answer: B
The Heavy forwarder requires a Forwarder license because it performs parsing, transformation, and filtering operations on data before forwarding. The Universal forwarder is license-free (though it requires a Splunk Enterprise license in the deployment), the Search head requires a different license type, and 'Heaviest forwarder' is not a valid Splunk component. The Heavy forwarder's advanced capabilities necessitate dedicated licensing.
Why the other options are wrong:
- A. Search heads require a Search head license, not a Forwarder license.
- C. Heaviest forwarder is not an actual Splunk component type.
- D. Universal forwarder is license-free and does not require a separate Forwarder license.
Question 16
Which optional configuration setting in inputs.conf allows you to selectively forward the data to specific indexer(s)?
- A. _TCP_ROUTING
- B. _INDEXER_LIST
- C. _INDEXER_GROUP
- D. _INDEXER_ROUTING
Show answer and explanation ▾
Correct answer: A
The tcpout routing setting (referenced as _TCP_ROUTING in inputs.conf context) allows selective forwarding of data to specific indexers. This configuration enables load balancing and selective routing based on data characteristics, allowing administrators to direct different data streams to different indexer groups or individual indexers.
Why the other options are wrong:
- B. _INDEXER_LIST is not a valid inputs.conf configuration parameter.
- C. _INDEXER_GROUP is not a standard inputs.conf setting for routing.
- D. _INDEXER_ROUTING is not the correct parameter name; the actual setting is tcpout routing configuration.
Question 17
To set up a network input in Splunk, what needs to be specified?
- A. File path.
- B. Username and password.
- C. Network protocol and port number.
- D. Network protocol and MAC address.
Show answer and explanation ▾
Correct answer: C
To set up a network input in Splunk, the Network Protocol (TCP, UDP, etc.) and Port Number must be specified. These define the listening parameters for the input. File path applies to file inputs, not network inputs. Username and password are not needed for network inputs. MAC addresses are not relevant to Splunk network input configuration.
Why the other options are wrong:
- A. File path is used for file inputs, not network inputs.
- B. Username and password are not required for network inputs.
- D. MAC address is not a configuration parameter for Splunk network inputs.
Question 18
Which Splunk forwarder type allows parsing of data before forwarding to an indexer?
- A. Universal forwarder
- B. Parsing forwarder
- C. Heavy forwarder
- D. Advanced forwarder
Show answer and explanation ▾
Correct answer: C
The Heavy forwarder is the Splunk component that allows parsing, transformation, and processing of data before forwarding it to indexers. This distinguishes it from the Universal forwarder, which only forwards raw data. Parsing forwarder and Advanced forwarder are not actual Splunk component types. The Heavy forwarder's ability to run custom scripts and apply configurations makes it suitable for complex data processing scenarios.
Why the other options are wrong:
- A. Universal forwarder does not parse data; it forwards raw data only.
- B. Parsing forwarder is not an official Splunk component designation.
- D. Advanced forwarder is not a recognized Splunk forwarder type.
Question 19
Which of the following statements describe deployment management? (Choose all that apply.)
- A. Requires an Enterprise license.
- B. Is responsible for sending apps to forwarders.
- C. Once used, is the only way to manage forwarders.
- D. Can automatically restart the host OS running the forwarder.
Show answer and explanation ▾
Correct answer: B
Deployment management is responsible for sending apps and configurations to forwarders in a centralized manner. It is not the only way to manage forwarders (manual configuration is also possible), it does not require an Enterprise license (it's part of standard Splunk functionality), and it cannot restart the host OS. Its primary function is centralized app and configuration distribution to managed forwarders.
Why the other options are wrong:
- A. Deployment management does not require an Enterprise license; it's a standard feature.
- C. Deployment management is optional; forwarders can be managed manually without it.
- D. Deployment management cannot restart the host OS; it manages Splunk configurations and apps only.
Question 20
During search time, which directory of configuration files has the highest precedence?
- A. $SPLUNK_HOME/etc/system/local
- B. $SPLUNK_HOME/etc/system/default
- C. $SPLUNK_HOME/etc/apps/app1/local
- D. $SPLUNK_HOME/etc/users/admin/local
Show answer and explanation ▾
Correct answer: D
During search time, the configuration precedence order from highest to lowest is: user- specific local settings ($SPLUNK_HOME/etc/users/admin/local), app-specific local settings ($SPLUNK_HOME/etc/apps/app1/local), system local settings ($SPLUNK_HOME/etc/system/local), and finally system default settings ($SPLUNK_HOME/etc/system/default). User-specific configurations have the highest precedence, allowing individual users to override all other configuration levels.
Why the other options are wrong:
- A. System local is lower precedence than app and user local configurations.
- B. System default has the lowest precedence in the hierarchy.
- C. App local is lower precedence than user-specific local settings.
Question 21
What is the correct order of steps in Duo Multifactor Authentication?
- A. 1. Request Login 2. Connect to SAML server 3. Duo MFA 4. Create User session 5. Authentication Granted 6. Log into Splunk
- B. 1. Request Login 2. Duo MFA 3. Authentication Granted 4. Connect to SAML server 5. Log into Splunk 6. Create User session
- C. 1. Request Login 2. Check authentication / group mapping 3. Authentication Granted 4. Duo MFA 5. Create User session 6. Log into Splunk
- D. 1. Request Login 2. Duo MFA 3. Check authentication / group mapping 4. Create User session 5. Authentication Granted 6. Log into Splunk
Show answer and explanation ▾
Correct answer: C
The correct Duo MFA flow with SAML is: user requests login, the system checks authentication and group mapping via SAML, authentication is granted, then Duo MFA is performed as a secondary factor, a user session is created, and finally the user logs into Splunk. This sequence ensures identity verification before MFA challenge, with MFA occurring after initial authentication validation.
Why the other options are wrong:
- A. This sequence connects to SAML before MFA, which reverses the proper order of primary authentication before secondary factors.
- B. This performs MFA before checking authentication and group mapping, which violates the principle of primary authentication before secondary MFA.
- D. This checks authentication after MFA, which is backwards; primary authentication must occur before the MFA challenge.
Question 22
How does the Monitoring Console monitor forwarders?
- A. By pulling internal logs from forwarders.
- B. By using the forwarder monitoring add-on.
- C. With internal logs forwarded by forwarders.
- D. With internal logs forwarded by deployment server.
Show answer and explanation ▾
Correct answer: C
The Monitoring Console monitors forwarders by receiving internal logs that are forwarded by the forwarders themselves to the indexers. Forwarders continuously send their internal metrics and logs (via the tcpout output groups) which the Monitoring Console then collects and displays. This is a push model where forwarders actively send their status information.
Why the other options are wrong:
- A. The Monitoring Console does not pull internal logs; it receives logs that are pushed by forwarders.
- B. While a forwarder monitoring add-on exists, the core mechanism uses internal logs forwarded by the forwarders themselves, not a separate add-on.
- D. The deployment server manages app/configuration distribution, not forwarder monitoring; internal logs come directly from the forwarders.
Question 23
Which of the following are supported options when configuring optional network inputs?
- A. Metadata override, sender filtering options, network input queues (quantum queues)
- B. Metadata override, sender filtering options, network input queues (memory/persistent queues)
- C. Filename override, sender filtering options, network output queues (memory/persistent queues)
- D. Metadata override, receiver filtering options, network input queues (memory/persistent queues)
Show answer and explanation ▾
Correct answer: D
Supported options when configuring optional network inputs include metadata override (to modify source, host, or sourcetype), receiver filtering options (to filter data at the receiving end), and network input queues that can be configured as either memory-based or persistent queues. These options provide flexibility in data processing and queue management for network inputs.
Why the other options are wrong:
- A. Quantum queues is not a real queue type; Splunk uses memory and persistent queues, and 'sender filtering' is not a network input option.
- B. While it mentions memory/persistent queues correctly, 'sender filtering' is not a valid network input configuration option.
- C. Filename override is not applicable to network inputs, and 'network output queues' is the wrong direction; these are input configurations.
Question 24
What is the default character encoding used by Splunk during the input phase?
- A. UTF-8
- B. UTF-16
- C. EBCDIC
- D. ISO 8859
Show answer and explanation ▾
Correct answer: A
UTF-8 is the default character encoding used by Splunk during the input phase. UTF-8 is a variable-width Unicode encoding that is backward compatible with ASCII and is the standard encoding for modern applications. Splunk uses UTF-8 to process incoming data from various sources to ensure proper character handling across different languages and character sets.
Why the other options are wrong:
- B. UTF-16 is not the default; it uses more bytes per character and is not Splunk's standard input encoding.
- C. EBCDIC is an obsolete mainframe encoding and is not used as Splunk's default character encoding.
- D. ISO 8859 (Latin-1) is a legacy single-byte encoding that is not the default; UTF-8 provides better Unicode support.
Question 25
Which of the following enables compression for universal forwarders in outputs.conf?
- A. [udpout:mysplunk_indexer11] compression=true
- B. [tcpout] defaultGroup=my_indexers compressed=true
- C. /opt/splunkforwarder/bin/splunk enable compression
- D. [tcpount:my_indexers] server=mysplunk_indexer1:9997, mysplunk_indexer2:9997 decompression=false
Show answer and explanation ▾
Correct answer: B
Compression for universal forwarders is enabled in outputs.conf using the [tcpout] stanza with the compressed=true parameter. This global setting in the tcpout stanza applies compression to data sent from the forwarder to indexers. The tcpout stanza is the correct location for configuring compression behavior for TCP outputs.
Why the other options are wrong:
- A. The stanza syntax is incorrect; udpout is for UDP outputs (not typically used with compression), and the parameter syntax is wrong.
- C. There is no CLI command to enable compression in Splunk; compression is configured through outputs.conf.
- D. The stanza name is misspelled (tcpount instead of tcpout), and decompression=false is not the correct parameter for enabling compression.
Question 26
User role inheritance allows what to be inherited from the parent role? (Choose all that apply.)
- A. Parents
- B. Capabilities
- C. Index access
- D. Search history
Show answer and explanation ▾
Correct answer: B
User role inheritance in Splunk allows capabilities to be inherited from parent roles. This is the fundamental purpose of role hierarchy-child roles automatically gain all capabilities assigned to their parent roles, reducing administrative overhead and ensuring consistent permission management across related roles.
Why the other options are wrong:
- A. Parent roles themselves are not inherited as objects; rather, their properties cascade downward.
- C. Index access is controlled through role configuration but is not inherited in the traditional sense-it must be explicitly assigned.
- D. Search history is user-specific metadata that does not inherit through role relationships.
Question 27
Which of the following statements apply to directory inputs? (Choose all that apply.)
- A. All discovered text files are consumed.
- B. Compressed files are ignored by default.
- C. Splunk recursively traverses through the directory structure.
- D. When adding new log files to a monitored directory, the forwarder must be restarted to take them into account.
Show answer and explanation ▾
Correct answer: C
Splunk recursively traverses through directory structures when monitoring directory inputs, allowing it to discover and ingest files from subdirectories automatically. This is a core feature that enables flexible log file organization without requiring individual path specifications for each subdirectory.
Why the other options are wrong:
- A. Not all discovered text files are consumed-Splunk respects file type filtering and configuration rules that may exclude certain files.
- B. Compressed files are not ignored by default; Splunk can be configured to handle various file types including compressed archives.
- D. The forwarder does not require a restart when new log files are added to a monitored directory; it detects and begins consuming them automatically.
Question 28
How would you configure your distsearch.conf to allow you to run the search below? sourcetype=access_combined status=200 action=purchase splunk_server_group=HOUSTON
- A. [distributedSearch:NYC] default = false servers = nyc1:8089, nyc2:8089 [distributedSearch:HOUSTON] default = false servers = houston1:8089, houston2:8089
- B. [distributedSearch] servers =nyc1, nyc2, houston1, houston2 [distributedSearch:NYC] default = false servers = nyc1, nyc2 [distributedSearch:HOUSTON] default = false servers = houston1, houston2
- C. [distributedSearch] servers =nyc1:8089, nyc2:8089, houston1:8089, houston2:8089 [distributedSearch:NYC] default = false servers = nyc1:8089, nyc2:8089 [distributedSearch:HOUSTON] default = false servers = houston1:8089, houston2:8089
- D. [distributedSearch] servers =nyc1:8089; nyc2:80893; houston1:8089; houston2:8089 [distributedSearch:NYC] default = false servers = nyc1:8089; nyc2:8089 [distributedSearch:HOUSTON] default = false servers = houston1:80897706; houston2:80898350
Show answer and explanation ▾
Correct answer: C
The distsearch.conf file requires server addresses to include port numbers (8089 is the default Splunk management port). The correct syntax uses the format `servers = host:port, host:port` with commas as delimiters. A parent [distributedSearch] stanza lists all servers, while named stanzas like [distributedSearch:HOUSTON] define server groups that can be referenced in searches via splunk_server_group parameter.
Why the other options are wrong:
- A. Missing port numbers in the server specification, which is required syntax.
- B. The parent [distributedSearch] stanza is missing port numbers, and the query requires proper port notation for distributed search to function.
- D. Uses semicolons as delimiters and contains malformed port numbers, neither of which is valid distsearch.conf syntax.
Question 29
Which of the following is a valid distributed search group?
- A. [distributedSearch:Paris] default = false servers = server1, server2
- B. [searchGroup:Paris] default = false servers = server1:8089, server2:8089
- C. [searchGroup:Paris] default = false servers = server1:9997, server2:9997
- D. [distributedSearch:Paris] default = false servers = server1:8089; server2:8089
Show answer and explanation ▾
Correct answer: A
Option A correctly uses the [distributedSearch:Paris] stanza format with valid server names. While Splunk typically uses port 8089, server names without explicit ports are acceptable in this context. The stanza name and structure match Splunk's distributed search configuration standards.
Why the other options are wrong:
- B. Uses incorrect stanza name [searchGroup:Paris] instead of [distributedSearch:Paris].
- C. Uses incorrect stanza name [searchGroup:Paris] and non-standard port 9997 instead of the management port 8089.
- D. Uses semicolons as server delimiters instead of commas, which is invalid syntax for distsearch.conf.
Question 30
Local user accounts created in Splunk store passwords in which file?
- A. $SPLUNK_HOME/etc/passwd
- B. $SPLUNK_HOME/etc/authentication
- C. $SPLUNK_HOME/etc/users/passwd.conf
- D. $SPLUNK_HOME/etc/users/authentication.conf
Show answer and explanation ▾
Correct answer: A
Local user accounts created in Splunk store their passwords in the $SPLUNK_HOME/etc/passwd file. This is the standard location where Splunk maintains local user authentication credentials when not using external authentication sources.
Why the other options are wrong:
- B. The etc/authentication directory is not the correct location for user password storage.
- C. There is no passwd.conf file in the etc/users directory; passwords are stored in the passwd file at the etc level.
- D. The authentication.conf file is used for authentication configuration, not password storage.
Question 31
For single line event sourcetypes, it is most efficient to set SHOULD_LINEMERGE to what value?
- A. True
- B. False
- C. <regex string>
- D. Newline Character
Show answer and explanation ▾
Correct answer: B
For single-line event sourcetypes, SHOULD_LINEMERGE should be set to False because line merging is unnecessary when each line is already a complete, discrete event. Setting it to False improves parsing efficiency by skipping the line-merging logic entirely.
Why the other options are wrong:
- A. Setting SHOULD_LINEMERGE to True would cause unnecessary processing overhead for data that is already properly separated into single-line events.
- C. A regex string is used for line breaking logic when merging is needed, not for sourcetypes with naturally single-line events.
- D. Newline character is a line breaking delimiter, not a value for the SHOULD_LINEMERGE setting.
Question 32
Which Splunk component does a search head primarily communicate with?
- A. Indexer
- B. Forwarder
- C. Cluster master
- D. Deployment server
Show answer and explanation ▾
Correct answer: A
A search head primarily communicates with indexers to distribute search requests and retrieve results. The indexers contain the actual data and execute the search queries, making them the primary communication target for a search head.
Why the other options are wrong:
- B. Forwarders send data to indexers, not to search heads; search heads do not typically communicate with forwarders.
- C. The cluster master manages indexer cluster configurations but is not the primary search communication target.
- D. The deployment server distributes configurations but is not involved in primary search execution communication.
Question 33
Which of the following authentication types requires scripting in Splunk?
- A. ADFS
- B. LDAP
- C. SAML
- D. RADIUS
Show answer and explanation ▾
Correct answer: D
RADIUS authentication in Splunk requires custom scripting to integrate properly with the RADIUS protocol and Splunk's authentication system. ADFS, LDAP, and SAML are all standard authentication methods that Splunk supports natively through built-in configuration options without requiring custom scripting.
Why the other options are wrong:
- A. ADFS (Active Directory Federation Services) is a standard authentication method supported natively by Splunk.
- B. LDAP is a standard authentication method with built-in support in Splunk.
- C. SAML is a standard authentication method with built-in support in Splunk.
Question 34
Which option accurately describes the purpose of the HTTP Event Collector (HEC)?
- A. A token-based HTTP input that is secure and scalable and that requires the use of forwarders.
- B. A token-based HTTP input that is secure and scalable and that does not require the use of forwarders.
- C. An agent-based HTTP input that is secure and scalable and that does not require the use of forwarders.
- D. A token-based HTTP input that is insecure and non-scalable and that does not require the use of forwarders.
Show answer and explanation ▾
Correct answer: B
The HTTP Event Collector (HEC) is a token-based HTTP input mechanism that is secure (uses tokens for authentication) and scalable (can handle high-volume data ingestion). Critically, HEC does not require the use of forwarders-it allows applications and systems to send data directly to Splunk via HTTP/HTTPS, making it flexible for modern cloud- native and distributed architectures.
Why the other options are wrong:
- A. HEC does not require forwarders; this is one of its key advantages over traditional forwarding methods.
- C. HEC is token-based, not agent-based; it does not require deploying agents on source systems.
- D. HEC is secure and scalable, not insecure and non-scalable; security is a core design principle.
Question 35
What is the difference between the two wildcards ... and * for the monitor stanza in inputs.conf?
- A. ... is not supported in monitor stanzas.
- B. There is no difference, they are interchangeable and match anything beyond directory boundaries.
- C. * matches anything in that specific directory path segment, whereas ... recurses through subdirectories as well.
- D. ... matches anything in that specific directory path segment, whereas * recurses through subdirectories as well.
Show answer and explanation ▾
Correct answer: C
In Splunk's inputs.conf monitor stanzas, the asterisk (*) wildcard matches anything within a single directory path segment, while the ellipsis (...) wildcard recursively traverses through subdirectories. For example, /var/log/* matches files directly in /var/log/, but /var/log/... matches files in /var/log/ and all subdirectories recursively.
Why the other options are wrong:
- A. The ... wildcard is fully supported in monitor stanzas for recursive directory matching.
- B. The wildcards are not interchangeable; they serve different purposes with different matching behaviors.
- D. This reverses the correct behavior; the descriptions are backwards.
Question 36
What type of data is counted against the Enterprise license at a fixed 150 bytes per event?
- A. License data
- B. Metrics data
- C. Internal Splunk data
- D. Internal Windows logs
Show answer and explanation ▾
Correct answer: B
Metrics data is counted against the Enterprise license at a fixed rate of 150 bytes per event. This special metering applies specifically to metrics data, which is typically high- volume, low-cardinality telemetry. License data, internal Splunk data, and Windows logs are either not counted the same way or have different licensing considerations.
Why the other options are wrong:
- A. License data is not metered at the 150 bytes per event rate.
- C. Internal Splunk data generally has different license considerations and metering rules.
- D. Internal Windows logs do not have a standard fixed 150 bytes per event metering rate.
Question 37
How do you remove missing forwarders from the Monitoring Console?
- A. By restarting Splunk.
- B. By rescanning active forwarders.
- C. By reloading the deployment server.
- D. By rebuilding the forwarder asset table.
Show answer and explanation ▾
Correct answer: D
To remove missing or inactive forwarders from the Monitoring Console, you must rebuild the forwarder asset table. This table maintains the list of known forwarders, and rebuilding it removes stale entries for forwarders that are no longer active or present. Simple restarts or rescans do not permanently remove missing forwarders from the console.
Why the other options are wrong:
- A. Restarting Splunk does not remove missing forwarders from the Monitoring Console.
- B. Rescanning active forwarders refreshes the list of active ones but does not remove missing entries.
- C. Reloading the deployment server does not specifically address the Monitoring Console's forwarder asset table.
Question 38
Which Splunk indexer operating system platform is supported when sending logs from a Windows universal forwarder?
- A. Any OS platform.
- B. Linux platform only.
- C. Windows platform only.
- D. None of the above.
Show answer and explanation ▾
Correct answer: A
A Windows universal forwarder can send logs to Splunk indexers running on any supported operating system platform-Linux, Windows, or other supported OSes. Forwarders are designed to be OS-agnostic in terms of their target indexers; the forwarder's OS and the indexer's OS are independent concerns. The forwarder communicates via the Splunk protocol regardless of either system's platform.
Why the other options are wrong:
- B. Indexers running on Linux are supported, but not exclusively; Windows indexers are also valid targets.
- C. Indexers running on Windows are supported, but not exclusively; Linux indexers are also valid targets.
- D. This contradicts the correct answer; indexers on any OS platform are supported.
Question 39
What are the required stanza attributes when configuring the transforms.conf to manipulate or remove events?
- A. REGEX, DEST, FORMAT
- B. REGEX, SRC_KEY, FORMAT
- C. REGEX, DEST_KEY, FORMAT
- D. REGEX, DEST_KEY, FORMATTING
Show answer and explanation ▾
Correct answer: C
When configuring transforms.conf to manipulate or remove events, the required stanza attributes are REGEX, DEST_KEY, and FORMAT. REGEX defines the pattern to match, DEST_KEY specifies where the transformation result should be written, and FORMAT defines how to format the matched data. These three attributes work together to capture, process, and store event modifications.
Why the other options are wrong:
- A. DEST is not a valid attribute; the correct attribute is DEST_KEY.
- B. SRC_KEY is not the correct attribute for this operation; DEST_KEY is required to specify the destination field.
- D. FORMATTING is not a valid attribute; the correct attribute is FORMAT.
Question 40
Which of the following indexes come pre-configured with Splunk Enterprise? (Choose all that apply.)
- A. _licence
- B. _internal
- C. _external
- D. _thefishbucket
Show answer and explanation ▾
Correct answer: B
The _internal index is the only pre-configured index that comes standard with Splunk Enterprise. It stores internal Splunk logs and metadata about Splunk operations. The _licence, _external, and _thefishbucket are not standard pre-configured indexes in Splunk Enterprise.
Why the other options are wrong:
- A. _licence is not a standard pre-configured index in Splunk Enterprise.
- C. _external is not a standard pre-configured index in Splunk Enterprise.
- D. _thefishbucket is not a standard pre-configured index; it is a directory used by inputs for tracking file positions.
Question 41
How often does Splunk recheck the LDAP server?
- A. Every 5 minutes.
- B. Each time a user logs in.
- C. Each time Splunk is restarted.
- D. Varies based on LDAP_refresh setting.
Show answer and explanation ▾
Correct answer: D
Splunk's LDAP rechecking frequency varies based on the LDAP_refresh setting, which is a configurable parameter in authentication.conf. This setting allows administrators to control how often Splunk revalidates LDAP user information, rather than using a fixed interval or event-based trigger. The frequency is determined by the specific configuration value set for LDAP_refresh.
Why the other options are wrong:
- A. LDAP rechecking is not fixed at every 5 minutes; it depends on configuration settings.
- B. While rechecking can occur at login, it is not limited to login events and depends on the LDAP_refresh setting.
- C. Splunk does not recheck LDAP only upon restart; the frequency is configurable.
Question 42
Where are license files stored?
- A. $SPLUNK_HOME/etc/secure
- B. $SPLUNK_HOME/etc/system
- C. $SPLUNK_HOME/etc/licenses
- D. $SPLUNK_HOME/etc/apps/licenses
Show answer and explanation ▾
Correct answer: C
License files in Splunk are stored in the $SPLUNK_HOME/etc/licenses directory. This is the standard location where Splunk Enterprise stores license files that define the data ingestion limits and features available to the instance.
Why the other options are wrong:
- A. $SPLUNK_HOME/etc/secure is used for encrypted authentication and credential files, not license files.
- B. $SPLUNK_HOME/etc/system contains default configuration files and system settings, not license files.
- D. $SPLUNK_HOME/etc/apps/licenses is not a standard location; licenses are stored in the etc/licenses directory.
Question 43
In which scenario would a Splunk Administrator want to enable data integrity check when creating an index?
- A. To ensure that hot buckets are still open for writers and have not been forced to roll to a cold state.
- B. To ensure that configuration files have not been tampered with for auditing and/or legal purposes.
- C. To ensure that user passwords have not been tampered with for auditing and/or legal purposes.
- D. To ensure that data has not been tampered with for auditing and/or legal purposes.
Show answer and explanation ▾
Correct answer: D
Enabling data integrity checks when creating an index ensures that data has not been tampered with, which is critical for auditing and legal compliance purposes. This feature allows Splunk to verify that indexed data remains unchanged and authentic, providing proof of data integrity for regulatory requirements.
Why the other options are wrong:
- A. Hot bucket state management is related to bucket rolling, not data integrity checks.
- B. Configuration file tampering detection is handled through other mechanisms, not index-level data integrity checks.
- C. User password tampering is related to authentication security, not index-level data integrity checks.
Question 44
Which Splunk component performs indexing and responds to search requests from the search head?
- A. Forwarder
- B. Search peer
- C. License master
- D. Search head cluster
Show answer and explanation ▾
Correct answer: B
A search peer is the Splunk component that performs indexing and responds to search requests from the search head. Search peers receive data, index it, and execute distributed searches initiated by the search head, making them essential to Splunk's distributed architecture.
Why the other options are wrong:
- A. A forwarder collects and forwards data to indexers; it does not perform indexing.
- C. A license master manages license usage across the deployment; it does not perform indexing or respond to searches.
- D. A search head cluster manages high availability for search heads; individual nodes do not perform indexing.
Question 45
When deploying apps, which attribute in the forwarder management interface determines the apps that clients install?
- A. App Class
- B. Client Class
- C. Server Class
- D. Forwarder Class
Show answer and explanation ▾
Correct answer: C
The Server Class attribute in the forwarder management interface determines which apps clients (forwarders) will install. Server Class is the configuration stanza that maps apps to specific forwarder groups based on defined criteria, controlling app distribution in the deployment.
Why the other options are wrong:
- A. App Class is not a standard forwarder management attribute for determining app installation.
- B. Client Class is not the correct attribute; the correct attribute is Server Class.
- D. Forwarder Class is not a valid forwarder management attribute for app deployment.
Question 46
In this sourcetype definition the MAX_TIMESTAMP_LOOKAHEAD is missing. Which value would fit best? [sshd_syslog] TIME_PREFIX = ^ TIME_FORMAT = %Y-%m-%d %H:%M:%S.%3N %z LINE_BREAKER = ([\r\n]+)\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2} SHOULD_LINEMERGE = false - TRUNCATE = 0 - Event example: 2018-04-13 13:42:41.214 -0500 server sshd[26219]: Connection from 172.0.2.60 port 47366
- A. MAX_TIMESTAMP_LOOKAHEAD = 5
- B. MAX_TIMESTAMP_LOOKAHEAD = 10
- C. MAX_TIMESTAMP_LOOKAHEAD = 20
- D. MAX_TIMESTAMP_LOOKAHEAD = 30
Show answer and explanation ▾
Correct answer: D
MAX_TIMESTAMP_LOOKAHEAD should be set to 30 for this sourcetype. The timestamp format is '2018-04-13 13:42:41.214 -0500', which is 29 characters long. The MAX_TIMESTAMP_LOOKAHEAD value must be large enough to capture the entire timestamp, so 30 provides sufficient buffer to ensure the complete timestamp is recognized and parsed correctly.
Why the other options are wrong:
- A. MAX_TIMESTAMP_LOOKAHEAD = 5 is far too small to capture the full timestamp of 29 characters.
- B. MAX_TIMESTAMP_LOOKAHEAD = 10 is insufficient to capture the complete timestamp including timezone offset.
- C. MAX_TIMESTAMP_LOOKAHEAD = 20 is slightly too small; the timestamp requires at least 29-30 characters for complete capture.
Question 47
What hardware attribute would you need to be changed to increase the number of simultaneous searches (ad-hoc and scheduled) on a single search head?
- A. Disk
- B. CPUs
- C. Memory
- D. Network interface cards
Show answer and explanation ▾
Correct answer: B
CPU is the primary hardware bottleneck for executing simultaneous searches on a search head. Each search requires processing power to dispatch queries, parse results, and execute search commands. While memory and disk also play roles, increasing CPU cores/performance directly increases the number of concurrent searches that can be handled. Network interface cards would not be the limiting factor for ad-hoc and scheduled searches.
Why the other options are wrong:
- A. Disk capacity primarily affects data storage and indexing performance, not the ability to run simultaneous searches.
- C. While memory is important for search performance, CPU is the primary limiting factor for concurrent search execution.
- D. Network interface cards affect data transmission rates, not the number of simultaneous searches a search head can execute.
Question 48
What conf file needs to be edited to set up distributed search groups?
- A. props.conf
- B. search.conf
- C. distsearch.conf
- D. distibutedsearch.conf
Show answer and explanation ▾
Correct answer: C
The distsearch.conf configuration file is used to set up and configure distributed search groups in Splunk. This file contains settings for search peers, search head pooling, and distributed search behavior. props.conf handles field properties, search.conf handles search behavior, and the misspelled 'distibutedsearch.conf' is not a valid Splunk configuration file.
Why the other options are wrong:
- A. props.conf is used for field extraction and parsing, not distributed search configuration.
- B. search.conf contains search-related settings but is not used for configuring distributed search groups.
- D. This filename is misspelled and is not a valid Splunk configuration file.
Question 49
After configuring a universal forwarder to communicate with an indexer, which index can be checked via the Splunk Web UI for a successful connection?
- A. index=main
- B. index=test
- C. index=summary
- D. index=_internal
Show answer and explanation ▾
Correct answer: D
The index=_internal index contains internal Splunk logs and metrics and is the appropriate place to verify successful communication between a universal forwarder and an indexer. You can search the _internal index for connection logs, metrics, and events that confirm the forwarder has successfully connected and is sending data to the indexer. The main, test, and summary indexes are not used for this diagnostic purpose.
Why the other options are wrong:
- A. The main index is where regular indexed data goes, not where forwarder connection diagnostics are logged.
- B. The test index is not a standard Splunk index for connection verification.
- C. The summary index is used for storing summary data from scheduled searches, not for diagnostic logs.
Question 50
Which is a valid stanza for a network input?
- A. [udp://172.16.10.1:9997] connection = dns sourcetype = dns
- B. [any://172.16.10.1:10001] connection_host = ip sourcetype = web
- C. [tcp://172.16.10.1:9997] connection_host = web sourcetype = web
- D. [tcp://172.16.10.1:10001] connection_host = dns sourcetype = dns
Show answer and explanation ▾
Correct answer: B
Option B is the only valid network input stanza. The correct syntax for network inputs uses the format [protocol://host:port] followed by configuration attributes. Valid protocols in Splunk include tcp, udp, and any (which accepts both). The attribute connection_host is a valid parameter that accepts values like ip, dns, and host. Option A uses 'connection' instead of 'connection_host', which is invalid. Option C uses 'web' as a value for connection_host, which is not a valid option. Option D has correct syntax but uses 'dns' as a connection_host value, which is not standard.
Why the other options are wrong:
- A. Uses 'connection' instead of the valid attribute 'connection_host'.
- C. Uses 'web' as a value for connection_host, which is not a valid parameter value.
- D. Uses 'dns' as a connection_host value, which is not a standard valid option.
Get the complete SPLK-1003 bank
These 50 questions are roughly 28% of the bank. The full pack has 209 real SPLK-1003 questions, each with the same depth of explanation, plus a questions-only PDF for timed practice and free updates forever.
View the full Splunk SPLK-1003 question bank →