Splunk Power User Practice Test

Splunk Certified Power User

Splunk Power User overview

  • 200 practice questions
  • 32 flashcards
  • 5 study guide topics
  • 39 key terms

What you'll study

  • Basic Searching and Search Under the Hood20%
  • Fields, Field Extraction, and Regular Expressions20%
  • Transforming Commands, Reports, and Dashboards20%
  • Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions20%
  • Data Models, Pivot, and Acceleration20%

The Splunk Certified Power User credential - often referred to as the Splunk Core Certified Power User - is a practitioner-level certification for people who already know how to run a basic search in Splunk and want to demonstrate that they can do real work with it. It sits above entry-level search knowledge and below the administrative and architect tracks, and it is aimed at SOC analysts, IT operations engineers, application support staff, developers, and business analysts whose daily work involves interrogating machine data. The skills it targets are practical: understanding how a search runs under the hood, creating and extracting fields, using regular expressions, applying transforming commands to produce reports and dashboards, and building knowledge objects such as tags, event types, lookups, and workflow actions. Data models, the Pivot interface, and acceleration also fall within scope. Typical preparation combines Splunk's own Power User elearning or instructor-led course, a lab instance where you can write and break searches freely, and repeated review of the published exam blueprint. Important caveat: when this page was built, Splunk's certification-track page for this exam returned a 404, so the exam parameters shown here - question count, duration, passing score, fee, retake policy, validity period, and domain weights - are unconfirmed and flagged for review. Verify them directly with Splunk Training and Certification before booking.

Common mistakes

Running a search without changing the time range picker, then concluding that events are missing or that a lookup/extraction 'doesn't work.'

Splunk Web defaults to a relative time range of Last 24 hours. Events outside that window never enter the pipeline, so the search looks broken even though the syntax is correct.

What to do instead

Before debugging syntax, explicitly set earliest/latest (for example earliest=-7d@d latest=now, or All time) and confirm the effective time range in the Job Inspector or the search's Time Range field. In dashboards, check whether the panel has its own time range that overrides the picker.

Putting a large or slow search inside square brackets as a subsearch and treating the output as complete and unfiltered.

Subsearches are silently capped at 10,000 results and roughly 60 seconds of runtime by default, and their output is injected into the outer search as an OR'd filter. Truncation produces quietly wrong result sets rather than errors.

What to do instead

Trim the subsearch to only the fields needed with fields/table, use return or format deliberately, and check the Job Inspector for subsearch truncation warnings. For large key sets, move the values into a CSV lookup and use | lookup instead.

Writing a rex expression with only a generic pattern such as rex "(?<user>\w+)" and expecting it to always capture the intended value.

The pattern has no surrounding literal context, so it matches the first token anywhere in _raw, and .* is greedy, so it over-consumes text. A single match is also returned by default, so multi-value cases are lost.

What to do instead

Anchor the pattern with the literal text that precedes the value, use non-greedy or character-class-restricted matching, and add max_match=0 when multiple values should be captured. Verify against sample events in the Field Extractor preview or with | regex before saving.

Building an extraction in the Field Extractor UI and assuming it will be visible to every user and every app.

Search-time extractions are written as knowledge objects in the app context where they were created and inherit that app's and role's permissions. Other apps and less-privileged roles will not see them until permissions are widened.

What to do instead

After creating the extraction, set the correct destination app and set object permissions (typically App-level or Global for shared use). Remember rex is inline and transient; only a saved extraction persists.

Using stats to compute a per-group value, then wondering why the original events and their fields are gone from the results.

stats is a transforming command: it replaces the result set with one row per group built from the aggregation functions. Candidates confuse it with eventstats (adds aggregates to each event) and streamstats (running aggregates).

What to do instead

Choose deliberately: stats to reduce to groups, eventstats to enrich each event with a group-level aggregate, streamstats for running/cumulative values in time order. Add sort before eventstats or streamstats where order matters.

Assuming the dashboard time range picker will control every panel's time range.

A panel whose search contains an explicit earliest/latest (or that is backed by a report with a fixed time range) ignores the dashboard picker. The panel then displays a static or stale window while the rest of the dashboard follows the picker.

What to do instead

Remove hard-coded earliest/latest from panel searches when the dashboard should drive time, and use the dashboard time range token instead. Verify by changing the dashboard picker and comparing panel results.

Tagging a field value and then assuming the tag can be used with any field, or assuming an event type filters events automatically once created.

A tag is attached to a specific field=value pair, so searching tag=xyz only returns events where that exact pairing occurred, not events where the value appeared in some other field. An event type is just a saved search string; it does no filtering until it is referenced with eventtype=.

What to do instead

Verify the tag exists on the intended field by running the field=value search first, then search tag= and compare counts. Reference event types explicitly in searches (eventtype=) and test the underlying search string before saving.

Confusing | lookup with | inputlookup, or building a lookup and finding it returns no matches for values that clearly exist in the CSV.

inputlookup reads the entire CSV as a result set; lookup enriches incoming events and needs a matching field name and correct definition/app permissions. Case differences between the event value and the CSV key, and missing or non-shared lookup definitions, silently produce no enrichment.

What to do instead

Use inputlookup to inspect the raw table and confirm exact key values, then use lookup for enrichment, naming the lookup definition explicitly. Check the definition's app context and permissions, field-name casing, and consider match type or default_match settings when values do not align exactly.

Using tstats or Pivot against a data model and getting empty or partial results, or expecting Pivot to expose every raw field.

Pivot requires the data model to be accelerated, and tstats only reports on fields defined within the data model. With summariesonly=t it returns only accelerated summaries, so if acceleration is disabled, still building, or the time range is not yet covered, results are empty or incomplete. Fields outside the model are never available.

What to do instead

Confirm acceleration status and coverage in the data model's settings, use | datamodel to inspect what is actually defined, and test with summariesonly=f to compare against raw. Only pivot on fields the model contains, and widen the time range or wait for the acceleration backfill to finish.

Placing a limiting command such as head or sort early in a pipeline and then aggregating, so the counts are computed over a truncated subset.

Commands execute left to right and each one receives only the results produced by the previous command. head 10 before stats count by host means only ten events are ever counted; the candidate reads the output as a full-population aggregate.

What to do instead

Order commands so filtering and aggregation happen over the full result set and limiting happens last (… | stats count by host | sort 10 - count). Read the pipeline as a sequence of transformations and verify intermediate row counts with a temporary | eventcount or | stats count between segments.

Exam requirements can change. Confirm current details with the exam provider.

Splunk Power User practice

