# Free SPLK-1003 practice questions

> 10 free SPLK-1003 practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/splunk-enterprise-administration/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/splunk-enterprise-administration/

### Question 1 of 10

A team needs a forwarder that can parse events, apply index-time transforms to route data to different indexes, and run Python-based modular inputs. Which instance type should they use?

- A. A heavy forwarder, which is a full Splunk Enterprise instance that forwards data
- B. A universal forwarder configured with a props.conf TRANSFORMS setting for routing
- C. A universal forwarder with an outputs.conf file that lists two target groups
- D. A deployment client that inherits its routing rules from the deployment server

**Answer:** A

**Explanation:** A heavy forwarder is a full Splunk Enterprise instance, so it runs the parsing pipeline, applies index-time transforms, and includes Python for modular inputs. The universal forwarder does not parse most data or ship Python, so index-time TRANSFORMS on it have no effect, and being a deployment client only governs how configuration is delivered, not what processing the instance can perform.

### Question 2 of 10

An admin reviews license usage and finds that one sourcetype consumes most of the daily volume after a noisy debug log was enabled. The goal is to see which source and host are responsible for the spike over the past 30 days. Where is this information most readily available?

- A. The search job inspector for a search against the main index over the same 30 days
- B. The output of splunk btool server list on the license manager with the debug flag
- C. The Indexing Performance dashboard on each indexer, filtered by the parsing queue
- D. The License Usage report on the license manager, split by source type, host, or source

**Answer:** D

**Explanation:** The license usage report view on the license manager, built from license_usage.log in _internal, can split historical usage by source type, host, source, index, or pool. Indexing performance dashboards show throughput and queue health rather than license accounting, the job inspector describes one search's execution, and btool only displays configuration settings.

### Question 3 of 10

After editing several .conf files by hand on a heavy forwarder, an administrator wants to detect typos such as misspelled attribute names before restarting. Which command helps?

- A. splunk check-integrity -index main
- B. splunk diag --collect=conf
- C. splunk btool check
- D. splunk reload deploy-server

**Answer:** C

**Explanation:** btool check scans configuration files and reports invalid stanzas or unknown attribute names, which catches typos before a restart. check-integrity verifies hashes of indexed data rather than configuration syntax, diag gathers a support bundle without validating settings, and reload deploy-server only refreshes a deployment server's serverclass information.

### Question 4 of 10

An index must keep data searchable for 90 days and then delete it. Which indexes.conf attribute controls this time-based retention?

- A. frozenTimePeriodInSecs = 7776000
- B. maxWarmDBCount = 90
- C. maxHotSpanSecs = 7776000
- D. coldToFrozenDir = 90d

**Answer:** A

**Explanation:** frozenTimePeriodInSecs sets the age at which buckets roll to frozen, and with no archive configured frozen data is deleted; 7776000 seconds is 90 days. maxHotSpanSecs limits the time span inside a hot bucket, maxWarmDBCount limits the number of warm buckets rather than their age, and coldToFrozenDir takes a directory path for archiving, not a duration.

### Question 5 of 10

An administrator wants to create a native Splunk user from the command line on a search head. Which command is correct?

- A. splunk create user jsmith -password 'S3cure!pass' -roles user,power -app search
- B. splunk add role jsmith -password 'S3cure!pass' -capability search -auth admin
- C. splunk add user jsmith -password 'S3cure!pass' -role user -auth admin:changeme
- D. splunk edit user jsmith -new-password 'S3cure!pass' -role power -auth admin

**Answer:** C

**Explanation:** splunk add user with -password, -role, and -auth creates a native account and assigns its role. There is no create user subcommand, edit user modifies an account that already exists rather than creating one, and add role creates a role rather than a user account.

### Question 6 of 10

An organization's user directory is a custom database with no LDAP or SAML interface. The administrator wants Splunk to validate logins against it. Which option fits this requirement?

- A. Scripted authentication with authType = Scripted and a Python script that queries the database
- B. SAML authentication with the database configured as an identity provider in authentication.conf
- C. Native authentication with a nightly import of the database users into $SPLUNK_HOME/etc/passwd
- D. LDAP authentication with a strategy whose host value points to the database listener port

**Answer:** A

**Explanation:** Scripted authentication lets Splunk call a custom script that implements user login and lookup functions against any external system. An LDAP strategy requires a directory that speaks LDAP, SAML requires a real SAML identity provider, and nightly imports into the native passwd file would copy credentials instead of validating them against the database.

### Question 7 of 10

Which statement describes a key difference between a universal forwarder and a heavy forwarder?

- A. The universal forwarder does not include Python or Splunk Web and usually forwards unparsed data
- B. The universal forwarder can index data locally, while the heavy forwarder can never store data
- C. The universal forwarder needs its own Enterprise license, while the heavy forwarder runs license-free
- D. The universal forwarder parses events locally, while the heavy forwarder sends raw TCP streams

**Answer:** A

**Explanation:** The universal forwarder is a lightweight package without Python or Splunk Web that generally sends unparsed data for the indexer to parse. Parsing happens on the heavy forwarder rather than the universal one, the universal forwarder has its own built-in license, and the heavy forwarder can index locally if configured to.

### Question 8 of 10

After adding a new peer, searches from the search head fail with authentication errors against that peer. What is the MOST likely cause?

- A. The search head's public key is missing from the peer's distServerKeys directory
- B. The peer's indexes.conf lacks a repFactor = auto setting on its custom indexes
- C. The peer's outputs.conf does not list the search head as a forwarding target
- D. The peer's outputs.conf does not list the search head as a forwarding target group

**Answer:** A

**Explanation:** Distributed search authenticates the search head to each peer with the search head's public key, which must be present under the peer's distServerKeys directory, normally placed by add search-server with valid remote credentials. repFactor applies to cluster replication, peers do not forward to search heads, and license pools are unrelated to search authentication.

### Question 9 of 10

Data flows from a universal forwarder to a heavy forwarder and then to an indexer. Where is the parsing phase performed for this data?

- A. On the heavy forwarder, and the indexer then skips parsing for the already-cooked data
- B. On the universal forwarder, because it is the first Splunk instance to touch the data
- C. On the indexer, because only an indexer can run the parsing pipeline on events
- D. On both forwarders, with the heavy forwarder repeating the line breaking a second time

**Answer:** A

**Explanation:** The first full Splunk Enterprise instance in the path, here the heavy forwarder, parses the data and sends it on as cooked events, so the indexer does not parse it again. The universal forwarder does not parse most data, the indexer is not the only instance that can parse, and parsing is not repeated on each hop.

### Question 10 of 10

After editing serverclass.conf by hand on a deployment server, how can the administrator make it re-read the configuration without restarting splunkd?

- A. Run splunk reload deploy-server
- B. Run splunk apply cluster-bundle
- C. Run splunk restart splunkweb
- D. Run splunk refresh deploy-clients

**Answer:** A

**Explanation:** reload deploy-server re-reads serverclass.conf and the deployment-apps directory so clients receive changes at their next phone home. Restarting Splunk Web does not reload deployment configuration, apply cluster-bundle pushes an indexer cluster bundle, and refresh deploy-clients is not a valid command.

Ready for a timed run? Take the free 15-question SPLK-1003 mini exam: https://devopscodelab.com/app/exams/splunk-enterprise-administration/mini/

DevOpsCode Lab is not affiliated with Splunk. SPLK-1003 and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
