Splunk Core Certified Power User (SPLK-1002) — Free Practice Questions
10 free sample questions from a bank of 273, with the correct answers and explanations. No signup required — start practising right now.
1Which one of the following statements about the search command is true?
It does not allow the use of wildcards.
It treats field values in a case-sensitive manner.
It can only be used at the beginning of the search pipeline.
It behaves exactly like search strings before the first pipe.
Answer: D
The short version
D — D states search-command equivalence correctly. search command mirrors pre-pipe search strings. The search command filters events exactly like implicit search strings before the first pipe, applying the same keyword and field-value matching.
Key concepts in this question
Implicit search: Text before the first pipe is an implied search that trims the event set before transforming commands.
Explicit search: Writing search mid-pipeline reapplies the same filtering logic to the current result set.
Syntax parity: Both forms share wildcard and field matching rules, making them interchangeable for filtering.
Why D is correct
The search command filters events exactly like implicit search strings before the first pipe, applying the same keyword and field-value matching. It does allow wildcards, is case-insensitive for values, and can appear later in the pipeline, not only at the start. The settled key therefore follows documented search-language behaviour.
Why the others are wrong
A. claims wildcards are disallowed, but asterisk and similar wildcards work in both implicit and explicit search.
B. claims case-sensitive values, while Splunk matching is case-insensitive for field values in this scope.
C. claims beginning-only use, but search can filter after pipes unlike the initial implicit clause.
SPLK-1002 exam tip
Treat explicit search as a repeatable pre-pipe filter anywhere in the pipeline.
2Which of the following statements would help a user choose between the transaction and stats commands?
stats can only group events using IP addresses.
The transaction command is faster and more efficient.
There is a 1000 event limitation with the transaction command.
Use stats when the events need to be viewed as a single correlated event.
Answer: C
The short version
C — C contrasts transaction limits correctly. transaction caps at 1000 events while stats scales. Transaction groups raw events into correlated multi-event records but is memory heavy and carries a 1000-event default limit, while stats aggregates by fields far more efficiently at scale.
Key concepts in this question
Transaction cost: Building event groups holds raw records in memory, constraining scale and speed.
Stats efficiency: Stats computes aggregates without preserving every raw event, scaling to large sets.
Limit signal: Hitting the 1000-event cap is a cue to prefer stats unless true event grouping is required.
Why C is correct
Transaction groups raw events into correlated multi-event records but is memory heavy and carries a 1000-event default limit, while stats aggregates by fields far more efficiently at scale. Stats is not limited to IPs, transaction is not faster, and single correlated views suit transaction rather than stats. The settled key therefore follows performance and limit guidance.
Why the others are wrong
A. limits stats to IP grouping, but stats groups by any field combination, not only addresses.
B. claims transaction is faster, inverting the documented performance relationship.
D. recommends stats for single correlated views, which is the transaction use case, not stats.
SPLK-1002 exam tip
Hear 1000 limit plus efficiency and choose the stats versus transaction split.
3What is the correct syntax to find events associated with a tag?
tag: =
tags=
tags: =
tag=
Answer: D
The short version
D — D gives the settled tag syntax correctly. tag search uses tag equals value syntax. The settled key selects tag equals value as the correct syntax for finding events associated with a tag in this bank row.
Key concepts in this question
Tag abstraction: Tags label field values with friendly names that can be searched directly.
Syntax precision: Exam rows test exact operator spelling, so settled form governs over variant habits.
Event association: Searching the tag returns all events whose field values carry that tag.
Why D is correct
The settled key selects tag equals value as the correct syntax for finding events associated with a tag in this bank row. Other spellings with plural tags or extra colons do not match the decided form, even though real-world search may accept variants. The explanation upholds the already settled mapping without proposing alternatives. In practice verify tags with the datasets viewer so searches use names actually defined in your environment.In service operation this distinction guides triage, routing, and audit evidence, so applying the settled rule consistently reduces rework and failed reviews.
Why the others are wrong
A. uses a colon-equals variant that the settled key does not select for this row.
B. uses plural tags without the settled operator form.
C. uses plural tags with colon spacing that differs from the decided syntax.
SPLK-1002 exam tip
For tag rows memorize the settled equals form rather than improvising variants.
4Which of the following is true about the Splunk Common Information Model (CIM)?
The CIM contains 28 pre-configured datasets.
The data models included in the CIM are configured with data model acceleration turned on.
The data models included in the CIM are configured with data model acceleration turned off.
The CIM is an app that needs to run on the indexer.
Answer: C
The short version
C — C states CIM acceleration default correctly. CIM data models ship with acceleration off. The Common Information Model ships data models with acceleration turned off by default, requiring admins to enable it per model based on volume and search needs.
Key concepts in this question
Model library: CIM provides normalized data models spanning many sourcetypes with hundreds of datasets via the add-on.
Acceleration cost: Enabling acceleration builds summaries that speed searches but consume storage and schedule resources.
Default off: Leaving acceleration off lets sites opt in selectively after sizing rather than paying cost everywhere.
Why C is correct
The Common Information Model ships data models with acceleration turned off by default, requiring admins to enable it per model based on volume and search needs. It contains far more than 28 datasets, and it is not an indexer-only app. The settled key therefore follows CIM administration defaults.
Why the others are wrong
A. counts 28 datasets, understating the hundreds of preconfigured datasets in the CIM add-on.
B. claims acceleration on by default, which would impose unplanned summary cost across all models.
D. calls CIM an indexer app, but it is a knowledge model layer used at search time, not an indexer process.
SPLK-1002 exam tip
Recall CIM as models with acceleration off until you enable it.
5Consider the following search run over a time range of last 7 days:
index=web sourcetype=access_combined | timechart avg(bytes) by product_name
Which option is used to change the default time span so that results are grouped into 12 hour intervals?
timespan=12
span=12h
timespan=12h
span=12
Answer: B
The short version
B — B buckets with span 12h correctly. span with hours buckets timechart into 12-hour groups. Timechart grouping is controlled by span, and span equals 12h aggregates the 7-day index web data into 12-hour buckets for average bytes by product.
Key concepts in this question
Span role: Span defines bucket duration for time-based aggregation in timechart and chart.
Unit need: Suffix h denotes hours, so 12h means twelve-hour windows rather than seconds or generic counts.
Averaging context: Avg bytes by product per bucket reveals product traffic rhythms over the week.
Why B is correct
Timechart grouping is controlled by span, and span equals 12h aggregates the 7-day index web data into 12-hour buckets for average bytes by product. Timespan is not the timechart bucket parameter, and bare numbers without units miss the hour granularity. The settled key therefore follows timechart syntax.
Why the others are wrong
A. uses timespan without h handling, which is not the timechart bucket control in this scope.
C. uses timespan with hours, mixing parameter names and missing the span keyword the command expects.
D. uses span without a unit, leaving duration ambiguous instead of explicit 12-hour buckets.
SPLK-1002 exam tip
Need time buckets in timechart, write span equals value plus time unit.
6When would transaction be used instead of stats?
To have a faster and more efficient search.
To see results of a calculation.
To group events based on start/end values.
To group events based on a single field value.
Answer: C
The short version
C — C reserves transaction for start-end grouping correctly. transaction stitches start-end event groups. Transaction is chosen over stats when events must be grouped by start and end boundary values into session-like records preserving duration and span.
Key concepts in this question
Boundary grouping: Start and end markers define sessions that stats rows cannot reconstruct as single entities.
Stats contrast: Stats aggregates by field values but discards sequence and duration context within groups.
Cost acceptance: Analysts accept transaction overhead only when session semantics are required.
Why C is correct
Transaction is chosen over stats when events must be grouped by start and end boundary values into session-like records preserving duration and span. Faster searches and single-field counts favour stats, while calculations alone do not require event stitching. The settled key therefore follows grouping-requirement mapping.
Why the others are wrong
A. claims faster efficiency, but transaction is heavier than stats and is never chosen for speed.
B. seeks calculation results, which stats computes more efficiently without session stitching.
D. groups by a single field value, which stats handles natively without transaction overhead.
SPLK-1002 exam tip
Hear start and end values and pick transaction over stats.
7Given the following eval statement:
... | eval field1 = if(isnotnull(fieid1),field1,0), field2 = if(isnull
Which of the following is the equivalent using fillnull?
C — C translates conditional nulls to fillnull correctly. chained fillnull with per-field defaults matches eval logic. The eval sets field1 to zero when not null logic applies and field2 to NO-VALUE when null, and the settled fillnull chain reproduces those per-field defaults in sequence.
Key concepts in this question
Eval null test: Isnull and isnotnull branches assign different defaults per field based on presence.
Fillnull mapping: Chained fillnull statements can set distinct defaults per field in order.
Order matter: Applying field1 default before field2 preserves the eval sequence semantics.
Why C is correct
The eval sets field1 to zero when not null logic applies and field2 to NO-VALUE when null, and the settled fillnull chain reproduces those per-field defaults in sequence. Claiming no equivalent ignores fillnull field-specific defaults, while bundled values or single-value forms misapply defaults across fields. The settled key therefore follows null-handling equivalence.
Why the others are wrong
A. claims no equivalent exists, but per-field fillnull chains can express the same defaults.
B. bundles both fields under one values list, misaligning which default belongs to which field.
D. applies value zero broadly or misorders fields, breaking the per-field default mapping.
SPLK-1002 exam tip
Translate per-field if-null evals to chained fillnull one field at a time.
8The Splunk Common Information Model (CIM) is a collection of what type of knowledge object?
Saved searches
Lookups
KV Store
Data models
Answer: D
The short version
D — D types CIM knowledge objects correctly. CIM is a collection of data models. The Common Information Model is fundamentally a collection of data models that normalize fields across sources for consistent searching.
Key concepts in this question
Data model role: Data models define hierarchical datasets with fields and constraints for accelerated or guided search.
CIM purpose: Standardized models let many apps share field names for security, network, and app domains.
Object contrast: Searches execute logic, lookups enrich, and stores persist, none of which defines the CIM collection itself.
Why D is correct
The Common Information Model is fundamentally a collection of data models that normalize fields across sources for consistent searching. Saved searches, lookups, and KV stores are separate knowledge objects with different roles. The settled key therefore follows Splunk knowledge taxonomy.
Why the others are wrong
A. names saved searches, which store query text rather than the normalized model collection.
B. names lookups, which map values for enrichment instead of defining CIM datasets.
C. names KV store, which persists app state rather than modeling CIM hierarchies.
SPLK-1002 exam tip
Expand CIM as data models on sight for taxonomy questions.
9How is a Search Workflow Action configured to run at the same time range as the original search?
Select the "Use the same time range as the search that created the field listing" checkbox.
Set the earliest time to match the original search.
Select the same time range from the time-range picker.
Select the "Overwrite time range with the original search" checkbox.
Answer: A
The short version
A — A aligns workflow action time correctly. same-time-range checkbox inherits originating search window. Selecting Use the same time range as the search that created the field listing makes the workflow action run with identical earliest and latest bounds as the originating search.
Key concepts in this question
Time inheritance: Dynamic inheritance keeps drill-through results consistent even when the parent window changes.
Manual risk: Hard-coding times diverges as soon as the parent search window is edited.
Listing context: Field listings carry their parent time context, which the checkbox reuses automatically.
Why A is correct
Selecting Use the same time range as the search that created the field listing makes the workflow action run with identical earliest and latest bounds as the originating search. Manually matching times or picker ranges is error-prone and does not dynamically inherit. The settled key therefore follows workflow-action configuration.
Why the others are wrong
B. sets earliest manually, which snapshots one bound and misses dynamic latest alignment.
C. picks the same range in the picker, which duplicates values without live inheritance.
D. names a similarly worded overwrite option that is not the settled checkbox label for this row.
SPLK-1002 exam tip
Need same time as parent search, tick the inherit-time checkbox.
10A calculated field is a shortcut for performing repetitive, long, or complex transformations using which of the following commands?
transaction
eval
lookup
stats
Answer: B
The short version
B — B shortcuts repetitive eval correctly. calculated fields wrap eval transformations. A calculated field stores a reusable eval expression that performs repetitive, long, or complex transformations automatically at search time.
Key concepts in this question
Eval core: Eval computes new or replacement field values with functions and conditionals.
Reuse benefit: Calculated fields apply the same eval logic across many searches without rewriting.
Command contrast: Other commands shape event sets rather than defining persistent field formulas.
Why B is correct
A calculated field stores a reusable eval expression that performs repetitive, long, or complex transformations automatically at search time. Transaction, lookup, and stats serve grouping, enrichment, or aggregation rather than field-expression reuse. The settled key therefore follows field-management definitions.
Why the others are wrong
A. names transaction, which groups events into sessions rather than defining reusable field math.
C. names lookup, which enriches with external tables instead of evaluating expressions.
D. names stats, which aggregates rows rather than deriving per-event calculated values.
SPLK-1002 exam tip
Link calculated field plus repetitive transform to eval.