200 questions. Each one lists the choices, the correct answer, and an explanation. With JavaScript, this list opens one question at a time. The checker at the top of this page saves progress in this browser when it is available.

  1. Question 1Basic Searching and Search Under the Hood

    If you run a search without specifying a time range, what range does Splunk apply?

    1. All time Correct answer.
    2. Last 60 minutes
    3. Last 24 hours
    4. Today

    Explanation

    A new search with no explicit time range defaults to All time, so Splunk considers every event it can read. Choosing a narrower range limits the buckets and events that must be scanned, which usually speeds the search up.

  2. Question 2Basic Searching and Search Under the Hood

    An inputs.conf stanza does not specify an index for its data. Which index receives that data by default?

    1. summary
    2. main Correct answer.
    3. default
    4. _internal

    Explanation

    When no index is named for incoming data, Splunk writes it to the main index. The summary index is used for summary-index output and _internal holds Splunk's own operational logs.

  3. Question 3Basic Searching and Search Under the Hood

    Which command produces a results table containing only the fields you name and lets you rename those fields with AS?

    1. eval
    2. rename
    3. table Correct answer.
    4. fields

    Explanation

    The table command selects the listed fields, sets the column order, and supports AS to rename columns in the output. The fields command also limits fields but has no AS renaming, while rename only changes field names.

  4. Question 4Basic Searching and Search Under the Hood

    What does the dedup command do?

    1. Removes events with duplicate field values Correct answer.
    2. Counts identical events and returns totals
    3. Sorts events by _time and drops the oldest
    4. Merges events that share a transaction ID

    Explanation

    dedup removes events whose values in the specified field (or fields) match an earlier event, keeping one representative event. With no field named it dedups on the full raw event. It does not sort, count, or merge events.

  5. Question 5Basic Searching and Search Under the Hood

    Which syntax sorts results from the highest value of the numeric field bytes to the lowest?

    1. sort - bytes Correct answer.
    2. sort bytes direction=desc
    3. sort desc bytes
    4. sort bytes desc

    Explanation

    A minus sign placed before a field name in sort reverses the default ascending order, giving descending order. The sort command has no desc keyword or direction argument.

  6. Question 6Basic Searching and Search Under the Hood

    Terms typed before the first pipe character of a search are passed to which command implicitly?

    1. eval
    2. where
    3. stats
    4. search Correct answer.

    Explanation

    The first segment of a search string is automatically treated as the argument of the search command, even though the word search is not typed. Later segments after a pipe must name their command explicitly.

  7. Question 7Basic Searching and Search Under the Hood

    Which field always holds the original text of an event exactly as it was indexed?

    1. _raw Correct answer.
    2. _indextime
    3. sourcetype
    4. _time

    Explanation

    _raw contains the unparsed event text as it was read at index time, and most search-time field extraction works from it. _time is the event timestamp, _indextime is when Splunk processed the event, and sourcetype is a classification value.

  8. Question 8Basic Searching and Search Under the Hood

    Which index contains Splunk's own internal logs and metrics?

    1. main
    2. _internal Correct answer.
    3. audit
    4. summary

    Explanation

    The _internal index stores Splunk's operational logs and metrics, which is why index=_internal searches reveal platform behaviour. main holds user data, summary holds summary-indexed results, and audit records administrative activity.

  9. Question 9Basic Searching and Search Under the Hood

    Which search is likely to run fastest when you only want a count of status=500 events per host?

    1. index=web | stats count by host status
    2. index=web | top host status
    3. index=web status=500 | stats count by host Correct answer.
    4. index=web | stats count by host | search status=500

    Explanation

    Placing the status=500 filter in the base search removes non-matching events before the transforming command runs, so stats processes far fewer events. Filtering early is the main lever for search performance.

  10. Question 10Basic Searching and Search Under the Hood

    Which statement best distinguishes top from stats count by?

    1. top cannot be used with a by clause
    2. top computes values across all events while stats only computes over a subset of events
    3. top only works on numeric fields
    4. top returns the N most common values plus a percent column Correct answer.

    Explanation

    top returns a limited number of the most frequent values (10 by default) and adds a percent column, which makes it a quick ranking tool. stats count by returns every group with counts and no percent column.

  11. Question 11Basic Searching and Search Under the Hood

    Which command removes the host field from the results while leaving every other field intact?

    1. dedup host
    2. fields - host Correct answer.
    3. table host
    4. rename host AS removed

    Explanation

    The fields command accepts a minus sign to exclude the named fields, keeping all others. table host would keep only host, dedup reduces events, and rename keeps the field under a new name.

  12. Question 12Basic Searching and Search Under the Hood

    What does the Search Job Inspector primarily show for a completed search?

    1. Execution costs per command and the search log Correct answer.
    2. The list of indexes the user is allowed to search
    3. The users who ran searches during the day
    4. The retention settings currently applied to each bucket

    Explanation

    The Job Inspector reports how long each command took, how many events each processed, messages, and the search log, which makes it the tool for diagnosing slow searches. It does not manage permissions or bucket retention.

  13. Question 13Basic Searching and Search Under the Hood

    What time window does earliest=-1d@d latest=now describe?

    1. Start of this week through now
    2. Start of yesterday through now Correct answer.
    3. Exactly the previous 24 hours
    4. Midnight today through now

    Explanation

    The relative modifier -1d moves back one day and @d then snaps to the beginning of that day, which is midnight yesterday. Without the @d snap you would get a rolling 24 hour window.

  14. Question 14Basic Searching and Search Under the Hood

    Which command extracts a new field from the raw event text using a search-time regular expression?

    1. lookup
    2. rex Correct answer.
    3. extract
    4. eval

    Explanation

    rex applies a named or inline regular expression to a field (by default _raw) and writes the captured groups into new fields. eval calculates values from existing fields, and lookup enriches events from a lookup table.

  15. Question 15Basic Searching and Search Under the Hood

    How does eventstats differ from stats?

    1. It requires a by clause
    2. It adds the aggregate value to each event Correct answer.
    3. It keeps only the aggregated rows
    4. It runs only on the indexer

    Explanation

    stats collapses events into one row per group, while eventstats computes the same aggregate and appends it to every original event, which preserves all events for later comparison. That is why eventstats output can be filtered again with search or where.

  16. Question 16Basic Searching and Search Under the Hood

    Which command groups related events that share a field value into single units using options such as maxspan and maxpause?

    1. stats
    2. dedup
    3. transaction Correct answer.
    4. append

    Explanation

    transaction joins events that share a value into one result, bounded by time constraints like maxspan and maxpause. stats aggregates values but does not merge events into single multi-event records.

  17. Question 17Basic Searching and Search Under the Hood

    Newly arriving data is written into which type of bucket, which is both writable and searchable?

    1. cold
    2. hot Correct answer.
    3. warm
    4. thawed

    Explanation

    Hot buckets are the active write targets and can be searched while they are being written. When a hot bucket rolls it becomes a read-only warm bucket, and cold buckets are read-only on slower storage.

  18. Question 18Basic Searching and Search Under the Hood

    What is the main effect of using a search term with a leading wildcard, such as *error?

    1. It limits the search to the last 24 hours
    2. It cannot use index terms and must examine many more events Correct answer.
    3. It uses the bloom filter to skip more buckets
    4. It automatically becomes case-insensitive

    Explanation

    Index terms are stored in a keyword index, so a term that begins with a wildcard has no usable prefix and cannot be resolved through those terms or the bloom filters. Splunk must instead scan far more events, which makes the search slow.

  19. Question 19Basic Searching and Search Under the Hood

    Which command filters events by evaluating a boolean expression built from eval functions, such as where like(field, "%foo%")?

    1. rex
    2. eval
    3. where Correct answer.
    4. search

    Explanation

    where accepts an eval-style expression and keeps only events for which it evaluates to true, which allows function-based comparisons that keyword search cannot express. eval instead writes the expression result into a field on every event.

  20. Question 20Basic Searching and Search Under the Hood

    What is the default maximum time a subsearch may run before Splunk stops it?

    1. 300 seconds
    2. 10 seconds
    3. 30 seconds
    4. 60 seconds Correct answer.

    Explanation

    Subsearches are capped at 60 seconds by default, after which results are finalized and the outer search continues with what was returned. They are also limited in the number of results they can return.

  21. Question 21Basic Searching and Search Under the Hood

    Which search returns events where the status field is either missing or set to something other than 200?

    1. index=web status NOT 200
    2. index=web status!=200
    3. index=web NOT status=200 Correct answer.
    4. index=web status=NOT 200

    Explanation

    The not-equal operator requires the field to exist and be unequal, so it silently drops events that lack the field. Negating an equality with NOT keeps those events as well, because a missing field satisfies the negation.

  22. Question 22Basic Searching and Search Under the Hood

    Which command reports on indexed fields using the tsidx files and does not read raw events?

    1. mstats
    2. stats
    3. tstats Correct answer.
    4. eventstats

    Explanation

    tstats queries the metadata stored in tsidx files for indexed fields, so it avoids reading raw events and returns results much faster than stats on large data. mstats is the equivalent command for metrics indexes.

  23. Question 23Basic Searching and Search Under the Hood

    You want dedup to keep the most recent event for each host value. Which search does that?

    1. index=main | dedup -host sortby +_time
    2. index=main | dedup host sortby -_time Correct answer.
    3. index=main | dedup host sortby _time
    4. index=main | dedup host

    Explanation

    dedup keeps the first event it encounters for each field value, so the retained event depends on the order at that point. sortby -_time orders the events newest first, which makes the newest event the one kept.

  24. Question 24Basic Searching and Search Under the Hood

    What lets Splunk skip entire buckets that cannot contain a search term?

    1. The timeline
    2. The transaction ledger
    3. The bloom filter stored in each bucket Correct answer.
    4. The summary index

    Explanation

    Each bucket carries a bloom filter that can prove a term is absent, letting the search head ignore that bucket without reading it. This bucket elimination, together with time range and index selection, is a primary reason narrow searches return quickly.

  25. Question 25Basic Searching and Search Under the Hood

    Which search returns one row per host and a separate column for each status value?

    1. index=web | chart count over host by status Correct answer.
    2. index=web | timechart count by host
    3. index=web | stats count by host status
    4. index=web | top host status

    Explanation

    chart count over host by status puts the values of host on the rows and the values of status into separate columns, which is the crosstab shape. stats count by host status returns one row per host-status pair instead.

  26. Question 26Basic Searching and Search Under the Hood

    When two search terms are separated only by a space in a Splunk search, which operator is applied implicitly?

    1. OR
    2. NOT
    3. AND Correct answer.
    4. XOR

    Explanation

    Splunk treats a space between two terms as an implicit AND, so every term must appear in the event for it to match. Writing the operator explicitly is optional but produces identical behavior. To widen results you must type OR between the terms yourself.

  27. Question 27Basic Searching and Search Under the Hood

    Which command returns only the first 10 results of a search when no argument is given?

    1. head Correct answer.
    2. sort
    3. tail
    4. top

    Explanation

    The head command limits results to the first N rows and defaults to 10 when no number is specified. It preserves the incoming event order rather than sorting. To keep more rows you supply a number, as in head 50.

  28. Question 28Basic Searching and Search Under the Hood

    Which search matches only events where the words connection refused appear together as a contiguous phrase?

    1. "connection refused" Correct answer.
    2. connection*refused
    3. connection OR refused
    4. connection AND refused

    Explanation

    Enclosing terms in double quotation marks tells Splunk to match them as a single phrase in the raw text rather than as separate tokens. Unquoted terms are joined with an implicit AND, which can match events where the words appear far apart. Quoted phrases are matched against the segmenter output for the event.

  29. Question 29Basic Searching and Search Under the Hood

    Which search mode is selected by default when you run a search in Splunk Web?

    1. Fast
    2. Verbose
    3. Debug
    4. Smart Correct answer.

    Explanation

    Smart mode is the default. It behaves like Fast mode for transforming searches and like Verbose mode for searches that return raw events, which balances speed against field availability. Users can switch modes from the search job settings.

  30. Question 30Basic Searching and Search Under the Hood

    A dashboard panel runs the search 'index=web earliest=-15m status=500' while the time range picker is set to Last 24 hours. Which time range does the search actually use?

    1. The overlap of the two ranges, which yields the last 15 minutes only when data exists
    2. The last 15 minutes Correct answer.
    3. A merged range that spans both settings, which yields the last 24 hours
    4. The last 24 hours, because the time range picker always overrides modifiers written into the search string

    Explanation

    Time modifiers placed directly in the search string take precedence over the time range picker for that search. The picker supplies a default range only when the search does not specify its own earliest or latest. Here the search string restricts results to the last 15 minutes.

  31. Question 31Basic Searching and Search Under the Hood

    Which statement correctly distinguishes the table command from the fields command?

    1. table and fields are interchangeable, because both permanently drop the raw event data from the results
    2. table keeps every event intact and only highlights the listed fields, while fields flattens the results so that each event becomes a row of a statistics table
    3. table outputs only the listed fields in a column layout, while fields keeps whole events and merely limits which fields are shown Correct answer.
    4. table sorts the results by the listed fields, while fields removes those fields from each event

    Explanation

    The table command converts results into a tabular output containing only the fields you list. The fields command keeps the events themselves and simply includes or excludes fields, which makes it a lighter-weight operation when you still want raw events. Neither command sorts the results.

  32. Question 32Basic Searching and Search Under the Hood

    Which stats function returns the number of distinct values of a field?

    1. values
    2. count
    3. dc Correct answer.
    4. sum

    Explanation

    The dc function counts distinct values of a field, for example dc(clientip) for unique visitors. The count function counts occurrences of events or of a field being present, including repeats. Distinct counts cannot be derived from a plain count when duplicates exist.

  33. Question 33Basic Searching and Search Under the Hood

    Which eval function returns the first of its arguments that is not null?

    1. if
    2. case
    3. nullif
    4. coalesce Correct answer.

    Explanation

    The coalesce function evaluates its arguments left to right and returns the first non-null value, which is useful for filling gaps between alternative fields. It accepts any number of arguments. The if and case functions choose between values based on conditions rather than on null status.

  34. Question 34Basic Searching and Search Under the Hood

    Which search orders results by the count field from highest to lowest?

    1. index=web | stats count by host | sort - count Correct answer.
    2. index=web | stats count by host | sort count
    3. index=web | stats count by host | sort + count
    4. index=web | stats count by host | sort count desc

    Explanation

    The sort command reverses direction when a field name is preceded by a minus sign, so sort - count gives descending order. A plus sign or no sign gives ascending order. The sort command does not accept the desc keyword used by SQL.

  35. Question 35Basic Searching and Search Under the Hood

    In a distributed deployment, which component receives the search, sends it to the indexers, and merges their results?

    1. The license manager
    2. The indexer cluster manager node
    3. The search head Correct answer.
    4. The universal forwarder

    Explanation

    The search head is responsible for parsing and distributing the search and for merging the partial results returned by indexers. Indexers perform the raw-event retrieval and much of the per-bucket work. Forwarders only collect and send data to indexers.

  36. Question 36Basic Searching and Search Under the Hood

    Which command appends the fields returned by a subsearch as new columns on the current results?

    1. appendcols Correct answer.
    2. format
    3. join
    4. append

    Explanation

    The appendcols command runs a subsearch and attaches its output fields as additional columns to the existing rows, matching them by position rather than by a shared key. The append command adds the subsearch output as extra rows instead. Use join when you need matching on a common field.

  37. Question 37Basic Searching and Search Under the Hood

    You have a CSV file of host-to-owner mappings. Which command adds an owner field to each event by matching on the host field?

    1. lookup Correct answer.
    2. join
    3. inputlookup
    4. outputlookup

    Explanation

    The lookup command enriches events with fields from a lookup table such as a CSV, matching on one or more fields by default. The table must already be defined or referenced as a lookup definition. inputlookup and outputlookup work with the lookup table as a data source or destination and do not enrich event results.

  38. Question 38Basic Searching and Search Under the Hood

    By default, how many results can a subsearch return before Splunk truncates its output?

    1. 10,500 Correct answer.
    2. 1,000
    3. 50,000
    4. Unlimited

    Explanation

    Subsearch results are capped at 10,500 rows by default, and Splunk adds a message to the job when this limit is reached. The cap exists because subsearch output is rewritten into the parent search string, so unbounded output would make the search unmanageable. Large subsearches should usually be restructured or replaced with lookup or stats-based approaches.

  39. Question 39Basic Searching and Search Under the Hood

    What happens when a hot bucket reaches its maximum size?

    1. It is deleted to free space
    2. It is rolled to warm and a new hot bucket is created Correct answer.
    3. It is converted into a frozen bucket and removed from the index immediately
    4. Its events are re-indexed into the default index and the bucket file is removed

    Explanation

    A hot bucket is the writable, searchable bucket that receives new data. When it grows past its size limit it is rolled: it becomes a warm bucket and a fresh hot bucket is opened for incoming events. Warm buckets remain searchable but are no longer written to.

  40. Question 40Basic Searching and Search Under the Hood

    Which command adds a cumulative running total to each event, keeping every event in the results, without collapsing them into a single row?

    1. streamstats Correct answer.
    2. transaction
    3. eventstats
    4. stats

    Explanation

    streamstats computes aggregates incrementally as events stream through and writes the running value onto each event, so the event count is preserved. eventstats also keeps events but computes a single non-cumulative value over the whole result set. stats reduces the result set to one row per group.

  41. Question 41Fields, Field Extraction, and Regular Expressions

    Which set of fields does Splunk automatically add to every event, regardless of sourcetype?

    1. user, action, and status
    2. timestamp, message, and severity
    3. host, source, and sourcetype Correct answer.
    4. src, dest, and port

    Explanation

    Splunk assigns host, source, and sourcetype to events as they are indexed, so these metadata fields are available for every event. Fields such as user or status exist only when they are extracted or explicitly added.

  42. Question 42Fields, Field Extraction, and Regular Expressions

    Which command narrows search results to only the fields you name and is preferred over table when you do not need column formatting?

    1. eval
    2. rename
    3. fields Correct answer.
    4. dedup

    Explanation

    The fields command includes or excludes fields and is optimized for that purpose. Use table only when you also need to control column order or tabular formatting.

  43. Question 43Fields, Field Extraction, and Regular Expressions

    Which command returns results as a table with columns in the exact order listed in the command?

    1. stats
    2. sort
    3. fields
    4. table Correct answer.

    Explanation

    The table command returns a table whose columns follow the order in which the fields are listed. The fields command also selects fields but does not apply table column formatting.

  44. Question 44Fields, Field Extraction, and Regular Expressions

    Which rex expression extracts a value into a field named user?

    1. rex "(?<user>\w+)" Correct answer.
    2. rex "(<user>\w+)"
    3. rex "(?P<user>\w+)"
    4. rex "($user\w+)"

    Explanation

    Named capture groups in Splunk regular expressions use the syntax (?<name>pattern). The group name is placed in angle brackets immediately after a question mark.

  45. Question 45Fields, Field Extraction, and Regular Expressions

    Which command renames the field clientip to src_ip?

    1. eval src_ip=clientip
    2. rename clientip AS src_ip Correct answer.
    3. rename src_ip=clientip
    4. fields clientip AS src_ip

    Explanation

    The rename command uses the syntax rename <old> AS <new>. It changes the field name without recalculating values.

  46. Question 46Fields, Field Extraction, and Regular Expressions

    A field created with the rex command during a search is available:

    1. only to members of the admin role
    2. only after the search is saved as a report
    3. only within that search's results Correct answer.
    4. to all users after the search completes

    Explanation

    Fields created by rex exist only in the results of the current search. To make an extraction persistent, you must define it in configuration or save it as part of a knowledge object.

  47. Question 47Fields, Field Extraction, and Regular Expressions

    Which command creates a new field by calculating a value from existing fields?

    1. sort
    2. table
    3. eval Correct answer.
    4. dedup

    Explanation

    The eval command calculates values and adds a new field to each result. It is the standard command for creating calculated fields.

  48. Question 48Fields, Field Extraction, and Regular Expressions

    When no field argument is given, the rex command applies its pattern to which field?

    1. _raw Correct answer.
    2. host
    3. _time
    4. sourcetype

    Explanation

    rex searches the _raw field by default. Use the field argument to apply the pattern to a different field.

  49. Question 49Fields, Field Extraction, and Regular Expressions

    An event contains user=alice;role=admin;dept=ops. Which command extracts these pairs using a semicolon between pairs and an equals sign between each key and value?

    1. extract pairdelim="=" kvdelim=";"
    2. rex pairdelim=";" kvdelim="="
    3. extract pairdelim=";" kvdelim="=" Correct answer.
    4. extract kvdelim=";" delim="="

    Explanation

    The extract command uses pairdelim for the delimiter between key-value pairs and kvdelim for the delimiter between a key and its value. Here pairs are separated by semicolons and keys from values by equals signs.

  50. Question 50Fields, Field Extraction, and Regular Expressions

    Which statement describes the fieldformat command?

    1. It changes the underlying value of a field for later commands.
    2. It changes how a field value is displayed without changing the value used by subsequent commands. Correct answer.
    3. It renames a field and removes the original field.
    4. It permanently extracts a new field at index time.

    Explanation

    fieldformat changes only the display representation of a value; subsequent commands still see the original value. Use eval when the calculated value itself must change.

  51. Question 51Fields, Field Extraction, and Regular Expressions

    Given the fields a, b, and c, which expression returns the first non-null value among them?

    1. eval first=if(a,b,c)
    2. eval first=mvfind(a,b,c)
    3. eval first=coalesce(a,b,c) Correct answer.
    4. eval first=a+b+c

    Explanation

    The coalesce function returns its first argument that is not null, making it the standard way to merge fallback fields. The if function requires a boolean condition and two result values.

  52. Question 52Fields, Field Extraction, and Regular Expressions

    Which command replaces null values in all fields with 0?

    1. replace null WITH 0
    2. fillnull 0
    3. fillnull value=0 Correct answer.
    4. eval *=0

    Explanation

    fillnull uses the syntax fillnull value=<string> to replace null values, and it applies to all fields unless a field list is provided. The bare form fillnull 0 is not a valid value assignment.

  53. Question 53Fields, Field Extraction, and Regular Expressions

    The search ... | dedup user returns:

    1. only events where user appears exactly once
    2. the first event for each distinct value of user Correct answer.
    3. the last event for each distinct value of user
    4. all events, with duplicate users removed from the user field only

    Explanation

    dedup with a field list keeps the first event for each distinct combination of values and drops subsequent events with the same values. The first occurrence is kept unless the sort order or keeplast option changes it.

  54. Question 54Fields, Field Extraction, and Regular Expressions

    Which command filters results to events whose _raw field matches a regular expression?

    1. regex Correct answer.
    2. match
    3. searchmatch
    4. rex

    Explanation

    The regex command filters events by matching a pattern against a field, using _raw by default. rex is used to extract new fields from a pattern match rather than only filter events.

  55. Question 55Fields, Field Extraction, and Regular Expressions

    Which command extracts fields from a JSON event?

    1. spath Correct answer.
    2. json
    3. kv
    4. xmlkv

    Explanation

    spath extracts fields from structured JSON and XML data and can navigate nested objects and arrays. It is the standard command for explicit structured-data extraction.

  56. Question 56Fields, Field Extraction, and Regular Expressions

    Which command extracts fields from events that contain tabular text, such as output copied from a table?

    1. multikv Correct answer.
    2. table
    3. extract
    4. spath

    Explanation

    multikv parses tabular event text by using header and row information within the event. It is designed for events that contain multiple rows of column-aligned data.

  57. Question 57Fields, Field Extraction, and Regular Expressions

    Which search returns only events where status is exactly the uppercase string OK, excluding events with ok or Ok?

    1. status=OK
    2. status::OK Correct answer.
    3. status="OK"
    4. status==OK

    Explanation

    The :: operator forces case-sensitive matching on a field value, while the normal = comparison is case-insensitive. Quoting a value does not make the comparison case-sensitive.

  58. Question 58Fields, Field Extraction, and Regular Expressions

    Which search compares the value of the bytes field against the value of the bytes_out field?

    1. where bytes > bytes_out Correct answer.
    2. filter bytes > bytes_out
    3. eval bytes > bytes_out
    4. search bytes > bytes_out

    Explanation

    The where command evaluates expressions and can compare two fields directly. The search command treats bare terms literally and does not perform field-to-field comparisons.

  59. Question 59Fields, Field Extraction, and Regular Expressions

    Which search keeps all fields whose names begin with user_?

    1. fields user_* Correct answer.
    2. fields user_+
    3. fields user_?
    4. fields user_%

    Explanation

    The fields command accepts the asterisk as a wildcard in field names, so fields user_* keeps every field starting with user_. The other symbols are not field-name wildcards in Splunk.

  60. Question 60Fields, Field Extraction, and Regular Expressions

    Which rex option causes every match in the field to be returned as a multivalue field?

    1. all=true
    2. mv=1
    3. max_match=0 Correct answer.
    4. max_match=1

    Explanation

    Setting max_match=0 removes the limit on the number of matches and returns all matches as a multivalue field. The default max_match=1 returns only the first match.

  61. Question 61Fields, Field Extraction, and Regular Expressions

    Which search removes the string ID: from every occurrence in the msg field?

    1. rex field=msg "s/ID://g"
    2. eval msg=sed(msg,"ID:","")
    3. rex field=msg mode=sed "s/ID://g" Correct answer.
    4. replace msg "ID:"

    Explanation

    rex with mode=sed applies a sed-style substitution to the field value instead of extracting a new field. The s/old/new/g form replaces every occurrence.

  62. Question 62Fields, Field Extraction, and Regular Expressions

    Which regular expression matches error or warning only when either appears as a whole word?

    1. error|warning
    2. (error|warning)
    3. \b(error|warning)\b Correct answer.
    4. [error|warning]

    Explanation

    \b marks a word boundary, so \b(error|warning)\b matches those words only when they stand alone. The parentheses keep the alternation together so the boundary applies to either word.

  63. Question 63Fields, Field Extraction, and Regular Expressions

    What is the erex command used for?

    1. It extracts all key-value pairs from the _raw field.
    2. It runs an existing regular expression against events and filters matches.
    3. It replaces matched text using sed substitution syntax.
    4. It generates a regular expression from example field values that you provide. Correct answer.

    Explanation

    erex helps build a regular expression by generating candidate patterns from example values you supply. You then review and refine the generated expression before using it for extraction.

  64. Question 64Fields, Field Extraction, and Regular Expressions

    Which regular expression captures everything before the first comma in the field value, excluding the comma itself?

    1. (?<val>.+),
    2. (?<val>[^,]*,)
    3. (?<val>[^,]*) Correct answer.
    4. (?<val>.*)

    Explanation

    [^,]* matches a run of characters that are not commas, so the group stops before the first comma. A greedy .* would consume through the last comma instead.

  65. Question 65Fields, Field Extraction, and Regular Expressions

    Which props.conf setting defines an inline search-time field extraction using a regular expression?

    1. REPORT-foo
    2. FIELDALIAS-foo
    3. EXTRACT-foo Correct answer.
    4. TRANSFORMS-foo

    Explanation

    Search-time inline regular expression extractions in props.conf use stanza names beginning with EXTRACT-. REPORT- is used for transform-based extractions that reference entries in transforms.conf.

  66. Question 66Fields, Field Extraction, and Regular Expressions

    Which command returns results containing only the fields you name, displayed in the exact order you list them?

    1. fields
    2. table Correct answer.
    3. dedup
    4. rename

    Explanation

    The table command keeps only the fields named as arguments and controls the left-to-right column order of the output. The fields command also selects fields but does not guarantee a display order and is typically used to include or exclude fields for performance.

  67. Question 67Fields, Field Extraction, and Regular Expressions

    Which field stores the original, unprocessed text of each event exactly as it was indexed?

    1. _time
    2. linecount
    3. sourcetype
    4. _raw Correct answer.

    Explanation

    The _raw field holds the complete event text before any field extraction takes place, which is why search-time extractions run against it by default. Other default fields such as _time, host, source and sourcetype describe the event rather than contain its body.

  68. Question 68Fields, Field Extraction, and Regular Expressions

    Which command converts a single-value field that contains a delimiter into a multivalue field?

    1. mvcount
    2. makemv Correct answer.
    3. nomv
    4. mvexpand

    Explanation

    The makemv command splits the values of a single field on a delimiter (whitespace by default) and stores the pieces as multiple values of the same field. Use the delim argument to specify a delimiter other than whitespace.

  69. Question 69Fields, Field Extraction, and Regular Expressions

    Which command changes the name of a field in the search results without altering the underlying indexed data?

    1. table
    2. replace
    3. eval
    4. rename Correct answer.

    Explanation

    The rename command changes how a field is labeled in the current results only, leaving the indexed data untouched. It can rename one field or several fields in a single command using comma-separated pairs.

  70. Question 70Fields, Field Extraction, and Regular Expressions

    Which props.conf attribute gives an existing field an alternate name that searches can use at search time?

    1. REPORT-<name>
    2. EXTRACT-<name>
    3. FIELDALIAS-<name> Correct answer.
    4. LOOKUP-<name>

    Explanation

    FIELDALIAS stanzas map a new name onto an existing field using the syntax <existing_field> AS <new_name>, and the alias is applied at search time. This lets searches written for one naming convention work against data that uses another.

  71. Question 71Fields, Field Extraction, and Regular Expressions

    Which props.conf setting on a sourcetype causes Splunk to automatically extract fields from JSON-formatted events at search time?

    1. LINE_BREAKER = json
    2. KV_MODE = json Correct answer.
    3. SHOULD_LINEMERGE = true
    4. INDEXED_EXTRACTIONS = json

    Explanation

    Setting KV_MODE to json performs key-value field extraction from JSON structures at search time, leaving _raw intact. INDEXED_EXTRACTIONS = json is a different setting that extracts JSON fields at index time.

  72. Question 72Fields, Field Extraction, and Regular Expressions

    Which regular expression matches a value such as 85 or 85%, requiring at least one digit and allowing an optional trailing percent sign?

    1. [0-9]%
    2. \d+%? Correct answer.
    3. \d*%+
    4. \d?%*

    Explanation

    \d+ requires one or more digits and the ? quantifier makes the percent sign optional, so both 85 and 85% match. Quantifiers apply only to the element immediately preceding them.

  73. Question 73Fields, Field Extraction, and Regular Expressions

    Which statement about field names and field values in Splunk searches is accurate?

    1. Both field names and field values are case insensitive.
    2. Field names are case sensitive; field values are not. Correct answer.
    3. Both field names and field values are case sensitive.
    4. Field names are case insensitive; field values are not.

    Explanation

    Field names must be referenced with the exact capitalization used when the field was created, so User and user are different fields. Field values, by contrast, are matched case-insensitively in ordinary search terms unless a case-sensitive function or option is used.

  74. Question 74Fields, Field Extraction, and Regular Expressions

    Which eval function evaluates a list of condition-and-result pairs and returns the result belonging to the first condition that evaluates to true?

    1. coalesce
    2. if
    3. case Correct answer.
    4. validate

    Explanation

    case takes pairs of arguments in the form condition, result and returns the result paired with the first condition that evaluates to true. The if function evaluates only a single condition and then chooses between two results.

  75. Question 75Fields, Field Extraction, and Regular Expressions

    Which command adds fields to your events by matching a field value against a CSV file?

    1. join
    2. inputlookup
    3. outputlookup
    4. lookup Correct answer.

    Explanation

    The lookup command enriches each event with fields from the lookup table whose key column matches the specified field value. It is a search-time enrichment and does not modify the indexed data.

  76. Question 76Fields, Field Extraction, and Regular Expressions

    Which props.conf attribute creates a new field at search time by evaluating an expression instead of matching a regular expression?

    1. EVAL-<name> Correct answer.
    2. LOOKUP-<name>
    3. REPORT-<name>
    4. TRANSFORMS-<name>

    Explanation

    EVAL-<fieldname> takes an eval expression as its value and creates or overwrites that field whenever events from the stanza are searched. It is the calculated-field mechanism and does not depend on any regex pattern.

  77. Question 77Fields, Field Extraction, and Regular Expressions

    Which eval function returns the number of values held by a multivalue field?

    1. mvfilter
    2. mvcount Correct answer.
    3. mvindex
    4. mvjoin

    Explanation

    mvcount accepts a field and returns the count of values it contains, which is useful for testing whether a field is multivalue. It is often paired with where clauses such as mvcount(field)>1.

  78. Question 78Fields, Field Extraction, and Regular Expressions

    Which regular expression construct asserts that a specified pattern must appear immediately ahead without consuming any characters?

    1. (?=...) Correct answer.
    2. (?!...)
    3. (?:...)
    4. (?#...)

    Explanation

    A positive lookahead (?=...) tests that the following text matches the pattern but does not include those characters in the overall match. This is useful when you need to constrain a match without extracting the lookahead text.

  79. Question 79Fields, Field Extraction, and Regular Expressions

    An event contains the text a=1;b=2;c=3. Which rex expression extracts a field named val whose value is exactly 1?

    1. | rex "a=(?<val>\S+)"
    2. | rex "b=(?<val>[^;=]+)"
    3. | rex "(?<val>[^=]+)"
    4. | rex "a=(?<val>[^;]+)" Correct answer.

    Explanation

    A negated character class such as [^;]+ consumes characters until the next semicolon, and the pattern is anchored on the literal a=, so only the digits 1 are captured. Greedy wildcards that are not limited to a stopping character run past the delimiter.

  80. Question 80Fields, Field Extraction, and Regular Expressions

    Which rex mode replaces text that matches the pattern instead of extracting a new field from it?

    1. mode=replace
    2. mode=sed Correct answer.
    3. mode=filter
    4. mode=extract

    Explanation

    The rex command accepts mode=sed, which applies a sed-style substitution expression such as s/ID://g to the values of a field and writes the modified value back. The other mode accepted by rex is break, which terminates the extraction after the first match.

  81. Question 81Transforming Commands, Reports, and Dashboards

    Which command groups events by one or more fields and calculates aggregate values such as count, sum, and average?

    1. stats Correct answer.
    2. table
    3. eval
    4. rex

    Explanation

    The stats command transforms the result set into a table of aggregates, with one row per distinct combination of the BY-clause fields. It replaces the individual events with those summarized rows.

  82. Question 82Transforming Commands, Reports, and Dashboards

    Which command returns the most frequent values of a field together with their count and percentage?

    1. dedup
    2. sort
    3. rare
    4. top Correct answer.

    Explanation

    top ranks field values by frequency and reports count and percent for each. By default it returns only the most common values.

  83. Question 83Transforming Commands, Reports, and Dashboards

    Which command orders search results by one or more fields in ascending or descending order?

    1. arrange
    2. order
    3. sort Correct answer.
    4. rank

    Explanation

    sort arranges results by the listed fields, ascending by default; a minus sign before a field sorts it descending. Adding limit=0 keeps all results rather than the default 10,000.

  84. Question 84Transforming Commands, Reports, and Dashboards

    Which command returns a results table containing only the listed fields, displayed in the order listed?

    1. table Correct answer.
    2. dedup
    3. fields
    4. rename

    Explanation

    table outputs the specified fields as columns in the order given and drops all other fields. The fields command also selects fields but does not control column order.

  85. Question 85Transforming Commands, Reports, and Dashboards

    Which command removes duplicate results based on the values of a specified field?

    1. uniq
    2. dedup Correct answer.
    3. distinct
    4. cluster

    Explanation

    dedup keeps the first occurrence of each distinct value of the named field and removes later duplicates. Adding sortby changes which event is kept.

  86. Question 86Transforming Commands, Reports, and Dashboards

    Which command builds a table in which rows are values of one field, columns are values of another field, and each cell holds an aggregate?

    1. stats
    2. timechart
    3. xyseries
    4. chart Correct answer.

    Explanation

    chart uses an OVER clause for rows and a BY clause for columns, placing the aggregate in each cell. timechart is the time-oriented variant that always puts time on the x-axis.

  87. Question 87Transforming Commands, Reports, and Dashboards

    Which eval function returns the current date and time?

    1. strftime
    2. now Correct answer.
    3. time
    4. relative_time

    Explanation

    now() returns the current epoch time, which can then be formatted with strftime. relative_time returns a timestamp shifted by a relative offset.

  88. Question 88Transforming Commands, Reports, and Dashboards

    Which command changes the name of a field in the search results?

    1. rename Correct answer.
    2. alias
    3. as
    4. fieldformat

    Explanation

    rename changes field names and can rename several fields in one clause using wildcards. It does not alter the field values.

  89. Question 89Transforming Commands, Reports, and Dashboards

    A search returns individual events, and the analyst wants every event to also show the average duration for its host without removing any events. Which search accomplishes this?

    1. eventstats avg(duration) BY host Correct answer.
    2. stats avg(duration) BY host
    3. top duration BY host
    4. streamstats avg(duration) BY host

    Explanation

    eventstats computes aggregates and appends them to every event as a new field while leaving the events intact. stats would instead replace the events with one row per host.

  90. Question 90Transforming Commands, Reports, and Dashboards

    Which command computes a running average of a numeric field as events are processed in order?

    1. stats avg(bytes) BY host
    2. eventstats avg(bytes) BY host
    3. streamstats avg(bytes) Correct answer.
    4. accum bytes

    Explanation

    streamstats calculates aggregates incrementally over the events processed so far and adds the result to each event. This makes it suited to running totals and running averages.

  91. Question 91Transforming Commands, Reports, and Dashboards

    Which command filters results using eval expressions and can compare two fields to each other?

    1. filter
    2. regex
    3. search
    4. where Correct answer.

    Explanation

    where evaluates an eval expression for each result and keeps rows where the expression is true, so comparisons such as where bytes > avg_bytes work. search compares field values to literal terms rather than to other fields.

  92. Question 92Transforming Commands, Reports, and Dashboards

    Which command groups related events that share a field value into a single result that includes the duration between the first and last event?

    1. transaction field Correct answer.
    2. collect index=summary
    3. stats count BY field
    4. group field

    Explanation

    transaction merges related events into one result with fields such as duration and eventcount. Its grouping can be refined with startswith and endswith options.

  93. Question 93Transforming Commands, Reports, and Dashboards

    Which command groups numeric values into discrete ranges or buckets for summarization?

    1. bin Correct answer.
    2. group
    3. segment
    4. collect

    Explanation

    bin places numeric values into ranges of a chosen span, which is often done before stats to summarize ranges. It is also used with time to create time buckets.

  94. Question 94Transforming Commands, Reports, and Dashboards

    Which command extracts new fields from raw event text using a regular expression with named capture groups?

    1. rex Correct answer.
    2. extract
    3. eval
    4. regex

    Explanation

    rex applies a regular expression to a field and creates new fields from named groups such as (?<status>\d+). The regex command filters events rather than creating fields.

  95. Question 95Transforming Commands, Reports, and Dashboards

    Which command adds a field showing the difference between the current value of a numeric field and its previous value?

    1. accum
    2. diff
    3. delta Correct answer.
    4. trendline

    Explanation

    delta calculates the difference between consecutive values of a field, optionally grouped with a BY clause. accum instead adds a cumulative total.

  96. Question 96Transforming Commands, Reports, and Dashboards

    Which command replaces null values in specified fields with a default value?

    1. eval
    2. coalesce()
    3. fillnull Correct answer.
    4. replace

    Explanation

    fillnull substitutes a value, 0 by default, wherever the listed fields are null. The coalesce eval function can do something similar but only inside an eval expression.

  97. Question 97Transforming Commands, Reports, and Dashboards

    Which command adds the results of a subsearch as new columns to the right of the current results?

    1. union
    2. join
    3. append with a subsearch
    4. appendcols Correct answer.

    Explanation

    appendcols runs a subsearch and attaches its fields as additional columns, matching results row by row. append instead adds the subsearch results as additional rows.

  98. Question 98Transforming Commands, Reports, and Dashboards

    Which command enriches events by matching field values against a CSV file and adding fields from that file?

    1. join
    2. eval
    3. inputlookup
    4. lookup Correct answer.

    Explanation

    lookup matches an event field to a lookup table and returns the configured output fields. inputlookup instead reads the lookup file as search results.

  99. Question 99Transforming Commands, Reports, and Dashboards

    In a timechart, which argument sets the width of each time bucket on the x-axis?

    1. bins
    2. interval
    3. span Correct answer.
    4. granularity

    Explanation

    span controls the time width of each bucket, for example span=5m. The bin command creates buckets in general searches, but in timechart the argument is span.

  100. Question 100Transforming Commands, Reports, and Dashboards

    A dashboard has a base search, and a panel runs a smaller search on the base search results without executing the base search again. What is this smaller search called?

    1. drilldown search
    2. post-process search Correct answer.
    3. subsearch
    4. acceleration summary search

    Explanation

    A post-process search reuses the results of a base search and applies additional filtering and aggregation, which reduces load on the search head. It is configured on the panel that references the base search.

  101. Question 101Transforming Commands, Reports, and Dashboards

    Which command runs a statistical search directly against an accelerated data model and returns results without running a raw search?

    1. tstats Correct answer.
    2. collect
    3. pivot
    4. datamodel

    Explanation

    tstats queries indexed fields and data model acceleration summaries, making statistical searches much faster than raw event searches. Acceleration must be enabled on the data model for the summaries to exist.

  102. Question 102Transforming Commands, Reports, and Dashboards

    A search returns rows with fields _time, host, and count. Which command turns host values into separate columns so each row is a time and each column is a host?

    1. xyseries Correct answer.
    2. transpose
    3. untable
    4. chart

    Explanation

    xyseries takes x, y, and value fields and pivots the y values into columns, which is the standard way to reshape already aggregated results. untable performs the reverse transformation.

  103. Question 103Transforming Commands, Reports, and Dashboards

    A dashboard panel must let a user click a table row and pass that row's host value to another panel as a token. Which dashboard feature provides this?

    1. post-process
    2. drilldown Correct answer.
    3. intent
    4. token binding

    Explanation

    Drilldown defines what happens when a user clicks a panel value, including setting tokens from the clicked row for other panels to use. Those tokens are then referenced in other searches with $token$ syntax.

  104. Question 104Transforming Commands, Reports, and Dashboards

    Which command changes how a field's values are displayed without changing the underlying values used in calculations?

    1. replace, which substitutes matching strings
    2. eval, which changes the stored value
    3. fieldformat, which changes display only Correct answer.
    4. convert, which changes the data type

    Explanation

    fieldformat applies formatting to a field for display while leaving the original value intact for later calculations. eval, by contrast, creates or overwrites actual field values.

  105. Question 105Transforming Commands, Reports, and Dashboards

    Which statement describes what report acceleration does?

    1. It builds an index of the fields used by the report so the report runs faster. Correct answer.
    2. It caches each dashboard panel's results separately for every user.
    3. It schedules the report and emails the results to a list of recipients.
    4. It stores the full report results in a summary index that other searches can read.

    Explanation

    Report acceleration creates and maintains a high-performance index of the fields used by the report, which speeds up later runs of that same report. It does not store the finished report output.

  106. Question 106Transforming Commands, Reports, and Dashboards

    Which command groups results by the values of a field and returns the most frequent of those values along with a count and a percentage for each?

    1. dedup
    2. rare
    3. stats
    4. top Correct answer.

    Explanation

    The top command summarizes events by a field and returns the most common values, showing a count and a percent column for each by default. It returns ten values unless a limit is supplied. Using rare instead reverses the selection and returns the least common values.

  107. Question 107Transforming Commands, Reports, and Dashboards

    Which command removes results that share the same value of a specified field, keeping only the first result for each distinct value?

    1. dedup Correct answer.
    2. cluster
    3. stats
    4. uniq

    Explanation

    dedup compares the values of the fields it is given and retains only the first result for each distinct combination, which reduces a result set to one row per value. It can be limited to a number of duplicates to keep and can sort by another field first to control which result survives.

  108. Question 108Transforming Commands, Reports, and Dashboards

    Which syntax sorts results from the highest to the lowest value of a numeric field named bytes?

    1. sort by bytes descending
    2. reverse bytes
    3. sort bytes desc
    4. sort - bytes Correct answer.

    Explanation

    A leading minus sign placed before the field name reverses the default ascending order, so sort - bytes produces descending order. Multiple fields can be listed, each with its own leading minus sign where descending order is wanted.

  109. Question 109Transforming Commands, Reports, and Dashboards

    Which command returns only the named fields, in the order listed, as a set of columns?

    1. rex
    2. fields
    3. rename
    4. table Correct answer.

    Explanation

    The table command keeps only the fields it is given and returns them in the order specified, producing a columnar output; it also accepts wildcards. The fields command also removes unlisted fields but preserves the original order and does not impose a column layout.

  110. Question 110Transforming Commands, Reports, and Dashboards

    Which command appends a new column containing the sum of the numeric fields within each individual row of results?

    1. addtotals Correct answer.
    2. addcoltotals
    3. stats sum
    4. accum

    Explanation

    addtotals calculates a row-wise total across the numeric fields present in each result and adds it as a new column, named Total by default. It can be limited to specific fields and can also be told to label the column differently.

  111. Question 111Transforming Commands, Reports, and Dashboards

    Which eval function evaluates several condition and value pairs and returns the value paired with the first condition that is true?

    1. case Correct answer.
    2. if
    3. coalesce
    4. validate

    Explanation

    case accepts alternating boolean expressions and output values and returns the value belonging to the first expression that evaluates to true, making it the standard choice for multi-branch logic. A final true condition can be used as a catch-all for unmatched events.

  112. Question 112Transforming Commands, Reports, and Dashboards

    A field named user holds several values within a single event. Which command produces one separate result for each value of that field?

    1. nomv
    2. mvcombine
    3. mvexpand Correct answer.
    4. mvcount

    Explanation

    mvexpand takes a multivalued field and emits one copy of the event per value, so downstream commands such as stats can count each value separately. It should be used carefully because it multiplies the number of results.

  113. Question 113Transforming Commands, Reports, and Dashboards

    Which command adds the results of a subsearch as additional rows beneath the results of the outer search?

    1. lookup
    2. join
    3. append Correct answer.
    4. appendcols

    Explanation

    append runs a subsearch and places its results after the outer search results as extra rows, which is useful when two searches return comparable fields that should be reviewed together. The outer search results are not modified or reordered.

  114. Question 114Transforming Commands, Reports, and Dashboards

    Which stats function returns every value of a field as a multivalued field, including duplicate values?

    1. collect
    2. list Correct answer.
    3. values
    4. mvappend

    Explanation

    list keeps all values found in each group in the order they were encountered, so repeated values remain in the multivalued result. The values function instead returns only distinct values and sorts them.

  115. Question 115Transforming Commands, Reports, and Dashboards

    Which stats function returns the number of distinct values that a field contains within each group?

    1. distinct
    2. count
    3. values
    4. dc Correct answer.

    Explanation

    dc, short for distinct count, reports how many unique values of a field appear in each group created by the by clause. Counting unique values is different from counting events, because repeated values are ignored.

  116. Question 116Transforming Commands, Reports, and Dashboards

    A dashboard has a time input configured with the token tok. Which token references the earliest time chosen by the user?

    1. $tok.start$
    2. $tok.from$
    3. $tok.time.earliest$
    4. $tok.earliest$ Correct answer.

    Explanation

    A time input publishes two tokens, $tok.earliest$ and $tok.latest$, which panel searches reference in their earliest and latest settings. Other input types such as dropdowns publish only the raw selected value under the base token name.

  117. Question 117Transforming Commands, Reports, and Dashboards

    Which attribute on a dashboard panel prevents that panel's search from running until a token produced by a user selection has a value?

    1. depends Correct answer.
    2. condition
    3. searchWhenChanged
    4. rejects

    Explanation

    The depends attribute names one or more tokens, and the panel delays running its search until every named token has a value, which avoids searches firing on an empty input. Values can also be filtered with rejects so that unsuitable selections never populate the token.

  118. Question 118Transforming Commands, Reports, and Dashboards

    An analyst wants an existing saved search to run automatically each weekday morning and email its results to a distribution list. Which approach accomplishes this?

    1. Edit the saved search's schedule, set a cron expression, and enable an email action. Correct answer.
    2. Add a timechart with span=1d so the report covers each weekday.
    3. Convert the search into a dashboard panel and refresh the dashboard at that time each day.
    4. Add the search output to a lookup file and configure that lookup to refresh automatically.

    Explanation

    Scheduling a saved search stores a cron schedule that runs it in the background, and enabling the email action sends the results to the configured recipients. Scheduling settings are found when editing the saved search, along with the actions to take when it completes.

  119. Question 119Transforming Commands, Reports, and Dashboards

    In a chart command, which option caps the number of series generated by the split-by clause and groups the remaining values into a single series?

    1. limit Correct answer.
    2. other
    3. top
    4. maxseries

    Explanation

    The limit option sets how many distinct values of the split-by field become their own series, and any values beyond that are combined into a series named OTHER. If the number of distinct values is within the limit, no OTHER series is created.

  120. Question 120Transforming Commands, Reports, and Dashboards

    Which command runs a search template once for every distinct value of a field in the current results and merges the results it returns?

    1. union
    2. foreach
    3. appendpipe
    4. map Correct answer.

    Explanation

    map takes the distinct values of a field and runs a templated subsearch for each one, combining the output, and it is bounded by the maxsearches argument. Because it launches many searches, it performs poorly on result sets with many distinct values.

  121. Question 121Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    What does a tag do in Splunk?

    1. Applies a keyword to a field/value pair Correct answer.
    2. Schedules a saved search that writes results to an index
    3. Maps lookup keys to lookup values at search time
    4. Extracts fields at index time using a regular expression

    Explanation

    A tag is a knowledge object that attaches a keyword to a specific field/value combination, which lets you search with tag=<keyword>. Tags are applied at search time and are stored in tags.conf.

  122. Question 122Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which field do events gain when they match an event type?

    1. event_type
    2. sourcetype
    3. tag
    4. eventtype Correct answer.

    Explanation

    When a search matches the search string of an event type, Splunk adds a field named eventtype whose value is the name of the event type. This field is added at search time and becomes multivalued when several event types match the same event.

  123. Question 123Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which command returns the contents of a lookup file as search results?

    1. inputlookup Correct answer.
    2. collect
    3. outputlookup
    4. lookup

    Explanation

    The inputlookup command reads a lookup table file or lookup definition and returns its rows as search results. It is typically used to inspect or process lookup data without correlating it to events.

  124. Question 124Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    What is the purpose of a workflow action?

    1. To schedule a report and email its results
    2. To extract fields from raw event data
    3. To normalize field names across sourcetypes
    4. To add a clickable link or button to events or fields Correct answer.

    Explanation

    Workflow actions add links, buttons, or menu items to events and field values so users can launch searches, open URLs, or pass values to other applications. They are configured under Settings > Fields > Workflow actions.

  125. Question 125Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    The host web01 has been tagged with the keyword web. Which search returns the events carrying that tag?

    1. index=main tag=web Correct answer.
    2. index=main tag::web=true
    3. index=main TAG(web)
    4. index=main tags=web

    Explanation

    The tag field can be searched directly with tag=<tagname>, which matches events where that keyword is applied to any field value. The search index=main tag=web therefore returns the events tagged with web.

  126. Question 126Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    In which configuration file are event types stored?

    1. props.conf
    2. tags.conf
    3. eventtypes.conf Correct answer.
    4. transforms.conf

    Explanation

    Event types are defined as stanzas in eventtypes.conf, with the search string, optional tags, and priority. The file can be managed through Splunk Web under Settings > Event types.

  127. Question 127Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which command writes the current search results into a lookup file?

    1. lookup
    2. outputlookup Correct answer.
    3. collect
    4. inputlookup

    Explanation

    The outputlookup command writes the results of a search to a lookup table file or KV store collection, replacing the existing contents unless append=true is specified. It is the counterpart of inputlookup.

  128. Question 128Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which syntax inserts the value of the src field into a workflow action's URI?

    1. %src%
    2. $src$ Correct answer.
    3. <src>
    4. {{src}}

    Explanation

    Workflow actions use dollar-sign token substitution, so $src$ is replaced at runtime with the value of the src field from the event. The same token syntax is used in labels and in search strings for search-type actions.

  129. Question 129Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A user created a tag, but a teammate cannot see or use it. What most likely explains this?

    1. The tag's sharing permissions and app context Correct answer.
    2. The teammate's search time range is too narrow
    3. The tag was created at index time instead of search time
    4. The tag's priority value is set too low

    Explanation

    Tags are knowledge objects, so their visibility depends on the sharing setting (owner, app, or all apps) and on role permissions. A tag shared only with its app or owner is invisible to other users or other apps.

  130. Question 130Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which statement about the eventtype field is correct?

    1. It is written to disk at index time
    2. It overwrites the sourcetype field
    3. It is added at search time and can hold several values Correct answer.
    4. It exists only for events that also have tags

    Explanation

    The eventtype field is generated at search time for each event that matches an event type's search string. If more than one event type matches, the field becomes multivalued with one value per matching event type.

  131. Question 131Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    An event type named login_failure exists. Which search filters events using that event type?

    1. index=main type=login_failure
    2. index=main | eventtype login_failure
    3. index=main eventtype=login_failure Correct answer.
    4. index=main event_type::login_failure=true

    Explanation

    Event types are referenced in search by filtering on the eventtype field with the event type name as the value. The search is evaluated at search time against the event type's saved search string.

  132. Question 132Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A lookup definition named users maps the field user to the field dept. Which search adds only the dept field to results?

    1. | inputlookup users dept
    2. | lookup users user OUTPUT dept Correct answer.
    3. | lookup users dept
    4. | lookup dept OUTPUT users

    Explanation

    In the lookup command the lookup name comes first, followed by the field to match on, and OUTPUT lists the fields to bring back. Specifying OUTPUT dept limits the added fields to dept.

  133. Question 133Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    How does a lookup table file differ from a lookup definition?

    1. Only definitions can be referenced by the lookup command
    2. The file is a config stanza; the definition holds the rows
    3. The file holds the data; the definition configures its use Correct answer.
    4. Both are created only inside transforms.conf

    Explanation

    A lookup table file is the actual data source, such as a CSV file or a KV store collection. A lookup definition is the knowledge object that tells Splunk how to use that file, including match fields and case sensitivity.

  134. Question 134Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    You want a workflow action to be offered only on events from the access_combined sourcetype. Where is that configured?

    1. In props.conf with a REPORT stanza
    2. In the workflow action's apply-to settings Correct answer.
    3. In authorize.conf with a role stanza
    4. In transforms.conf with a lookup stanza

    Explanation

    Each workflow action has apply-to settings that determine whether it appears on the event menu or on a specific field, and which sourcetypes or fields it is available for. Restricting the sourcetype there hides the action elsewhere.

  135. Question 135Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which action types can a workflow action use?

    1. Search and PUT only
    2. GET (link), POST, and search Correct answer.
    3. GET and DELETE only
    4. GET and lookup

    Explanation

    A workflow action can open a URL with a GET request, submit data to a URL with a POST request, or run a secondary search. The chosen type determines which configuration fields, such as URI or search string, are available.

  136. Question 136Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which search returns events that have the tag prod on any of their fields?

    1. index=main | tags prod
    2. index=main prod=true
    3. index=main tag::prod
    4. index=main tag=prod Correct answer.

    Explanation

    The tag field aggregates every tag keyword applied to an event, so filtering on tag=prod matches the keyword regardless of which field carries it. To restrict the match to one field you would use the tag::<field> form instead.

  137. Question 137Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    An automatic lookup is configured for the host field in props.conf. What effect does it have on searches?

    1. Matching events are dropped from the results
    2. Fields are added to events automatically Correct answer.
    3. The lookup file is rewritten on every search
    4. It runs only when outputlookup is used

    Explanation

    An automatic lookup runs whenever the relevant sourcetype or event type is searched, enriching events with lookup fields without requiring an explicit lookup command. It never removes events unless you explicitly filter on the returned fields.

  138. Question 138Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    The search | lookup mylookup id returns no additional fields. Which is the most likely cause?

    1. The lookup file has no column named id Correct answer.
    2. The lookup command requires a time range
    3. Lookups can match only on the host field
    4. The lookup file has too many columns

    Explanation

    The field named after the lookup name must exist both in the events and in the lookup file for matches to occur. If the lookup header uses a different name, no values match and no fields are returned.

  139. Question 139Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which setting makes a workflow action open its destination in a new browser window?

    1. The search string setting
    2. The open-in-new-window setting Correct answer.
    3. The label token setting
    4. The apply-to field setting

    Explanation

    Workflow actions include an option to open the link in a new window, which sets the browser target to a blank frame. The apply-to, search string, and label settings control other aspects such as availability and displayed text.

  140. Question 140Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Where in Splunk Web do you view and edit existing tags?

    1. Settings > Lookups
    2. Settings > Fields > Fields
    3. Settings > Tags Correct answer.
    4. Settings > Data inputs

    Explanation

    Tags are managed as knowledge objects under Settings > Tags, where you can review, rename, and delete them and adjust permissions. Tags can also be added directly from the field value menu in search results.

  141. Question 141Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A tag is created in app A with sharing set to App. A user runs a search in app B on the same instance. Does the tag apply?

    1. Yes, because tags are stored inside the index
    2. No, because the tag is scoped to app A Correct answer.
    3. Yes, because tags always apply across all apps
    4. No, because tags are private to each user

    Explanation

    Knowledge objects, including tags, are scoped to their app context. A tag shared only with its own app is not visible to searches run in another app unless it is shared to all apps.

  142. Question 142Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    An event matches two event types that apply different tags to it. Which tags take effect?

    1. Tags from both event types are always merged
    2. Those from the event type with the lower priority
    3. Those from the event type that was created first
    4. Those from the event type with the higher priority Correct answer.

    Explanation

    Each event type has a priority value, and when several event types match the same event, the one with the highest priority determines the tags and field values that are applied. Priority resolves conflicts rather than merging results.

  143. Question 143Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which lookup type stores its data as JSON documents and supports per-record updates and accelerated lookups?

    1. A CSV lookup
    2. A geospatial lookup
    3. A scripted lookup
    4. A KV store lookup Correct answer.

    Explanation

    KV store lookups keep their data in collections of JSON documents, which can be edited record by record in Splunk Web and accelerated for large or frequently changing datasets. CSV lookups instead read from a flat file uploaded to the app.

  144. Question 144Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A workflow action must run a secondary search that receives the clicked field value. Which configuration accomplishes this?

    1. A GET action with a static URI
    2. An automatic lookup bound to the field
    3. A POST action with a form payload
    4. A search action using a field token Correct answer.

    Explanation

    A search-type workflow action runs a secondary search, and the clicked field value is passed into that search through dollar-sign token substitution. GET and POST actions instead send the user to a URL.

  145. Question 145Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Both host=web01 and user=web01 carry the tag prod. Which search matches only when the tag is on the host field?

    1. index=main | tag prod host
    2. index=main tag=prod
    3. index=main tag::host=prod Correct answer.
    4. index=main prod::host=true

    Explanation

    Tags applied to a specific field appear as fields of the form tag::<fieldname>, so tag::host=prod restricts the match to tags on the host field. Searching tag=prod would match the keyword on any field, including user.

  146. Question 146Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which statement best describes an event type in Splunk?

    1. A saved search string that categorizes events Correct answer.
    2. A tag applied to a sourcetype
    3. A scheduled search that writes results to an index
    4. A lookup table that maps field values to categories

    Explanation

    An event type is a saved search string that is evaluated at search time to categorize matching events. Splunk adds the event type name to the eventtype field of every event the search string matches. Event types do not store results, schedule execution, or map field values.

  147. Question 147Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    In Splunk, a tag is attached directly to which of the following?

    1. An entire index
    2. A specific field-value pair Correct answer.
    3. A user role and its capabilities
    4. A sourcetype definition in props.conf

    Explanation

    Tags are stored against a field-value pair, so tagging host=web01 with prod makes every event containing that pair searchable with tag=prod. Tagging an event type works the same way because the tag is applied to the eventtype field's value. Tags are search-time knowledge and do not modify raw data.

  148. Question 148Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which command returns the rows of a lookup table as search results?

    1. collect
    2. outputlookup
    3. lookup
    4. inputlookup Correct answer.

    Explanation

    The inputlookup command reads a lookup table file or KV Store collection and returns its contents as events in the results. The lookup command does the opposite job: it enriches events already in the pipeline by matching their field values against the table.

  149. Question 149Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    In Splunk Web, how do you create an event type from a search that has just been run?

    1. Export the search results to a CSV file for download
    2. Schedule the search as an alert
    3. Choose Save As, then Event type Correct answer.
    4. Add the search to a dashboard panel

    Explanation

    The Save As menu on the search page offers Event type, which saves the current search string as a new event type and applies it when the search is rerun. The search must return events rather than use transforming commands, because an event type has to categorize raw events.

  150. Question 150Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A lookup returns a field named priority that already exists in some events. Which search adds the lookup value only to events that do not already have a priority field?

    1. | lookup mylookup id OUTPUT priority AS src
    2. | lookup mylookup id AS priority
    3. | lookup mylookup id OUTPUTNEW priority Correct answer.
    4. | lookup mylookup id OUTPUT priority

    Explanation

    OUTPUTNEW writes the listed lookup fields only when the event does not already contain them, so existing values are preserved. The plain OUTPUT clause overwrites any existing value with the lookup value. The AS keyword renames the field used for matching, not the output behavior.

  151. Question 151Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which props.conf entry configures an automatic lookup that maps the event field dept through the lookup definition users?

    1. REPORT-user = user in raw
    2. EVAL-dept = coalesce(dept, "unknown")
    3. LOOKUP-dept = users dept AS dept Correct answer.
    4. FIELDALIAS-src = src AS clientip

    Explanation

    Automatic lookups are declared in props.conf with a LOOKUP-<name> setting whose value names a lookup definition followed by the field mapping. Because it is an automatic lookup, the enrichment is applied whenever the stanza's events are searched, without a lookup command.

  152. Question 152Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A lookup must match user names regardless of letter case. Which lookup definition setting accomplishes this?

    1. Set max_matches to 0 so all matches are returned
    2. Set match_type to WILDCARD for the user field
    3. Set external_type to kvstore for the definition
    4. Set case_sensitive_match to false Correct answer.

    Explanation

    The case_sensitive_match setting in the lookup definition controls whether lookup matching considers letter case, and setting it to false makes matching case-insensitive. This is configured on the definition, so it applies to every search that uses the lookup.

  153. Question 153Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A workflow action should be offered when a user clicks a field value in an event, but it should not appear in the event's action menu. Which setting controls this?

    1. Grant the action to every role
    2. Set the display location to Field menu Correct answer.
    3. Set the action type to POST
    4. Set the action's fields list to include every field

    Explanation

    The display location setting determines which menus offer the action: Field menu, Event menu, or Both. Choosing Field menu restricts the action to the menu that appears when a field value is clicked.

  154. Question 154Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Two event types match the same event and each specifies a different color. Which event type's color is displayed?

    1. The most recently created event type
    2. The one whose name sorts first alphabetically
    3. The one with the most specific search string
    4. The one with the higher priority value Correct answer.

    Explanation

    Each event type can be assigned a priority, and when several event types match one event the highest priority determines which color is shown. Name order, creation time, and search specificity play no part in resolving the display.

  155. Question 155Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A lookup definition must match event IP addresses against subnet ranges stored in the lookup, such as 10.0.0.0/8. Which match_type value should be used?

    1. EXACT
    2. CIDR Correct answer.
    3. WILDCARD
    4. REGEX

    Explanation

    The match_type setting on a lookup definition selects the matching algorithm, and CIDR allows a field value to match an entry written as an address range. EXACT compares literal strings, and WILDCARD allows asterisks and question marks in the table entries.

  156. Question 156Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    Which Splunk Web location is used to upload a CSV file so it can serve as a lookup table?

    1. Settings > User interface > Views
    2. Settings > Fields > Fields
    3. Settings > Data inputs > Files and directories
    4. Settings > Lookups > Lookup table files Correct answer.

    Explanation

    Lookup table files are managed under Settings > Lookups, where a CSV can be uploaded and then referenced by a lookup definition. Data inputs configure file monitoring and indexing rather than search-time lookups.

  157. Question 157Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    The lookup table users contains a user_id column, and events contain the field uid. Which search matches event values against the correct lookup column?

    1. | lookup users uid AS user_id
    2. | lookup users user_id OUTPUT uid
    3. | lookup users uid OUTPUT user_id
    4. | lookup users user_id AS uid Correct answer.

    Explanation

    In the lookup command the lookup table's column is named first, followed by AS and the event field to match it against. Using AS maps the table column user_id onto the event's uid field so the match succeeds.

  158. Question 158Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    An administrator adds LOOKUP-products = products.csv id AS id to props.conf, but the automatic lookup never enriches events. What is the most likely cause?

    1. The CSV file must be added as a KV Store collection
    2. Automatic lookups cannot be defined in props.conf
    3. Automatic lookups require the search to include the lookup command
    4. It references a CSV file instead of a lookup definition Correct answer.

    Explanation

    The LOOKUP- setting names a lookup definition, which is a stanza in transforms.conf that in turn points to the table file. Naming the CSV file directly leaves Splunk with no definition to resolve, so the setting is ignored.

  159. Question 159Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A workflow action's Fields setting lists only src and dest. A user clicks the value of the user field in an event. What happens?

    1. The action is not displayed for the user field Correct answer.
    2. The action appears and passes the literal text $user$
    3. The action appears only in the event's action menu
    4. The action appears and passes an empty value for user

    Explanation

    The Fields setting restricts the action to the listed fields, so the action is offered only when the user interacts with src or dest values. Clicking a field outside that list does not offer the action at all.

  160. Question 160Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

    A user tags the host value web01 in a single event with the tag prod. Which events are affected by that tag?

    1. Only the single event that was tagged
    2. Only events in the same index as the tagged event
    3. All events in which the host field has that value Correct answer.
    4. All events from the same source as the tagged event

    Explanation

    Tags are knowledge objects bound to a field-value pair, not to an individual event, so tagging host=web01 applies the tag to every event where host has that value. This is why tagging performed in the field menu affects searches across the whole data set.

  161. Question 161Data Models, Pivot, and Acceleration

    What is the primary purpose of a data model in Splunk?

    1. To define structured datasets for Pivot and tstats Correct answer.
    2. To replace indexes when ingesting data from forwarders
    3. To store raw event data in a compressed archive for long-term retention
    4. To schedule alerts for saved searches and reports

    Explanation

    A data model organizes event data into a hierarchical set of datasets with defined fields and constraints. Pivot and tstats use these definitions to build reports and run accelerated searches. Data models do not store raw events or replace indexes.

  162. Question 162Data Models, Pivot, and Acceleration

    Which command is designed to search accelerated data model summaries?

    1. | metadata
    2. | tstats Correct answer.
    3. | datamodel
    4. | inputlookup

    Explanation

    The tstats command queries data model summaries and is the primary command for accelerated data. It can group and aggregate fields defined in the data model. Other commands do not query accelerated data model summaries directly.

  163. Question 163Data Models, Pivot, and Acceleration

    What is Pivot in Splunk?

    1. A method for forwarding logs to a central indexer
    2. An indexer clustering feature for replicating buckets
    3. A command-line tool for editing data model JSON definitions
    4. A visual interface for building reports and charts from data models Correct answer.

    Explanation

    Pivot provides a graphical interface for creating tables, charts, and other reports from data model datasets. It lets users split, filter, and aggregate data without writing SPL manually. It is not an indexer clustering or forwarding feature.

  164. Question 164Data Models, Pivot, and Acceleration

    In a data model, which dataset type represents the base set of events from which child datasets inherit?

    1. Root event dataset Correct answer.
    2. Transaction dataset
    3. Child dataset
    4. Lookup dataset

    Explanation

    A root event dataset defines the broadest set of events in a data model and serves as the parent for child datasets. Child datasets inherit the constraints of their parent and add their own constraints. Lookup and transaction datasets are not the base event hierarchy.

  165. Question 165Data Models, Pivot, and Acceleration

    Data model acceleration stores precomputed results as which type of files?

    1. CSV lookup files
    2. tsidx summary files Correct answer.
    3. PDF reports
    4. KV store collections

    Explanation

    Data model acceleration builds tsidx summary files that contain precomputed field values and event summaries. These summaries allow tstats and Pivot to return results quickly. CSV lookups, KV store collections, and PDF reports are separate Splunk features.

  166. Question 166Data Models, Pivot, and Acceleration

    In Settings > Data Models, a data model shows an 'Accelerated' status. What does this mean?

    1. The data model is currently being edited by an administrator
    2. The data model has been disabled and cannot be used
    3. The data model contains only lookup-based fields and no event fields
    4. Summaries are built and available for tstats and Pivot Correct answer.

    Explanation

    An Accelerated status means Splunk has built acceleration summaries for the data model within its configured summary range. Those summaries can then be used by tstats and Pivot. The status does not mean the model is being edited or contains only lookup fields.

  167. Question 167Data Models, Pivot, and Acceleration

    In Pivot, which element is used to group results into rows?

    1. Cell value
    2. Split rows Correct answer.
    3. Filter
    4. Time range

    Explanation

    Split rows groups Pivot results by one or more field values, placing each group on its own row. Filters restrict which events are included, while cell values define the aggregation shown. Time range limits the search period.

  168. Question 168Data Models, Pivot, and Acceleration

    Which command displays the data models available in the current app context?

    1. | tstats
    2. | metadata
    3. | datamodel Correct answer.
    4. | pivot

    Explanation

    The datamodel command lists data models and can show details about their datasets and fields. It is used for inspection rather than for aggregating event data. The tstats command searches accelerated data, while metadata reports index metadata.

  169. Question 169Data Models, Pivot, and Acceleration

    A child dataset has constraint `status=500` and its parent has constraint `index=web`. Which events are included in the child dataset?

    1. All events in `index=web` regardless of status
    2. Only events that match `status=500` but not `index=web`
    3. All events with `status=500` regardless of index
    4. Only events that match both `index=web` and `status=500` Correct answer.

    Explanation

    Child datasets inherit their parent constraints, and their own constraints are applied in addition. The effective constraint is the parent constraint AND the child constraint. Therefore the child includes only events satisfying both conditions.

  170. Question 170Data Models, Pivot, and Acceleration

    In a data model, which field type calculates its value by using an eval expression at search time?

    1. Auto-extracted field
    2. String field
    3. Lookup field
    4. Eval field Correct answer.

    Explanation

    An eval field in a data model derives its value from an eval expression evaluated at search time. Auto-extracted fields come from indexed or search-time extraction, and lookup fields come from lookup tables. String is a data type, not a calculated field mechanism.

  171. Question 171Data Models, Pivot, and Acceleration

    In a tstats search, which argument identifies the data model and dataset to query?

    1. datamodel=Web.Web Correct answer.
    2. from=Web.Web
    3. model=Web.Web
    4. dataset=Web.Web

    Explanation

    The tstats command uses the datamodel argument in the form datamodel=<DataModel>.<Dataset>. This tells tstats which accelerated dataset to search. The other argument names are not the tstats syntax for selecting a data model dataset.

  172. Question 172Data Models, Pivot, and Acceleration

    What does `summariesonly=true` do in a tstats search?

    1. It disables acceleration for the data model and all child datasets
    2. It sums only numeric fields in the dataset
    3. It returns only the name of the summary index used
    4. It restricts results to accelerated summary data only Correct answer.

    Explanation

    The summariesonly argument controls whether tstats uses only accelerated summaries. When set to true, tstats does not fall back to raw data for time ranges outside the accelerated summaries. This is useful for confirming that results come from acceleration.

  173. Question 173Data Models, Pivot, and Acceleration

    In Pivot, what is the difference between a filter and a split?

    1. Both group events, but only filters can affect the chart type
    2. A filter reduces events; a split groups the remaining events Correct answer.
    3. A filter groups events for charting; a split removes events that do not match
    4. Both reduce events, but only splits can affect the chart type

    Explanation

    A Pivot filter applies conditions that remove events from the result set. A split groups the remaining events by field values into rows or columns. Filters and splits serve different purposes and are often used together.

  174. Question 174Data Models, Pivot, and Acceleration

    When you enable data model acceleration with a summary range of 30 days, what is accelerated?

    1. Only the current day's data
    2. Only data within the most recent 30 days Correct answer.
    3. All events ever indexed in the data model
    4. Only data older than 30 days

    Explanation

    The summary range defines how far back acceleration summaries are maintained. A 30-day summary range accelerates data within the most recent 30-day window. Older data is outside the accelerated range unless the summary range is extended.

  175. Question 175Data Models, Pivot, and Acceleration

    Accelerated data model summaries are queried directly with which methods?

    1. The stats command on raw events
    2. The lookup command
    3. tstats or Pivot Correct answer.
    4. The search command against the summary index

    Explanation

    Accelerated data model summaries are designed to be queried through tstats, and through Pivot when the underlying data model is accelerated. They are not a normal index that users search directly with the search command. Other commands do not specifically target data model acceleration summaries.

  176. Question 176Data Models, Pivot, and Acceleration

    In Pivot, which setting limits each split to the top N results?

    1. Limit Correct answer.
    2. Sort
    3. Filter
    4. Cell value

    Explanation

    The Limit setting in Pivot restricts each split to a specified number of results, commonly the top N by a chosen metric. Sorting controls order but does not by itself restrict the number of results. Filters and cell values serve different roles.

  177. Question 177Data Models, Pivot, and Acceleration

    To allow users in other apps to use a data model you created, what must you configure?

    1. A deployment app on each universal forwarder
    2. A license group that includes all target users
    3. Object permissions for the data model Correct answer.
    4. A separate index for every user who needs access

    Explanation

    Data model objects have permissions that determine which users and apps can view or edit them. Setting permissions to the app or global level makes the data model available outside your private context. Indexes, license groups, and forwarder apps do not control data model sharing.

  178. Question 178Data Models, Pivot, and Acceleration

    When data model acceleration is first enabled, what does Splunk do?

    1. Disables Pivot for that model until the next restart
    2. Builds summaries for the configured summary range Correct answer.
    3. Converts the data model into a lookup table definition
    4. Deletes the data model and recreates it from the raw index

    Explanation

    Enabling acceleration starts a background process that builds summaries over the configured summary range. Once built, the summaries can serve tstats and Pivot searches. Acceleration does not delete the model or disable Pivot.

  179. Question 179Data Models, Pivot, and Acceleration

    Why can high-cardinality fields make data model acceleration less efficient?

    1. They force Pivot to display results only as a pie chart
    2. They increase the size of tsidx summaries and slow searches Correct answer.
    3. They automatically disable tstats for the entire data model and all child datasets
    4. They prevent the data model from being saved in the app

    Explanation

    High-cardinality fields have many distinct values, which can make acceleration summaries larger and more expensive to search. This can reduce the performance benefit of acceleration. It does not prevent saving the data model or automatically disable tstats.

  180. Question 180Data Models, Pivot, and Acceleration

    Which Pivot chart type is best for showing a metric's trend over time?

    1. Line chart Correct answer.
    2. Single value
    3. Pie chart
    4. Scatter chart

    Explanation

    A line chart is well suited to showing how a metric changes across a time dimension. Pie charts show proportions, single values show one number, and scatter charts show relationships between two measures.

  181. Question 181Data Models, Pivot, and Acceleration

    Which dataset type in a data model is based on a search rather than only on constraints against raw events?

    1. Root search dataset Correct answer.
    2. Lookup dataset
    3. Root event dataset
    4. Child dataset

    Explanation

    A root search dataset is defined by a search and can serve as the parent for child datasets. A root event dataset is defined by constraints on events. Child datasets inherit from a parent, and lookup datasets derive fields from lookup files.

  182. Question 182Data Models, Pivot, and Acceleration

    A data model is accelerated for a 7-day summary range. A user runs a Pivot over the last 30 days. What is the likely behavior?

    1. Pivot fails immediately because the requested time range exceeds the configured summary range
    2. The most recent 7 days are served from summaries; older data requires a raw search and may be slower Correct answer.
    3. Pivot automatically extends the summary range to 30 days and rebuilds all summaries
    4. All 30 days are served from summaries because acceleration covers the entire data model regardless of range

    Explanation

    Acceleration only covers data inside the configured summary range. For a 30-day Pivot with a 7-day summary range, the most recent 7 days can use summaries while older data must be searched from raw events, which can be slower. Pivot does not automatically extend the summary range.

  183. Question 183Data Models, Pivot, and Acceleration

    In a tstats search, what happens if the `by` clause references a field that is not defined in the data model dataset?

    1. tstats ignores the by clause and returns one total count
    2. tstats creates the field in the data model and then groups on it
    3. The search fails or returns no grouped results for that field Correct answer.
    4. tstats extracts the missing field from raw events automatically and groups on it

    Explanation

    tstats groups only on fields that exist in the specified data model dataset. If the field is not part of that dataset, tstats cannot use it for grouping and the search typically fails or produces no grouped results. tstats does not modify the data model or silently ignore the clause.

  184. Question 184Data Models, Pivot, and Acceleration

    If a data model is not accelerated, how does Pivot generate its results?

    1. It reads precomputed tsidx summaries from the summaries directory
    2. It returns an error until an administrator enables acceleration
    3. It runs a search against raw data, which can be slower Correct answer.
    4. It uses the KV store to retrieve accelerated results

    Explanation

    Pivot can use a data model even when acceleration is not enabled. In that case, Pivot generates and runs a search against raw data, so results may take longer than with accelerated summaries. Acceleration is a performance optimization, not a requirement for Pivot.

  185. Question 185Data Models, Pivot, and Acceleration

    Which statement about data model acceleration and raw event retention is correct?

    1. Acceleration does not change raw event retention; summaries are separate from raw events Correct answer.
    2. Acceleration increases raw event retention automatically for the accelerated index
    3. Acceleration deletes raw events after the summaries are built for the summary range
    4. Acceleration summaries can be searched directly with the normal search command without using tstats or Pivot

    Explanation

    Data model acceleration creates separate summary files and does not alter how long raw events are retained. Raw event retention is controlled by index settings such as frozenTimePeriodInSecs. Deleting raw events would be a separate index retention decision.

  186. Question 186Data Models, Pivot, and Acceleration

    In a data model, which dataset type is defined by constraints on raw event metadata such as index, sourcetype, and host?

    1. Transaction dataset
    2. Root search dataset
    3. Root event dataset Correct answer.
    4. Child event dataset

    Explanation

    A root event dataset is the base of an event-based hierarchy and is defined entirely by constraints against raw events, such as index, sourcetype, host, and field values. Datasets built on top of it are children that add or inherit constraints.

  187. Question 187Data Models, Pivot, and Acceleration

    Which Pivot element holds the statistical aggregation, such as count or average, that appears in the results?

    1. Split Rows
    2. Column Values Correct answer.
    3. Split Columns
    4. Filter

    Explanation

    The Column Values element is where you choose the aggregation function and the field it applies to, and it produces the numbers shown in the report or chart. Split elements only group the data, and filters only restrict which events are included.

  188. Question 188Data Models, Pivot, and Acceleration

    Which statement best describes a data model in Splunk?

    1. A structured hierarchy of datasets describing event data Correct answer.
    2. A lookup table that maps field values to human-readable names
    3. A saved report that runs on a schedule and writes its results to an index
    4. A search-time field extraction that applies to one sourcetype

    Explanation

    A data model is a hierarchical, structured description of event data organized into datasets and fields. Tools such as Pivot, tstats, and the datamodel command read from that structure rather than from ad hoc searches.

  189. Question 189Data Models, Pivot, and Acceleration

    Data model definitions are persisted in the file system as files in which format?

    1. CSV
    2. JSON Correct answer.
    3. YAML
    4. XML

    Explanation

    Data models are stored under the app's data/models directory as JSON files, which is why they can be copied between apps and searched with the REST API. Lookups and configurations use other formats, but data models themselves are JSON.

  190. Question 190Data Models, Pivot, and Acceleration

    A transaction dataset in a data model is defined by which set of settings?

    1. An index, sourcetype, and host constraint for raw events
    2. A base search string and a set of inherited fields
    3. A grouping field plus maxspan and maxpause constraints Correct answer.
    4. A lookup definition and a match field for enrichment

    Explanation

    Transaction datasets group related events that share a common field value, bounded by maxspan for the total duration of a transaction and maxpause for the maximum gap between events. This mirrors the behavior of the transaction command.

  191. Question 191Data Models, Pivot, and Acceleration

    What is the effect of adding prestats=true to a tstats search?

    1. It groups results by every field defined in the data model dataset
    2. It appends the results of a second tstats search to the same report
    3. It returns partial results that a later stats command completes Correct answer.
    4. It restricts the search to accelerated data only and skips raw events

    Explanation

    prestats=true makes tstats return results in the prestats (partial aggregation) format, so a following stats, timechart, or chart command can finish the aggregation without another pass over the data. It is a performance option, not a filter on which data is read.

  192. Question 192Data Models, Pivot, and Acceleration

    Which tstats argument combines the results of multiple tstats searches, each drawn from a different dataset, into one report?

    1. append=t Correct answer.
    2. summariesonly=true
    3. prestats=true
    4. wrap=t

    Explanation

    append=t lets a single tstats search include additional tstats searches against other datasets, merging their result sets into one output. It is the standard way to report across more than one accelerated dataset in one search.

  193. Question 193Data Models, Pivot, and Acceleration

    Which role capability must a user have to turn on acceleration for a data model?

    1. accelerate_datamodel Correct answer.
    2. schedule_search
    3. edit_data_models
    4. edit_saved_searches

    Explanation

    Acceleration is a separate privilege from editing a data model, and it is granted through the accelerate_datamodel capability. A user with only editing rights can change the model's structure but cannot enable acceleration on it.

  194. Question 194Data Models, Pivot, and Acceleration

    In Pivot, what happens when you add a second field to the Split Rows element?

    1. The second field is ignored until the first split is removed
    2. The second field automatically moves to the Split Columns element
    3. The two fields are combined into a single concatenated row label
    4. Rows nest so the second field is grouped within each first value Correct answer.

    Explanation

    Each additional field in Split Rows creates another level of hierarchy, with inner splits evaluated inside each value of the outer split. This lets you drill from a broad category down to its sub-categories in one table.

  195. Question 195Data Models, Pivot, and Acceleration

    Why does a tstats search typically return results much faster than an equivalent search over raw events?

    1. It reads precomputed tsidx summaries instead of raw events Correct answer.
    2. It caches the results of the previous run in the dispatch directory
    3. It runs the search in parallel across all indexers by default
    4. It samples a subset of matching events and extrapolates the totals

    Explanation

    Data model acceleration writes summaries into tsidx files, and tstats queries those summaries rather than scanning and extracting fields from raw events. Because far less data is read, the search completes much faster and returns exact counts, not estimates.

  196. Question 196Data Models, Pivot, and Acceleration

    An accelerated data model currently uses a 30-day summary range. An admin changes the summary range to 90 days. What is the result?

    1. Existing summaries are deleted and only new events are accelerated
    2. The new range applies only to Pivot and not to tstats searches
    3. Nothing changes until the acceleration search is manually restarted
    4. Splunk backfills the extra 60 days, using more time and disk Correct answer.

    Explanation

    The summary range sets how far back summaries are built, so extending it requires generating summaries for the newly covered older period. That backfill consumes additional disk space and initial build time before the new range is complete.

  197. Question 197Data Models, Pivot, and Acceleration

    An admin adds a new field to the parent (root event) dataset of a data model. What is the effect on existing child datasets?

    1. Child datasets inherit the new field automatically Correct answer.
    2. The child datasets reject the change until their constraints are edited
    3. Child datasets must be recreated to see the new field
    4. The new field is visible only in the parent dataset's searches

    Explanation

    Datasets inherit the constraints and fields of their ancestors, so a field defined at the parent level becomes available to every descendant dataset. This inheritance is why fields should be defined at the highest level where they apply.

  198. Question 198Data Models, Pivot, and Acceleration

    What happens to existing acceleration summaries when you add a new field to an accelerated data model?

    1. Only summaries for the current day are regenerated on the next run
    2. They are invalidated and the model is rebuilt from scratch Correct answer.
    3. They are kept, but the new field is unavailable until a manual rebuild
    4. They keep serving results while the new field is added in place

    Explanation

    Because the accelerated summary files must contain every field the model defines, structurally changing an accelerated model invalidates its summaries. Splunk clears the old summaries and rebuilds them across the full summary range, so acceleration status drops and climbs again as the rebuild progresses.

  199. Question 199Data Models, Pivot, and Acceleration

    Which argument, used with `| datamodel <model> <dataset>`, returns the base search string from which the dataset's events are derived?

    1. summary
    2. objects
    3. search Correct answer.
    4. flatten

    Explanation

    The search argument makes the datamodel command output the generated search for the dataset, which is useful for verifying constraints and translations. The flatten argument instead returns events with fields flattened and the search appended, while the default returns dataset objects.

  200. Question 200Data Models, Pivot, and Acceleration

    A data model is accelerated with a 1-year summary range, but the summary index has a retention period of only 30 days. What is the consequence?

    1. The summary range is automatically shortened to match the retention period
    2. Acceleration fails and the data model reverts to unaccelerated status
    3. Older searches fall back to raw events, so their results remain complete
    4. Summaries older than 30 days are deleted, so old data is missing Correct answer.

    Explanation

    Acceleration summaries live in the summary index and are subject to that index's retention settings, so retention shorter than the summary range silently removes older summaries. Searches over the older period then report on incomplete data, especially when only summaries are used.

Splunk Power User flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Hot bucket
A hot bucket is the newest, writable bucket in an index; indexers write incoming events to it until maxDataSize is reached, then it rolls to warm.
Bloom filter
A per-bucket file that lets an indexer quickly determine whether a search term might exist in that bucket, skipping buckets that definitely do not contain it.
Search job lifetime
A search job with no activity is cancelled after 10 minutes by default; the TTL is configurable and can be extended while the job is still displayed.
Subsearch limits
A subsearch enclosed in square brackets returns at most 10,000 results and runs at most 60 seconds by default before it is truncated or terminated.
Search modes
Smart extracts only fields needed by the search, Fast disables field discovery for non-required fields, and Verbose extracts all fields and returns all matching events.
Streaming versus transforming
Streaming commands such as eval and rex process events as they arrive on indexers, while transforming commands such as stats run on the search head and collapse events into results.
_indextime
The timestamp recording when an event was indexed, distinct from _time, the event's own timestamp; it helps locate older events that were indexed recently.
Default fields
host, source, sourcetype, index, linecount, _time, _raw, and splunk_server are present on every event, plus search-time fields eventtype and tag.
Named capture group
In Splunk regex, (?<fieldname>pattern) creates a field named fieldname holding the text matched by pattern; used with rex and field transform stanzas.
rex command
rex field=_raw "user=(?<user>\w+)" extracts fields at search time using named groups; max_match=0 returns all matches instead of only the first.
Calculated field
A search-time field defined by an eval expression in props.conf as EVAL-fieldname; it is computed when used and is never stored in the index.
Field alias
A search-time mapping giving an existing field an additional name, so searches can use either name without altering raw data or index-time fields.
Multivalue field
A single field holding multiple values for one event; use mvcount, mvexpand, mvjoin, or values() in stats to count, expand, join, or collect them.
Non-capturing group
(?:pattern) groups alternation or quantifiers without creating a captured field; unnamed parentheses in Splunk regex do not create fields unless named.
Transforming command
stats, chart, timechart, top, and rare convert events into a results table; commands needing raw events, such as rex or transaction, cannot follow them.
stats count by
stats count by host groups events by each distinct host value and returns one row per group containing the number of matching events.
timechart span
timechart divides _time into bins of the given span, such as span=1h, and returns one row per bin with one column per split-by series.
eventstats command
eventstats computes aggregates across all events and appends the result to every event, unlike stats, which discards the original events and returns only aggregate rows.
Dashboard token
A token is a variable such as $host_token$ set by a dashboard input and referenced in panel searches, letting inputs drive and link searches.
Report acceleration
A saved report whose results are precomputed into summary tsidx files, so later runs read the summaries instead of rescanning raw events.
Tag
A tag is a name applied to a specific field-value pair; searching tag=security returns events whose tagged field values include the security tag.
Event type
A saved search that labels matching events with a value of the eventtype field; searchable as eventtype=name and applied at search time.
CSV lookup
A lookup table stored as a comma-separated file, paired with a lookup definition, used by the lookup command or automatic lookups to add fields to events.
Automatic lookup
A props.conf setting named LOOKUP-name that runs a lookup against every event of a sourcetype at search time, adding the table's fields.
inputlookup command
inputlookup reads the contents of a lookup table file into the search pipeline as results, without searching any index or raw events.
Workflow action
A knowledge object that creates a link from a field value in an event to an external resource, either a GET URL or a POST form submission.
Root event dataset
The base dataset of a data model; its constraints filter events and its attributes become fields that Pivot and tstats can use.
Data model acceleration
Precomputes a data model into tsidx summary files so Pivot and tstats query summaries instead of raw events, greatly reducing search time.
tstats command
tstats queries accelerated data model summaries with syntax like | tstats count from datamodel=DM.Object by Object.field, avoiding raw event scanning.
Pivot
A Splunk interface that builds reports from a data model by applying filters, splitting rows and columns, and choosing an aggregation without writing SPL.
Child dataset
An object nested under a parent in a data model; it inherits the parent's constraints and adds its own, narrowing the set of events it represents.
summariesonly option
Setting summariesonly=true on tstats restricts results to time ranges that have already been accelerated, so unaccelerated periods return no data.

Splunk Power User study guide

Basic Searching and Search Under the Hood

What actually happens

When you run a search, the search head parses your string into search terms, dispatches to indexers, and each indexer scans time-ordered buckets using bloom filters and the tsidx term dictionary to find candidate events before any command runs. Because most fields are extracted at search time, only default fields exist when the search begins: host, source, sourcetype, index, _time, _raw, linecount, punct, and splunk_server. Everything else appears only after extraction, or because a command such as rex created it.

Search modes control extraction effort:

  • Fast - field discovery off; quickest, but many fields are missing from the sidebar.
  • Smart (default) - extracts the fields the search actually needs.
  • Verbose - extracts every field for every returned event.

Traps that show up in questions

AND is implicit, but AND/OR/NOT must be uppercase (or is treated as a keyword). NOT and != also return events where the field is absent; add field=* when the field must exist. Double quotes force exact-phrase matching and suppress wildcards, so "*error*" matches far less than *error*. Trailing wildcards (foo*) are cheap; leading wildcards (*foo) force a broad scan.

Worked example:

index=web sourcetype=access_combined status>=500 host=* NOT host=dev-* earliest=-4h

Index and sourcetype cut volume first, the time range bounds which buckets are read, the numeric comparison uses an extracted field, and host=* prevents the NOT clause from silently dropping events with no host.

Rule of thumb: filter with index/sourcetype/time first, keywords second, field comparisons third - each earlier step removes work for every later step. Search results live in a job that eventually expires, so use Save As if you need persistence, and the Job Inspector when a search is slow.

Fields, Field Extraction, and Regular Expressions

Layers of fields

Default fields are always present. Extracted fields appear at search time from props.conf rules for the sourcetype, from automatic lookups, or from commands like rex. The field sidebar splits Selected (used in your search), Interesting (common or unusual), and All fields.

Three mechanisms get confused constantly: a field alias (same value, new name), a calculated field (an eval expression evaluated at search time), and a lookup (an external table joined on a key). Index-time extraction is rarely appropriate - search-time extraction keeps flexibility and avoids reindexing.

Regex is the core skill

Named capture groups, (?<name>pattern), are what rex and the Field Extractor turn into fields; an unnamed group produces nothing. .* is greedy and will swallow text you wanted - prefer [^ ]+ or lazy .*?. Escape special characters (\. for a literal dot); \d is a digit, \w a word character, \s whitespace, and (?i) makes a pattern case-insensitive. rex matches anywhere in the string, so anchor with ^ and $ only when you mean it. Use rex field=<otherfield> to run regex against something besides _raw, and max_match=0 to capture every match.

Field names are case-sensitive; field values are matched case-insensitively by default.

Worked example:

| rex field=_raw "(?<method>[A-Z]+) (?<uri>/\S+) HTTP/\d\.\d"

This pulls the HTTP method and URI out of a web access log; a second rex with (?<status>\d{3}) grabs the response code.

Rule of thumb: prototype with inline rex (temporary, applies only to your job); once the pattern works, save it as a field extraction for the sourcetype so every user gets it.

Transforming Commands, Reports, and Dashboards

Transforming commands

Transforming commands turn a stream of events into a results table. The workhorses are stats, chart, timechart, top, rare, and contingency.

stats is the most flexible: | stats count, dc(user) AS users, avg(bytes) AS avg_bytes BY host collapses events into one row per host. count counts events; dc counts distinct values - using count where dc was meant is a classic trap. chart and timechart handle two dimensions: a chart split-by becomes columns, while timechart requires _time, uses a span (or bins) on the time axis, and caps series (default limit 10). top and rare return the top/rarest values of a field with countfield and percentfield; top defaults to 10 results.

If you need aggregates but must keep every event, use eventstats (aggregate added to each row) or streamstats (running/cumulative values in time order). Use bin or span to group _time; table and fields shape columns but are not transforming commands.

Reports and dashboards

A report is a saved search - optionally scheduled with cron, alerted on, and accelerated (report acceleration or summary indexing). Dashboards are XML classic dashboards or Dashboard Studio; both gain speed from a base search with post-process searches, and interactivity from tokens ($tok$) and drilldowns.

Worked example:

index=web status=500 | timechart span=1h count AS errors BY host limit=5

One row per hour, one column per host, series capped at five.

Rule of thumb: filter before transforming, transform as late as possible, and remember everything after a transforming command operates on the table, not on raw events.

Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

Shared, permissioned configuration

Knowledge objects are reusable configurations stored in an app context with private or shared (app/global) permissions. If another user cannot see your tag or lookup, permissions are almost always the answer.

Tags

A tag names a specific field/value pair - for example tagging sourcetype=access_combined as web. Search it like a field: tag=web, or combine tag=web tag=error. Tags exist only at search time and never alter indexed data.

Event types

An event type is a saved search whose matching events gain the field eventtype. Search eventtype=login_failure; list them with | eventtype. Event types can be tagged, assigned a priority, and reused by alerts and other knowledge objects.

Lookups

Lookups join external data at search time. A lookup definition (transforms.conf) points at a CSV file or a KV Store collection; an automatic lookup is wired to a sourcetype in props.conf and runs on every event, so keep those small. Commands: | lookup file.csv key OUTPUTNEW newfield, inputlookup to read a whole table, outputlookup to write results back. OUTPUT overwrites existing fields; OUTPUTNEW only fills fields that do not already exist - a favorite exam trap.

Workflow actions

Workflow actions add links or POSTs to the event Actions menu. They are configured as GET, POST, or search, may reference event values with $field$ tokens, can be restricted by app and role, and appear only when the triggering field has a value in that event.

Worked example:

index=sales | lookup products.csv product_id OUTPUTNEW product_name

Enriches events without clobbering a product_name that extraction already produced.

Rule of thumb: default to OUTPUTNEW unless you deliberately want to overwrite existing values.

Data Models, Pivot, and Acceleration

Data models

A data model is a structured, hierarchical description of your data: a root event (constraints such as index and sourcetype), child objects, and fields that can be extracted, eval-based, lookup-based, or regex-based. Inspect one with | datamodel Web Web search (returns the generated SPL) or | datamodel Web Web flat (returns field names). Models are edited under Settings > Data Models.

Pivot

Pivot is the point-and-click UI over a data model: add filters, split rows and columns, add column values, and Splunk builds the SPL. A Pivot does not require acceleration, but it is slow on large data unless the model is accelerated. Pivot elements can be saved as reports and edited later.

Acceleration

Data model acceleration (DMA) builds tsidx summaries in the index for a whole data model, so child objects inherit acceleration. Accelerated data is queried with tstats, which reads summaries only:

| tstats count FROM datamodel=Web.Web BY Web.host, Web.status

Use summariesonly=true to force tstats to answer solely from summaries and expose gaps. Fields created by eval or lookup inside the data model usually are not in summaries, so filtering on them can fail or return partial counts.

Worked example - compare before trusting:

| tstats count FROM datamodel=Web.Web WHERE Web.status=500 BY Web.host

vs. index=web sourcetype=access_combined status=500 | stats count BY host over the same window. A mismatch usually means the acceleration time window does not cover the range, or a non-summary field was used.

Rule of thumb: DMA is for repeated dashboards over large data; raw searches are for one-off deep dives.

Splunk Power User cheat sheet

Quick reference

Basic Searching and Search Under the Hood

  • The search head parses SPL, dispatches the job, and merges results; indexers search their local buckets. Streaming commands (search, eval, where, rex) are distributed to indexers, while transforming commands (stats, chart, timechart) run on the search head.

  • Bucket lifecycle: hot (writable) -> warm -> cold -> frozen (deleted) -> thawed (restored from archive). A hot bucket rolls to warm when maxDataSize is reached; the auto setting is roughly 750MB on small systems and 10GB otherwise.

  • Every bucket carries a time range, so the indexer skips any bucket whose range does not overlap the search's earliest/latest values before reading events.

  • The lexicon maps terms to the buckets containing them, .tsidx files hold term-to-event postings, and bloom filters let the indexer rule out buckets that definitely lack a term.

  • Job states progress queued -> parsing -> running -> finalizing -> done; a job with no activity is cancelled after 10 minutes by default (TTL is configurable and can be extended).

  • A subsearch in square brackets runs before the outer search and is capped by default at 10,000 results (maxout) and 60 seconds (maxtime); exceeding either truncates or terminates it.

  • Search modes: Smart performs field discovery only for fields the search needs, Fast disables field discovery for non-required fields, Verbose extracts every field and returns all matching events.

  • The UI returns a maximum of 10,000 events and exports return up to 50,000 by default; use fields, table, or head to keep result sets small.

  • The time range picker applies an implicit filter on _time; _indextime records when the event was indexed and differs from the event's own _time value.

Quick reference

Fields, Field Extraction, and Regular Expressions

  • Always-present fields: host, source, sourcetype, index, _time, _raw, linecount, splunk_server, plus search-time eventtype and tag.

  • Named capture groups (?pattern) create a field; (?:pattern) is non-capturing; unnamed parentheses group but do not produce a Splunk field.

  • Regex tokens: \d digit, \w [A-Za-z0-9_], \s whitespace, . any character except newline, * zero or more, + one or more, ? zero or one, {n,m} range, [^abc] negated class; * is greedy, *? is lazy.

  • rex field=_raw "user=(?\w+)" extracts at search time; max_match=0 returns every match, and mode=sed performs a substitution instead of extraction.

  • extract with kvdelim/pairdelim parses delimited key-value pairs, spath parses JSON and XML, multikv parses tabular raw events into fields.

  • props.conf search-time settings: REPORT- names an extraction stanza, EVAL- defines a calculated field, LOOKUP- adds an automatic lookup, FIELDALIAS- renames a field.

  • Field aliases, calculated fields, and most extractions are search-time only: raw data and index-time fields are never modified.

  • Multivalue handling: values() and list() in stats, plus mvcount, mvexpand, mvjoin, makemv, and split; sort order depends on whether values are treated as numeric.

  • where evaluates an eval expression against extracted fields, whereas search matches keywords and wildcards; a leading wildcard in search prevents efficient term lookup.

Quick reference

Transforming Commands, Reports, and Dashboards

  • Transforming commands -- stats, chart, timechart, top, rare, contingency -- collapse events into a results table; afterward only result-set commands (sort, head, where, eval, dedup) may follow, not rex or transaction.

  • stats count by host, sourcetype returns one row per distinct combination; common functions are count, dc, sum, avg, min, max, values, list, median, perc95, earliest, latest.

  • chart over by builds a matrix; timechart by bins _time using span=auto or an explicit span such as span=1h.

  • timechart and chart default to roughly 10 series unless limit is raised; useother and usenull control how remaining series and null values appear.

  • eventstats appends the aggregate to every event without removing events; streamstats computes running or cumulative values; neither is a transforming command.

  • Accelerated reports must be saved searches that use a transforming command; summaries are written as tsidx files and reused on later runs of the same report and time range.

  • Simple XML dashboards nest or -> -> -> <chart|table|single> -> , where holds the SPL and / set the panel time range.

  • Dashboard inputs (time range picker, dropdown, text box) set tokens such as $tok$ that panel searches reference; blocks with and chain inputs together.

  • A base search plus post-process searches lets several panels share one search; the base search must be a transforming or reporting search and is referenced by id.

Quick reference

Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

  • Tags attach to a specific field-value pair, never to raw text alone; tag= returns events whose tagged field values carry that tag, and tags are applied at search time from tags.conf.

  • An event type is a saved search string stored in eventtypes.conf that assigns a value to the eventtype field; the field is multivalue when several event types match one event.

  • Lookup workflow: place the .csv lookup table file, create a lookup definition (transforms.conf), then call it with | lookup def field OUTPUT newfield or automatically via props.conf LOOKUP-.

  • lookup match types are exact (default), CIDR for IP ranges, and glob; a nonexistent key returns null unless the definition specifies a default match value.

  • inputlookup reads a lookup table file into the pipeline as results; outputlookup writes results back to the file, and append=t preserves existing rows.

  • KV store lookups keep rows in an app's KV store collection, support larger and updatable datasets, and are defined with collections.conf plus a transforms stanza.

  • Workflow actions attach a link to field values in events: GET actions build a URI with $field$ substitution, POST actions submit form fields; they are configured with label, fields, and link.uri.

  • Macros are reusable SPL fragments invoked as name(arg1,arg2) and defined in macros.conf; arguments are referenced as $arg1$, and iseval=1 makes the macro usable inside eval expressions.

  • Knowledge object permissions are private (owner), shared in an app, or global (all apps); scheduled searches and dashboards only see objects available in their app context.

Quick reference

Data Models, Pivot, and Acceleration

  • A data model is a hierarchy of datasets: a root event, search, or transaction dataset, with child datasets that inherit and add constraints; attributes become usable fields.

  • Dataset types: event datasets constrain raw events, search datasets start from an arbitrary base search or table, and transaction datasets are built with the transaction command.

  • Constraints filter events on fields such as index, sourcetype, host, and _time; children inherit all parent constraints, narrowing the event set further down the tree.

  • Data model acceleration precomputes a dataset into tsidx summary files, so Pivot and tstats read summaries instead of raw events; only accelerated datasets support summariesonly=true.

  • tstats syntax: | tstats count from datamodel=DM.Object by Object.field, optionally with where, prestats=true plus a following stats, and fields or rename for shaping output.

  • Pivot elements are filters (constrain events), split rows, split columns, and column values (the aggregation); a saved Pivot can become a report or a dashboard panel without writing SPL.

  • Acceleration is bounded by the configured acceleration time range, so data outside that window is not summarized and returns no tstats results when summariesonly=true.

  • Acceleration jobs are scheduled and run by the search head that owns the data model, writing summaries that consume indexer disk space and are rebuilt as new data arrives.

  • tstats against accelerated summaries is typically far faster than the equivalent raw search because it reads only term and statistic postings, not raw events.

Splunk Power User key terms

Search Head

The Splunk component that handles user interaction: it runs searches, manages knowledge objects, and distributes search work to indexers. Users connect to it through the web interface or CLI to run SPL searches.

Related: Indexer, Universal Forwarder
Indexer

The Splunk component that receives and stores incoming data in indexes and performs retrieval and processing of that data at search time. It builds and searches buckets of raw events.

Related: Search Head, Bucket
Universal Forwarder

A lightweight Splunk agent installed on a source machine that collects local data and sends it to an indexer or heavy forwarder. It does not parse or index data itself.

Related: Indexer, Search Head
SPL (Search Processing Language)

The query language used in Splunk to retrieve and manipulate events. A search is a series of commands joined by pipe characters, where each command passes its results to the next.

Related: Subsearch, Transforming Command
Subsearch

A search enclosed in square brackets that runs first inside another search. Its results feed into the outer search, typically supplying values for a filter or an IN clause.

Related: SPL (Search Processing Language), Search Job Inspector
Search Job Inspector

A debugging and performance panel for a completed search. It shows execution costs, search duration, result counts, messages, and which phases of the job consumed the most time.

Related: Search Mode
Search Mode

A setting controlling how much processing Splunk performs to produce results. Fast returns only the fields needed, Verbose returns all fields and event data, and Smart balances the two automatically.

Related: Search Job Inspector
Bucket

The physical directory where an indexer stores a slice of index data, such as a range of events by time. Buckets move through hot, warm, cold, and frozen states as data ages.

Related: Indexer
Field

A searchable name/value pair in an event, such as host=web01 or status=404. Fields let you filter, group, and calculate on data instead of reading raw text.

Related: Field Extraction, Named Capture Group
Field Extraction

The process of teaching Splunk to pull a value out of raw event text and assign it a field name. Extraction can be automatic, regex-based, delimiter-based, or defined in a data model.

Related: Regular Expression (Regex), Named Capture Group
Regular Expression (Regex)

A pattern language for matching text. In Splunk it appears in commands such as rex, inside field extraction definitions, and in search filters to locate and capture specific substrings.

Related: Named Capture Group, rex
Named Capture Group

A regex subpattern written as (?...) that saves the matched text into a field with that name. Named groups let one pattern produce several usable fields at once.

Related: Regular Expression (Regex), rex
rex

A search command that extracts fields from raw event text using a regular expression at search time. It is often used for quick, one-off extractions or to test a pattern.

Related: Regular Expression (Regex), Named Capture Group
erex

A command that helps you build a regular expression by supplying example values. Splunk generates a candidate pattern that matches your examples, which you can then refine.

Related: rex, Regular Expression (Regex)
Multivalue Field

A single field that holds more than one value for an event, such as several IP addresses. Values can be counted with mvcount, expanded with mvexpand, or filtered with mvfilter.

Related: eval, Field
eval

A command that creates or overwrites fields by calculating expressions, using functions for string, numeric, time, and conditional operations. It adds computed fields without removing existing ones.

Related: Field, Multivalue Field
Transforming Command

A command that turns individual events into a summary result set, such as a table of counts by host. After a transforming command, the results are no longer raw events.

Related: stats, timechart
stats

A transforming command that aggregates events into summary rows using functions such as count, sum, avg, and dc, grouped by one or more fields through the by clause.

Related: Transforming Command, timechart
timechart

A transforming command that produces a table of aggregated values over time, with time on the x-axis. It is the standard way to build trending charts in reports and dashboards.

Related: stats, Dashboard
dedup

A command that removes duplicate events based on the values of one or more fields, keeping the first or last occurrence. It is useful for finding unique combinations of values.

Related: Transforming Command, stats
Report

A saved search with a defined set of results, often displayed as a table or chart. Reports can be scheduled, shared, and added to dashboards as panels.

Related: Dashboard, Base Search
Dashboard

A collection of panels that display saved searches, reports, or charts side by side, usually with input controls. Dashboards give users a quick visual overview of data.

Related: Report, Token
Token

A placeholder variable in a dashboard whose value is set by an input or a drilldown and then substituted into panel searches. Tokens make dashboards interactive.

Related: Dashboard, Base Search
Base Search

A shared search that runs once in a dashboard and is reused by several panels, which then apply their own post-processing. It reduces load by avoiding repeated identical searches.

Related: Dashboard, Report
Tag

A short keyword attached to field/value pairs so searches can refer to them by a friendly name, like tag=web. Tags group related values without changing the underlying data.

Related: Event Type, Workflow Action
Event Type

A saved definition that categorizes events by a search string, letting you label and group similar events. Event types can be used in searches and are often paired with tags.

Related: Tag, Macro
Lookup Table

A file or KV store collection holding reference data, such as a CSV of hostnames and owners. Splunk can join that data to events at search time using the lookup command.

Related: Lookup Definition, Automatic Lookup
Lookup Definition

A knowledge object that tells Splunk where a lookup table lives, which fields it contains, and how those fields should be matched to fields in your events.

Related: Lookup Table, Automatic Lookup
Automatic Lookup

A lookup configured to run automatically whenever events containing its match fields are searched, adding the lookup's fields without an explicit lookup command in the search.

Related: Lookup Definition, Lookup Table
Workflow Action

A knowledge object that adds a clickable link to field values in search results, typically opening an external URL or running another search. It is defined per field.

Related: Tag, Field Alias
Macro

A reusable block of SPL stored under a name and inserted into searches with backtick syntax, optionally with arguments. Macros keep complex search logic consistent and easier to maintain.

Related: Event Type, Field Alias
Field Alias

A knowledge object that makes one field name refer to another, so searches can use either name. Aliases help normalize data where different sources use different field names.

Related: Macro, Workflow Action
Data Model

A structured, hierarchical description of data in terms of datasets, fields, and constraints. Data models make data easier to search and are the foundation for Pivot and acceleration.

Related: Dataset, Pivot, Data Model Acceleration
Dataset

A named node within a data model that defines a set of events or search results, such as a root event dataset or a child dataset narrowed by additional constraints.

Related: Data Model, Constraint
Constraint

A filter attached to a data model dataset that limits which events belong to it, usually by field values. Child datasets inherit and add to the constraints of their parent.

Related: Dataset, Data Model
Pivot

A point-and-click interface for building reports and charts from a data model without writing SPL. Users pick a dataset, split rows by fields, and add aggregated values.

Related: Data Model, Data Model Acceleration
Data Model Acceleration

A setting that precomputes a data model's statistics in the background so Pivot and tstats searches return results much faster, at the cost of disk space and processing.

Related: Pivot, tstats
tstats

A command that queries indexed fields and accelerated data models directly instead of raw events. It is much faster than a normal search when the needed fields are indexed or accelerated.

Related: Data Model Acceleration, Summary Index
Summary Index

An index that stores the results of a scheduled report so later searches can read the precomputed results instead of rescanning raw events. It is a manual form of acceleration.

Related: tstats, Data Model Acceleration

Splunk Power User study plan

8 weeks · About 7 hours per week

Week 1

Basic Searching and Search Under the Hood

  • Diagram the three phases a search job passes through (search head parse/dispatch, indexer, search head merge) and state which phase each of five given commands executes in.

  • Run the same query in fast, smart, and verbose mode and record the differences in returned fields and runtime.

  • Rewrite five inefficient searches by tightening the time range, replacing leading wildcards, and adding indexed-field filters first.

  • Use the Job Inspector to read scanCount, runTime, and searchProviders for a slow search and name the dominant cost.

  • Build three subsearches and one OR-based alternative for the same result, then compare their runtimes.

Your checkpoint

A two-page search-lifecycle cheat sheet plus a table of 10 executed searches listing runtime, scanned events, and the one change you made to speed each up.

Week 2

Basic Searching and Search Under the Hood & Fields, Field Extraction, and Regular Expressions

  • Distinguish default, indexed, and custom fields by inspecting the same event with the fields command and the interesting-fields sidebar.

  • Use fieldsummary and the field picker to shortlist which fields are worth extracting from a new sourcetype.

  • Write rex expressions with named capture groups that extract three previously unextracted values from raw event text.

  • Validate each new extraction with erex and confirm the match rate across at least 100 events.

  • Explain the difference between search-time extraction via rex and knowledge-object field extractions, and pick the right one for a repeated need.

Your checkpoint

Three working rex expressions saved as field extractions, each with a measured match rate over 100+ events and a one-line note on why the pattern is anchored the way it is.

Week 3

Fields, Field Extraction, and Regular Expressions

  • Construct at least ten regular expressions from scratch covering character classes, quantifiers, alternation, anchors, and non-capturing groups.

  • Use sed mode in rex to substitute values in place and explain when sed mode is preferable to a plain capture.

  • Handle multivalue fields with mvexpand, nomv, and mvcount in three searches that depend on splitting correctly.

  • Use coalesce to merge two sparse fields into one reliable field and demonstrate the fallback order with sample output.

  • Diagnose three broken regexes (greedy overreach, unescaped metacharacter, missing anchor) and state the minimal fix for each.

Your checkpoint

A personal regex reference card of 10 self-written patterns, each shown with a matching and a non-matching sample string, plus the three repaired broken patterns with their fixes.

Week 4

Fields, Field Extraction, and Regular Expressions & Transforming Commands, Reports, and Dashboards

  • Convert five event-level searches into transforming pipelines that return only aggregated rows.

  • Use stats with multiple by-clauses and compare the output shape against eventstats and streamstats for the same data.

  • Build a timechart with a span that produces a readable number of columns and adjust it when the span is wrong.

  • Replace a slow wildcard filter with a field-extraction-plus-where filter and measure the runtime difference.

Your checkpoint

Three saved reports built on transformed output (one stats, one timechart, one top-plus-lookup), each under a documented runtime budget.

Week 5

Transforming Commands, Reports, and Dashboards

  • Assemble a dashboard with at least four panels drawn from your saved reports and confirm each panel loads independently.

  • Add a form input whose token filters every panel, and prove the token reaches each panel's search.

  • Use appendcols or append deliberately in one panel and justify why a join was not used.

  • Apply a chart overlay or split-by to one panel and verify the field ordering is correct.

  • Trim each panel's base search to the minimum fields and time range it needs.

Your checkpoint

A four-panel dashboard with one token-driven input and a short build note explaining the search behind each panel and its runtime.

Week 6

Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions

  • Define two event types from saved searches and apply them so they appear in the event-type field on matching events.

  • Design a tag taxonomy of at least six tags and apply them to three field-value pairs, then search by tag to prove reuse.

  • Build a CSV lookup, upload it, and wire it as an automatic lookup that enriches events without an explicit lookup command.

  • Create two workflow actions, one GET and one POST, and pass a field token into the URI.

  • Document the permission and app context each new knowledge object lives in.

Your checkpoint

A knowledge-object inventory listing two event types, six tags, one automatic lookup, and two workflow actions, with the exact search that proves each one works and its sharing scope.

Week 7

Data Models, Pivot, and Acceleration

  • Build a data model with a root event dataset and at least two child datasets constrained by different filters.

  • Add a calculated field to the data model and confirm it is usable in Pivot without a rex at search time.

  • Turn on acceleration for the data model and verify the acceleration summary shows a completed backfill.

  • Build a Pivot with three split-by rows and one column split, then compare its result to the equivalent stats search.

  • Explain when acceleration is skipped and identify one constraint that would prevent it.

Your checkpoint

An accelerated data model with two child datasets and a Pivot table whose output matches a hand-written stats search row for row, plus the acceleration summary captured after backfill.

Week 8

Basic Searching and Search Under the Hood & Fields, Field Extraction, and Regular Expressions & Transforming Commands, Reports, and Dashboards & Knowledge Objects: Tags, Event Types, Lookups, and Workflow Actions & Data Models, Pivot, and Acceleration

  • Take a timed 60-question practice exam spanning all five domains and score each domain separately.

  • Re-run every earlier deliverable without notes and repair anything that fails.

  • Rewrite your weakest ten missed questions as corrected flashcards with the reasoning, not just the answer.

  • Rebuild one dashboard panel and one data model from memory to confirm retention.

Your checkpoint

A scored 60-question practice exam with per-domain results, a remediation log of every miss, and all eight prior deliverables re-verified from memory.

Milestones

Week 2: Extract three fields from raw events with self-written rex and hit at least 90% match rate on 100+ events without consulting a reference.

Week 4: Score 80% or better on a self-made 30-question quiz covering domains 1 and 2, and convert any event-level search into a transforming search on demand.

Week 6: Demonstrate a working automatic lookup and a token-passing workflow action from a cold search bar, with no notes.

Week 8: Score 85% or better overall on the 60-question practice exam with no domain below 75%, and every earlier deliverable reproduced from memory.

Splunk Power User exam day

Your checklist

Government-issued photo ID

Bring the original (not a photocopy) of a valid photo ID. The name on the ID must match the name on your registration closely enough for the proctor to accept it; if your registration name differs, contact the provider before exam day to correct it. Confirm the exact list of accepted ID types with the provider - it varies by country.

Appointment confirmation and registration details

Have your confirmation email, candidate/registration ID, and the exact appointment time in the provider's stated time zone available. Double-check AM/PM and time-zone conversion the day before.

Working webcam, microphone, and speakers/headset

If you are taking the exam online with a remote proctor, your equipment must pass the provider's system check. Confirm with the provider whether headsets are permitted or whether standalone speakers are required.

Stable internet connection plus a backup

Wired or strong Wi-Fi for the primary connection, and a phone hotspot or second network as a fallback. A dropout mid-exam may be handled differently depending on the provider's policy - confirm what happens if you disconnect.

A quiet, private, well-lit room

No other people, no interruptions, desk surface cleared of papers, books, phones, and second screens unless the provider explicitly allows them. Proctors commonly ask for a 360-degree room scan, so remove anything you would not want inspected.

Laptop with power adapter, fully charged

Plug in rather than relying on battery. Close all other applications, notifications, and messaging clients before launching the exam.

Completed system/equipment test

Run the provider's pre-exam system test at least 24 hours ahead so you have time to fix camera, browser, or firewall issues. Confirm which browser version is supported.

Written-down provider support contact

Keep the provider's technical support phone number or chat link on a separate device or on paper, in case the exam session fails to launch.

Confirm the permitted-materials and scratch-paper policy

Do not assume pen and paper, a whiteboard, or notes are allowed. Confirm with the provider in advance what (if anything) you may use for scratch work and whether an on-screen notepad is provided.

Confirm exam logistics: question count, time limit, and passing score

These details can change between exam versions. Look up the current blueprint on the certification provider's official page on the day you schedule, and write the numbers down so you can pace yourself.

Confirm break rules and restroom plan

Break availability and whether the clock stops during a break differ between online-proctored and test-center delivery. Confirm with the provider, and plan hydration and restroom use accordingly.

A light review sheet of Splunk concepts you keep confusing

One page maximum: search command syntax families you mix up, field-extraction vs. field-lookup distinctions, eval/rex/transaction behavior, knowledge-object permission scoping, and report/dashboard acceleration terms. Review only - do not attempt to bring it into the exam.

Plan the day

72 hours before

Re-read the official exam blueprint domain by domain and score yourself honestly on each. Spend the remaining study time only on the weakest two or three domains. Take one timed practice set under exam-like conditions to calibrate pacing.

72 hours before

Log in to the testing provider's portal, verify the appointment date, time, and time zone, and re-read the candidate agreement and technical requirements page. Confirm ID requirements and permitted materials now, while there is still time to ask questions.

72 hours before

Run the system/equipment test on the exact machine and network you will use on exam day. Fix anything that fails - browser version, camera permissions, firewall, antivirus pop-ups - immediately rather than the night before.

24 hours before

Do a light pass only: skim your one-page review sheet and any command-syntax notes. Stop active studying early. Cramming new material the night before tends to increase errors rather than fix gaps.

24 hours before

Prepare the room: clear the desk, remove papers and extra devices, position the camera so the door behind you is visible, and tell household members not to enter or knock during your time slot.

24 hours before

Lay out your photo ID, laptop, charger, and the provider's support contact. Set two alarms. Get a normal night's sleep - do not trade sleep for one more practice set.

Morning of

Eat and hydrate normally. Avoid heavy caffeine if you are already anxious. Do not start a new topic; at most re-read your one-page sheet for ten minutes.

Morning of

Re-run the equipment check, restart the computer, close every background application, and disable notifications. Have your ID within arm's reach and your support number visible on a second device.

Morning of

Join the check-in several minutes before your appointment time - the provider's check-in, ID verification, and room scan take real time and are usually included in or precede your slot. Confirm the exact early-arrival window with the provider.

During the test

Read every question to the end before answering. Watch for qualifiers such as 'which is NOT', 'best', 'first', and 'least likely' - they flip the answer more often than the technical content does.

During the test

Answer what you know first and flag anything slow or ambiguous. Do not let one hard question consume several minutes; return to flagged items after you have cleared the rest.

During the test

Pace against the clock: divide the total time by the number of questions to get a per-question budget and check your position at the halfway mark. Leave a few minutes at the end to revisit flags and confirm you have no unanswered items.

During the test

On multi-part or exhibit-style item stems, restate the requirement in your own words before evaluating options - many distractors are technically true but do not satisfy the stated requirement.

After the test

Note which domains the exam actually emphasized while it is fresh, and confirm how and when your score is reported. If you did not pass, check the provider's retake waiting period and policy before rescheduling.

Rules to check

  • Bring valid government-issued photo ID in the original form; the name must match your registration. If your documents do not match, you may be refused entry and the fee may not be refunded - confirm the accepted documents with the provider beforehand.

  • Do not bring or use unauthorized materials - notes, second monitors, phones, smart watches, or reference cards - unless the provider's published policy explicitly permits them. Assume nothing is allowed until you have confirmed it.

  • Expect identity verification and a room or environment scan at check-in for online-proctored delivery. Keep the desk clear and comply with proctor instructions immediately; refusal to follow proctor direction can result in session termination.

  • No outside help of any kind, and no capturing or sharing exam content. Most certification programs require you to accept a non-disclosure and candidate agreement; violating it can void your result and bar you from future exams regardless of your score.

  • Break rules differ between online-proctored and test-center delivery, and the clock may keep running. Confirm with the provider whether breaks are permitted and whether they are timed, and plan accordingly rather than assuming.

  • Scoring policies - including the passing score, whether questions are weighted, and whether unanswered items count as incorrect - are set by the provider and can change. Verify the current numbers from the official source, not from forum posts.

  • If your session disconnects or the platform fails, do not keep troubleshooting silently. Contact provider support immediately and get a case or ticket number; the resolution and rescheduling policy depends on the provider, so confirm the specifics with them.

  • Check the retake policy and any waiting period before exam day so you know your options. Do not count on an immediate retake - confirm the rules with the provider rather than relying on memory or hearsay.

Splunk Power User FAQ

How many Splunk Power User practice questions are available?

The practice set has 200 Splunk Power User questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many Splunk Power User flashcards are available?

The flashcard set has 32 Splunk Power User cards. Each card shows the term and its definition.

Which topics does the Splunk Power User study material cover?

The Splunk Power User study material has 5 sections, including Basic Searching and Search Under the Hood, Fields, Field Extraction, and Regular Expressions, and Transforming Commands, Reports, and Dashboards.

What format facts does the catalog list for the Splunk Power User exam?

The catalog lists these item types: multiple choice for the Splunk Power User exam.