Sign in
Home/Splunk/Splunk Core Certified User (SPLK-1001)/Free questions

Splunk Core Certified User (SPLK-1001) — Free Practice Questions

10 free sample questions from a bank of 299, with the correct answers and explanations. No signup required — start practising right now.

1Which search string only returns events from hostWWW3?
  • host=*
  • host=WWW3
  • host=WWW*
  • Host=WWW3
Answer: B

The short version

B — host equals WWW3 returns only that host events. Exact field-value matching scopes results to the single host without wildcards or case errors.

Key concepts in this question

  • host field: the default metadata field recording which forwarder or system sent each event.
  • Exact match syntax: host equals value with no asterisk restricts results to that literal host name.
  • Wildcard host equals star: matches every host and therefore fails the only-WWW3 requirement.
  • Prefix wildcard WWW star: includes WWW3 but also any sibling hosts sharing the prefix, broadening scope.
  • Case sensitivity: field names and values follow case rules, so capitalized Host does not equal lowercase host behavior.

Why B is correct

B is correct because host equals WWW3 filters the index to events whose host metadata exactly equals WWW3. No wildcard expansion occurs and no other hosts qualify, satisfying the only-returns-events-from requirement. The syntax is efficient, precise and directly answers the search-string question.

Why the others are wrong

  • A. host equals star matches all hosts, returning far more than just WWW3 events.
  • C. host equals WWW star includes WWW3 plus any other WWW-prefixed hosts, violating only semantics.
  • D. Capitalized Host does not reference the standard lowercase host field correctly, so it misses the target.

SPLK-1001 exam tip

For SPLK-1001 host filtering, use exact host equals name for one host and add star only for prefix groups.

2When editing a dashboard, which of the following are possible options? (Choose all that apply.)
  • Add an output.
  • Export a dashboard panel.
  • Modify the chart type displayed in a dashboard panel.
  • Drag a dashboard panel to a different location on the dashboard.
Answer: C

The short version

C — Modifying the chart type is the settled editable dashboard-panel option. Edit mode lets authors switch visualizations while layout options in this bank are excluded.

Key concepts in this question

  • Dashboard edit mode: the authoring state exposing visualization, search and layout controls for owned dashboards.
  • Chart-type modification: changing column to line, pie or table rendering for an existing panel search.
  • Add-output misconception: outputs belong to form and workflow constructs, not to dashboard-panel editing choices here.
  • Export misconception: exporting panel data is a view-time action rather than an edit-mode structural option in this key.
  • Drag-to-relocate misconception: layout dragging may exist in Studio but is excluded from the settled correct set for this item.

Why C is correct

C is correct because the settled key identifies chart-type change as the possible edit option under test. Switching visualization preserves the underlying search while altering presentation for clearer insight. That capability is central to dashboard refinement and matches the choose-all-that-apply key containing only C.

Why the others are wrong

  • A. Adding an output is not among the settled dashboard edit options for this question.
  • B. Exporting a panel is a consumption action, not the settled edit-mode modification tested here.
  • D. Dragging a panel to a new location is excluded from the settled correct set for this bank item.

SPLK-1001 exam tip

On SPLK-1001 dashboard edits, lock in modify chart type as the safe settled answer for this bank.

3Portal for Splunk apps can be accessed through www.splunkbase.com
  • False
  • True
Answer: B

The short version

B — True, Splunkbase apps live at splunkbase dot com. The portal hosts certified apps, add-ons and technical previews for platform extension.

Key concepts in this question

  • Splunkbase: the official app marketplace for Splunk Cloud and Enterprise offering search, install and rating flows.
  • Apps versus add-ons: prebuilt dashboards plus data-collection and normalization packs extending search capabilities.
  • Portal access path: browser navigation to www.splunkbase.com with Splunk account authentication.
  • True-or-False discipline: the statement asserts a verifiable location that is either exactly right or wrong.
  • Ecosystem trust: downloading from the official portal ensures signing, review and version compatibility.

Why B is correct

B is correct because Splunk documents Splunkbase at splunkbase dot com as the portal for apps. Users browse categories, check compatibility with their Splunk version and deploy directly or download packages. That official location confirms the statement as true under the settled key.

Why the others are wrong

  • A. False is wrong because the Splunkbase portal is indeed reachable through www.splunkbase.com per Splunk docs.

SPLK-1001 exam tip

For SPLK-1001 fundamentals, memorize Splunkbase equals splunkbase dot com for all app-portal questions.

