Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Splunk
Exam Format
Registration
Validity
Skills this practice test covers
- Trace a setting through configuration layering with btool to find which file wins.
- Set retention for an index with frozenTimePeriodInSecs and the bucket paths in indexes.conf.
- Push apps to forwarders through a deployment server, server classes and deployment clients.
- Configure distributed search between a search head and its search peers.
- Create monitor, network, scripted, WMI and HTTP Event Collector inputs.
- Mask, route or drop events at index time with props.conf, transforms.conf and SEDCMD.
Explore related topics
SPLK-1003 exam content
17 domains · 48 topics · 230 of 328 questions sorted by domain
Splunk Admin Basics9 questions
This short domain sets the vocabulary for the rest of the exam. Candidates identify the Splunk components, such as indexers, search heads, forwarders and the deployment server, and describe the job of each.
Skills tested
- Identify the function of indexers, search heads and forwarders.
- Describe where the deployment server fits in a distributed deployment.
Questions by topic
- Splunk service management3
- Identify Splunk components6
License Management7 questions
Splunk licenses set how much data can be indexed each day. Candidates identify the license types and explain what causes a license violation and what it affects.
Skills tested
- Tell the Enterprise, Free, Forwarder and Dev/Test license types apart.
- Explain what causes license warnings and violations, and their impact.
Questions by topic
- Understand license violations3
- Identify license types4
Splunk Configuration Files16 questions
Much of Splunk is set in .conf files spread across system and app directories. Candidates describe the directory structure, explain how Splunk layers and ranks the files, and check the result with btool.
Skills tested
- Describe the default and local directories under $SPLUNK_HOME/etc/system and $SPLUNK_HOME/etc/apps.
- Apply precedence rules in the global context and the app context.
- Run btool with the debug option to see which file sets each value.
Questions by topic
- Use btool to examine configuration settings9
- Describe Splunk configuration directory structure3
- Understand configuration precedence4
Splunk Indexes21 questions
Indexes store the data in buckets that age from hot to warm, cold and frozen. Candidates describe the index structure, set options in indexes.conf, check data integrity, apply a retention policy and explain the fishbucket.
Skills tested
- Follow a bucket from hot to warm, cold and frozen, and name what triggers each move.
- Set homePath, coldPath and frozenTimePeriodInSecs in indexes.conf.
- Check index data integrity and repair a damaged bucket.
- Explain how the fishbucket stops Splunk from indexing a file twice.
Questions by topic
- Describe the fishbucket6
- Apply a data retention policy8
- Describe index structure3
- Index maintenance3
- Describe indexes.conf options1
Splunk User Management16 questions
Access in Splunk is based on roles. Candidates describe the built-in roles, create a custom role with its capabilities and index access, and add users.
Skills tested
- Describe the admin, power and user roles and the capabilities each grants.
- Create a custom role that inherits from another role and limits index access.
- Add users and assign them roles.
Questions by topic
- Create a custom role8
- Describe user roles in Splunk8
Splunk Authentication Management8 questions
This domain covers how users prove who they are. Candidates connect Splunk to LDAP, list the other authentication options and describe the steps to turn on multifactor authentication.
Skills tested
- Integrate Splunk with LDAP and map LDAP groups to Splunk roles.
- Set the bind DN that Splunk uses to query the directory.
- Describe the steps to enable multifactor authentication, such as Duo integration.
Questions by topic
- Integrate Splunk with LDAP4
- List other user authentication options4
Getting Data In12 questions
This domain introduces inputs and forwarders. Candidates describe the basic settings of an input, list the forwarder types, configure a forwarder and add an input to a universal forwarder from the CLI.
Skills tested
- Set the basic input attributes: host, source, sourcetype and index.
- Compare the universal forwarder with the heavy forwarder.
- Add an input to a universal forwarder with a CLI command.
Questions by topic
- List Splunk input options2
- Configure the receiver1
- List Splunk forwarder types4
- Heavy Forwarder capabilities3
- Add an input to UF using CLI2
Distributed Search24 questions
In larger deployments, a search head sends each search to many indexers. Candidates explain how distributed search works, configure search peers and groups, and list the options for scaling search heads.
Skills tested
- Explain how a search head sends searches to its search peers and merges the results.
- Add search peers and configure a distributed search group in distsearch.conf.
- List search head scaling options, such as search head clustering.
Questions by topic
- Describe how distributed search works6
- List search head scaling options5
- Configure a distributed search group10
- Search Head Cluster Management3
Getting Data In - Staging8 questions
This domain describes the path that data takes inside Splunk. Candidates list the three phases of the indexing process (input, parsing and indexing) and the input options available.
Skills tested
- Place each processing step in the input, parsing or indexing phase.
- List the Splunk input options and when each one fits.
Questions by topic
- List the three phases of the Splunk Indexing process6
- List Splunk input options2
Configuring Forwarders10 questions
Forwarders must know where to send data and how. Candidates configure forwarders and the receivers they send to, and identify additional options such as acknowledgments and compression.
Skills tested
- Open a receiving port on the indexer and point the forwarder at it.
- Turn on acknowledgments so that forwarded data is not lost in transit.
- Identify forwarder options such as compression and event batching.
Questions by topic
- Identify additional Forwarder options7
- Heavy Forwarder capabilities1
- Configure the receiver2
Forwarder Management22 questions
With many forwarders, central management saves time. Candidates use the deployment server, deployment apps, deployment clients and server classes, and monitor what was deployed.
Skills tested
- Explain what the deployment server does and when to use it.
- Configure deployment clients with deploymentclient.conf.
- Group clients into server classes and assign deployment apps to them.
- Monitor forwarder management activities and find deployment errors.
Questions by topic
- Configure client groups7
- Troubleshooting forwarder management8
- Monitor forwarder management activities4
- Describe Splunk Deployment Server3
Monitor Inputs10 questions
Monitor inputs read files and directories as they change. Candidates create these inputs, use their optional settings and deploy them to remote systems.
Skills tested
- Create file and directory monitor inputs in inputs.conf.
- Use optional settings such as ignoreOlderThan and crcSalt.
- Deploy a monitor input to remote forwarders.
Questions by topic
- Use optional settings for monitor inputs10
Network and Scripted Inputs9 questions
Not all data sits in files. Candidates create TCP and UDP network inputs, describe their optional settings and write a basic scripted input.
Skills tested
- Create TCP and UDP inputs and set connection_host.
- Write a basic scripted input that runs at a set interval.
Questions by topic
- Create a basic scripted input6
- Create network (TCP and UDP) inputs3
Agentless Inputs9 questions
Some data arrives without a forwarder on the source. Candidates create Windows Management Instrumentation (WMI) inputs and describe the HTTP Event Collector and its tokens.
Skills tested
- Create a WMI input to collect data from Windows hosts.
- Describe how applications send events to the HTTP Event Collector with HEC tokens.
Questions by topic
- Describe HTTP Event Collector5
- Creating Windows Management Instrumentation (WMI) inputs4
Fine Tuning Inputs8 questions
This domain looks closely at the input phase. Candidates describe the default processing at input and adjust options such as sourcetype fine-tuning and character set encoding.
Skills tested
- Describe what Splunk does to data by default in the input phase.
- Override the sourcetype and set the character set encoding for an input.
Questions by topic
- Configure input phase options, such as sourcetype fine-tuning and character set encoding7
- Optimize and configure event line breaking1
Parsing Phase and Data21 questions
Parsing turns a stream of data into events with timestamps. Candidates explain the default parsing, tune line breaking, control how timestamps and time zones are assigned, and check the result with Data Preview.
Skills tested
- Tune event line breaking with settings such as BREAK_ONLY_BEFORE.
- Explain how Splunk finds or assigns timestamps and time zones.
- Validate event creation with Data Preview before indexing.
Questions by topic
- Use Data Preview to validate event creation during the parsing phase9
- Explain how timestamps and time zones are extracted or assigned to events7
- Optimize and configure event line breaking5
Manipulating Raw Data20 questions
The last domain changes data before it is written to disk. Candidates use props.conf and transforms.conf to mask or delete data, override the sourcetype or host, route events to an index or drop them, and use SEDCMD.
Skills tested
- Mask sensitive values with SEDCMD or with a transform.
- Route events to another index with DEST_KEY and _MetaData:Index.
- Keep unwanted events out of the index with a filtering transform.
Questions by topic
- Use transformations with props.conf and transforms.conf4
- Route events to specific indexes based on event content4
- Prevent unwanted events from being indexed7
- Use SEDCMD to modify raw data5
Requirements
- Required: Splunk Core Certified Power User before this exam.
- Recommended: hands-on Splunk Enterprise administration, including data ingestion and management.
- Recommended: knowledge of Splunk components, architecture and distributed deployments.
About the SPLK-1003 exam
SPLK-1003 is Splunk's exam for administrators who install, configure and maintain Splunk Enterprise. Its domains cover licenses and configuration files, indexes, users and authentication, forwarders and their management, data inputs, parsing and index-time changes to raw data. Candidates must already hold Splunk Core Certified Power User. Passing earns the Splunk Enterprise Certified Admin certification, a Professional-level credential.
The PlanetCert practice test puts the most questions on distributed search, forwarder management, indexes, parsing and raw data changes. The explanations show how the pieces connect. For example, a TRANSFORMS setting in props.conf does nothing without a matching stanza in transforms.conf. Flashcard Mode suits the many settings and file names, from frozenTimePeriodInSecs to deploymentclient.conf. Brainy AI Assistant can trace a setting through configuration layering or explain btool output line by line.
How to earn the certification
- Earns
- Splunk Enterprise Certified AdminProfessional
- Before
- SPLK-1002 Splunk Core Certified Power User
Required before SPLK-1003. It proves the search and knowledge object skills that administration builds on.
- SPLK-1001 Splunk Core Certified User
The first exam in the Splunk Core track, usually taken before Power User.
- SPLK-1002 Splunk Core Certified Power User
- After
- SPLK-2002 Splunk Enterprise Certified Architect
The architect path, for those who design and troubleshoot large distributed Splunk deployments.
- SPLK-2001 Splunk Certified Developer
The developer path, for those who build Splunk apps and dashboards.
- SPLK-2002 Splunk Enterprise Certified Architect
How to prepare for SPLK-1003
- 1
Stand up a three-instance lab
Run one indexer, one search head and one universal forwarder, in virtual machines or containers. Distributed search and forwarder management both need more than one instance.
- 2
Edit .conf files by hand
Make changes in local directories instead of Splunk Web, and check each change with btool. This builds the precedence skills that many configuration questions test.
- 3
Run a deployment server
Set up a deployment server, a server class and a deployment app, then watch a forwarder pick up the app. Forwarder management is one of the largest topics in the practice test.
- 4
Onboard a messy log file
Index a log with multi-line events and odd timestamps. Fix line breaking and timestamps in Data Preview, then mask a field with SEDCMD and route some events to a second index.
- 5
Close out with timed drills
Take the SPLK-1003 practice test in Timed Mode, then retry each missed setting in the lab. Brainy AI Assistant can compare two similar settings, such as crcSalt and initCrcLength.
Start a timed SPLK-1003run
Splunk's blueprint points to the Splunk Enterprise Certified Admin Learning Path, including the Splunk Enterprise System Administration course, along with Splunk Docs.
Who SPLK-1003 is for
- Administrators who install and maintain Splunk Enterprise for their organization.
- System administrators who manage Splunk alongside other platforms.
- Security operations center (SOC) administrators who keep the security team's data flowing.
- Power User holders who are moving from searching data to running the platform.
Typical job titles: Splunk administrator · Systems administrator · SIEM engineer · Observability engineer · SOC engineer
SPLK-1003 glossary
19 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- btool
- A Splunk command-line tool that shows the merged result of configuration files and, with the debug option, which file set each value.
- Configuration layering
- The way Splunk merges copies of the same .conf file from several directories into one working configuration, by precedence.
- crcSalt
- An inputs.conf setting that adds a value to a file's checksum, so that files which start the same way are still read as separate files.
- Data Preview
- The Splunk Web tool that shows how data will be broken into events and timestamped before it is indexed.
- Deployment Server
- A Splunk instance that sends apps and configuration to many deployment clients, such as forwarders, from one place.
- deploymentclient.conf
- The configuration file on a Splunk instance that names the deployment server it should contact.
- distsearch.conf
- The configuration file that lists a search head's search peers and its distributed search settings.
- Fishbucket
- An internal index where Splunk records how far it has read each monitored file, so that it does not index the same data twice.
- Frozen buckets
- Data past its retention limit. By default Splunk deletes it, but it can archive it instead.
- frozenTimePeriodInSecs
- The indexes.conf setting that sets how old data in an index can get before it rolls to frozen.
- Heavy Forwarder
- A full Splunk instance used as a forwarder, which can parse, filter and route data before sending it on.
- Hot buckets
- Index buckets that are open and still receiving new events. They roll to warm when they are full or when Splunk restarts.
- HTTP Event Collector
- A Splunk input that receives events that applications send over HTTP or HTTPS, using tokens instead of a forwarder.
- LDAP
- A directory protocol that lets Splunk check user names and passwords against a directory and map its groups to Splunk roles.
- Search head
- The Splunk instance that takes a user's search, sends it to the indexers and merges their results.
- SEDCMD
- A props.conf setting that edits raw data at index time with sed-style replacements, for example to mask account numbers.
- Server classes
- Groups of deployment clients, defined on the deployment server, that receive the same deployment apps.
- transforms.conf
- The configuration file that defines transformations, such as routing, masking or filtering, which props.conf then calls.
- Universal Forwarder
- A lightweight Splunk agent that collects data on a host and sends it to indexers, mostly without parsing it.