SPLK-1003

Free SPLK-1003 practice questions

10 questions from our SPLK-1003 practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.

Back to the SPLK-1003 practice exams

Question 1 of 10, Splunk Admin Basics

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?

  1. AA heavy forwarder, which is a full Splunk Enterprise instance that forwards data Correct answer
  2. BA universal forwarder configured with a props.conf TRANSFORMS setting for routing
  3. CA universal forwarder with an outputs.conf file that lists two target groups
  4. DA deployment client that inherits its routing rules from the deployment server

Answer and 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, License Management

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?

  1. AThe search job inspector for a search against the main index over the same 30 days
  2. BThe output of splunk btool server list on the license manager with the debug flag
  3. CThe Indexing Performance dashboard on each indexer, filtered by the parsing queue
  4. DThe License Usage report on the license manager, split by source type, host, or source Correct answer

Answer and 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, Splunk Configuration Files

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?

  1. Asplunk check-integrity -index main
  2. Bsplunk diag --collect=conf
  3. Csplunk btool check Correct answer
  4. Dsplunk reload deploy-server

Answer and 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, Splunk Indexes

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

  1. AfrozenTimePeriodInSecs = 7776000 Correct answer
  2. BmaxWarmDBCount = 90
  3. CmaxHotSpanSecs = 7776000
  4. DcoldToFrozenDir = 90d

Answer and 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, Splunk User Management

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

  1. Asplunk create user jsmith -password 'S3cure!pass' -roles user,power -app search
  2. Bsplunk add role jsmith -password 'S3cure!pass' -capability search -auth admin
  3. Csplunk add user jsmith -password 'S3cure!pass' -role user -auth admin:changeme Correct answer
  4. Dsplunk edit user jsmith -new-password 'S3cure!pass' -role power -auth admin

Answer and 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, Splunk Authentication Management

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?

  1. AScripted authentication with authType = Scripted and a Python script that queries the database Correct answer
  2. BSAML authentication with the database configured as an identity provider in authentication.conf
  3. CNative authentication with a nightly import of the database users into $SPLUNK_HOME/etc/passwd
  4. DLDAP authentication with a strategy whose host value points to the database listener port

Answer and 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, Getting Data In

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

  1. AThe universal forwarder does not include Python or Splunk Web and usually forwards unparsed data Correct answer
  2. BThe universal forwarder can index data locally, while the heavy forwarder can never store data
  3. CThe universal forwarder needs its own Enterprise license, while the heavy forwarder runs license-free
  4. DThe universal forwarder parses events locally, while the heavy forwarder sends raw TCP streams

Answer and 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, Distributed Search

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

  1. AThe search head's public key is missing from the peer's distServerKeys directory Correct answer
  2. BThe peer's indexes.conf lacks a repFactor = auto setting on its custom indexes
  3. CThe peer's outputs.conf does not list the search head as a forwarding target
  4. DThe peer's outputs.conf does not list the search head as a forwarding target group

Answer and 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, Getting Data In - Staging

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

  1. AOn the heavy forwarder, and the indexer then skips parsing for the already-cooked data Correct answer
  2. BOn the universal forwarder, because it is the first Splunk instance to touch the data
  3. COn the indexer, because only an indexer can run the parsing pipeline on events
  4. DOn both forwarders, with the heavy forwarder repeating the line breaking a second time

Answer and 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, Forwarder Management

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

  1. ARun splunk reload deploy-server Correct answer
  2. BRun splunk apply cluster-bundle
  3. CRun splunk restart splunkweb
  4. DRun splunk refresh deploy-clients

Answer and 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.