4Splunk shows data in __________________.
  • ASCII Character order.
  • Reverse chronological order.
  • Alphanumeric order.
  • Chronological order.
Answer: B

The short version

B — Splunk displays data in reverse chronological order by default. Newest events appear first using event time for triage efficiency.

Key concepts in this question

  • Reverse chronological order: descending time sort with the most recent matching event at the top of results.
  • Event time basis: the _time field extracted at index time that drives display sequencing.
  • ASCII character order: byte-value sorting relevant to lexing, not to Splunk result presentation.
  • Alphanumeric order: sorting by field strings, useful for lookups but not the default event timeline.
  • Chronological order: ascending oldest-first display, opposite of the Splunk default for investigations.

Why B is correct

B is correct because Splunk search results timeline and event list default to newest first so analysts see current impact immediately. The reverse order accelerates incident response by surfacing fresh failures before historical context. That default presentation matches the settled key exactly.

Why the others are wrong

  • A. ASCII Character order describes encoding collation, not Splunk default event display sequencing.
  • C. Alphanumeric order would sort by strings rather than time, hiding recency needed for operations.
  • D. Chronological oldest-first order would bury new events at the bottom, opposite of Splunk behavior.

SPLK-1001 exam tip

Remember newest first for SPLK-1001: Splunk default display equals reverse chronological by _time.

5Which of the following can be used as wildcard search in Splunk?
  • =
  • >
  • !
  • *
Answer: D

The short version

D — Asterisk is the Splunk wildcard for search terms. It matches zero or more characters inside field values and raw text.

Key concepts in this question

  • Wildcard semantics: a placeholder expanding matches when full values are unknown or variable.
  • Asterisk behavior: placed at ends or inside terms, such as questionnaire P star, to broaden recall.
  • Equals sign: an exact-match operator between field and value, not a wildcard character.
  • Greater-than sign: a numeric comparison for ranges, unable to expand string patterns.
  • Exclamation mark: part of negation syntax with equals, not a standalone wildcard.

Why D is correct

D is correct because Splunk search language defines asterisk as the wildcard token for term expansion. It lets analysts match variants like pedia suffixes without enumerating every value. The other symbols perform comparison or negation and cannot substitute for pattern expansion.

Why the others are wrong

  • A. Equals asserts exact field equality and performs no wildcard expansion on its own.
  • B. Greater-than compares numeric or time ranges, it does not match partial strings broadly.
  • C. Exclamation participates in not-equals logic and is not a wildcard for Splunk searches.

SPLK-1001 exam tip

For SPLK-1001 wildcards, asterisk is the only answer; reserve equals and exclamation for exact and negation logic.

6What result will you get with following search index=test sourcetype="The_Questionnaire_P*" ?
  • the_questionnaire _pedia
  • the_questionnaire pedia
  • the_questionnaire_pedia
  • the_questionnaire Pedia
Answer: C

The short version

C — The wildcard sourcetype resolves to the_questionnaire_pedia. Quoted prefix plus star matches the underscored suffix exactly among the choices.

Key concepts in this question

  • Sourcetype filtering: constraining search to a data type such as questionnaire data for precise recall.
  • Quoted prefix with star: The_Questionnaire_P star expands only values beginning with that literal stem.
  • Underscore literal: an exact character that must be matched, distinguishing pedia with underscore from spaced variants.
  • Case handling in options: the settled match preserves the underscored lowercase pedia form shown in C.
  • Space versus underscore: spaced or mixed-case alternatives fail the literal pattern and are excluded.

Why C is correct

C is correct because the search index equals test plus sourcetype quoted prefix P star matches the indexed sourcetype the_questionnaire_pedia. The trailing star absorbs pedia after P while the underscore remains part of the stored value. Among the options only C reproduces that exact underscored form, confirming the settled key.

Why the others are wrong

  • A. A spaced pedia with leading gap breaks the underscore continuity required by the stored sourcetype.
  • B. A space-separated pedia similarly lacks the underscore and fails the literal prefix match.
  • D. Mixed spacing and capitalization does not equal the settled underscored sourcetype value.

SPLK-1001 exam tip

On SPLK-1001 sourcetype wildcards, match underscores literally and let star absorb only the trailing remainder.

7Prefix wildcards might cause performance issues.
  • False
  • True
Answer: B

The short version

B — True, leading wildcards risk serious search performance costs. Prefix star patterns prevent index pruning and force broad dictionary scans.

Key concepts in this question

  • Prefix wildcard: a search term beginning with star, such as star error, requiring suffix matching across terms.
  • Index optimization: Splunk uses term dictionaries to skip non-matching buckets when terms have known prefixes.
  • Performance impact: leading wildcards defeat that pruning, increasing I-O, CPU and latency on large indexes.
  • Best-practice guidance: Splunk docs advise avoiding leading wildcards or restricting them with filters and time bounds.
  • True-or-False test: the statement claims a performance hazard that documentation confirms.

Why B is correct

B is correct because Splunk must examine far more indexed terms when the start of the term is unknown. That scan expansion slows searches and can strain indexers, especially over long time ranges. Recognizing the cost guides authors toward rooted terms, tags or data-model acceleration instead.

Why the others are wrong

  • A. False is wrong because official guidance and field experience confirm leading wildcards degrade performance.

SPLK-1001 exam tip

For SPLK-1001 performance, memorize leading star equals slow; prefer rooted terms with time and index filters.

8Machine data can be in structured and unstructured format.
  • False
  • True
Answer: B

The short version

B — True, machine data spans structured and unstructured forms. Splunk ingests ordered logs plus free-form text with equal facility.

Key concepts in this question

  • Machine data: automatically generated records from servers, devices, apps and sensors across the estate.
  • Structured examples: JSON, CSV and key-value logs with predictable fields ready for direct extraction.
  • Unstructured examples: free-text messages, stack traces and syslog bodies requiring parsing at search time.
  • Schema-on-read: Splunk applies field extraction after ingestion, unifying both formats without upfront modeling.
  • Platform value: one pipeline for heterogeneous formats eliminates separate stores for each log style.

Why B is correct

B is correct because Splunk was built to onboard any machine-generated format, from neatly delimited files to raw event streams. Index-time segmentation plus search-time extraction handles both structured fields and unstructured prose. That dual coverage is why the statement is true under the settled key.

Why the others are wrong

  • A. False is wrong because limiting machine data to one format contradicts Splunk schema-on-read design.

SPLK-1001 exam tip

On SPLK-1001 concepts, link machine data to both structured and unstructured, linked by schema on read.

9Field names are case sensitive.
  • True
  • False
Answer: A

The short version

A — True, Splunk field names are case sensitive. Host versus host or Sourcetype versus sourcetype reference different identifiers in search.

Key concepts in this question

  • Field-name casing: exact-case matching required when writing searches, macros and calculated fields.
  • host versus Host example: lowercase host hits standard metadata while capitalized Host misses unless such a custom field exists.
  • Search precision benefit: case discipline prevents accidental conflation of distinct custom fields.
  • Value casing nuance: values may have their own case rules, but names themselves remain strictly case sensitive.
  • Troubleshooting hint: empty results often trace to miscapitalized field names rather than missing data.

Why A is correct

A is correct because Splunk search language treats field identifiers with case sensitivity. Using the wrong case addresses a non-existent field and returns no matches, as shown by the Host versus host distractor earlier. Honoring exact casing is therefore required for reliable searches.

Why the others are wrong

  • B. False is wrong because Splunk does not normalize field-name case, exact casing is enforced.

SPLK-1001 exam tip

For SPLK-1001 syntax, always copy field casing exactly; Host is not host in Splunk searches.

10Splunk internal fields contains general information about events and starts from underscore i.e. _ .
  • True
  • False
Answer: A

The short version

A — True, underscore-prefixed fields are Splunk internal metadata. Names starting with underscore carry event context such as time, index and source type.

Key concepts in this question

  • Internal fields: system-managed metadata describing each event provenance and processing state.
  • Underscore convention: leading underscore signals internal scope, for example _time, _index and _raw.
  • General event information: timestamps, host, source and storage location available without custom extraction.
  • Search usage: internal fields can filter and sort, though leading-underscore fields are hidden by default in display.
  • Custom-field contrast: user-extracted fields lack the prefix, distinguishing business data from platform metadata.

Why A is correct

A is correct because Splunk reserves the underscore prefix for internal fields containing general information about events. Documentation lists _time, _index, _source and related names as the standard internal set. That naming rule exactly matches the statement tested here.

Why the others are wrong

  • B. False is wrong because internal fields do start with underscore per Splunk field-naming conventions.

SPLK-1001 exam tip

Remember underscore equals internal on SPLK-1001: _time and _index are metadata, not custom extractions.

Want the full bank of 299 questions for Splunk Core Certified User (SPLK-1001)? See all practice exams.