SPLK-1002 Splunk Core Certified Power User Exam Free Practice Exam Questions (2026 Updated)

The Field Extractor Utility (FX) is a tool that helps you extract fields from your events using a graphical interface or by manually editing the regular expression2. The FX has a button that displays events that do not contain extracted fields, which is the Non-Matches button2. The Non-Matches button shows you the events that do not match the regular expression that you have defined for your field extraction2. This way, you can check if your field extraction is accurate and complete2. Therefore, option B is correct, while options A, C and D are incorrect because they are not buttons that display events that do not contain extracted fields.

The timeline is a graphical representation of your search results that shows the distribution of events over time2. You can use the timeline to zoom in or out of a specific time range or to select one or more bars on the timeline to filter your results by that time range2. However, these actions will not re-run the search, but rather refine the existing results based on the selected time range2. Therefore, options B, C and D are correct, while option A is incorrect because zooming out will re-run the search with a broader time range.

The time range specified for a historical search defines the amount of data fetched from the index matching that time range2. A historical search is a search that runs over a fixed period of time in the past2. When you run a historical search, Splunk searches the index for events that match your search string and fall within the specified time range2. Therefore, option B is correct, while options A and C are incorrect because they are not what the time range defines for a historical search.

The Splunk Common Information Model (CIM) provides a methodology to normalize data from different sources and source types. The CIM defines a common set of fields and tags for different types of data, such as web, network, email, etc. This allows you to search and analyze data from different sources in a consistent way.

Splunk event types are based on search strings that cannot contain pipes or subsearches.

Extract: “Event type search strings must not contain a pipe (|) and cannot include transforming or filtering commands.”

Thus, only option B is a valid event type definition because it is a simple base search without pipelines or subsearches.

The correct answer is A. | where 10yearAnnerversary=Renewal-MonthYear.

The where command is used to filter the search results based on an expression that evaluates to true or false. The where command can compare two fields, two values, or a field and a value. The where command can also use functions, operators, and wildcards to create complex expressions1.

The syntax for the where command is:

| where < expression >

The expression can be a comparison, a calculation, a logical operation, or a combination of these. The expression must evaluate to true or false for each event.

To compare two fields with the where command, you need to use the field names without any quotation marks. For example, if you want to find events where the values for the 10yearAnnerversary field match the values for the Renewal-MonthYear field, you can use the following syntax:

| where 10yearAnnerversary=Renewal-MonthYear

This will return only the events where the two fields have the same value.

The other options are not correct because they use quotation marks around the field names, which will cause the where command to interpret them as string values instead of field names. For example, if you use:

| where ‘10yearAnnerversary’=‘Renewal-MonthYear’

This will return no events because there are no events where the string value ‘10yearAnnerversary’ is equal to the string value ‘Renewal-MonthYear’.

The Splunk Common Information Model (CIM) Add-on is a foundational component for many Splunk apps, providing a common framework for data normalization and field extraction. This add-on includes a set of pre-configured data models that are essential for consistent reporting, searching, and correlation across various types of data. These data models help standardize field names and event structures, ensuring that data from disparate sources can be queried in a uniform way. While the CIM Add-on facilitates the use of standardized sourcetypes and supports data validation, the primary feature it offers is the set of pre-configured data models which are crucial for maintaining consistency across different datasets.

A chart is a graphical representation of your search results that shows the relationship between two or more fields2. You can display a chart in stack mode by changing the Stack Mode option in the Format menu2. Stack mode allows you to stack multiple series on top of each other in a chart to show the cumulative values of each series2. Therefore, option C is correct, while options A, B and D are incorrect because they are not ways to display a chart in stack mode.

The explanation is as follows:

The transaction command is used to find transactions based on events that meet various constraints12.

Transactions are made up of the raw text (the _raw field) of each member, the time and date fields of the earliest member, as well as the union of all other fields of each member1.

The startswith option is used to define the first event in a transaction by specifying a search term or an expression that matches the event13.

For example, | transaction clientip JSESSIONID startswith="view" will create transactions based on the clientip and JSESSIONID fields, and the first event in each transaction will contain the term “view” in the _raw field2.

When using the Field Extractor (FX) tool in Splunk and the tool fails to extract a value from all appropriate events, there are specific steps you can take to improve the extraction process. These steps involve interacting with the FX tool and possibly adjusting the extraction method:

A. Select an additional sample event with the Field Extractor (FX) and highlight the missing value in the event. This approach allows Splunk to understand the pattern better by providing more examples. By highlighting the value in another event where it wasn't extracted, you help the FX tool to learn the variability in the data format or structure, improving the accuracy of the field extraction.

D. Edit the regular expression manually. Sometimes the FX tool might not generate the most accurate regular expression for the field extraction, especially when dealing with complex log formats or subtle nuances in the data. In such cases, manually editing the regular expression can significantly improve the extraction process. This involves understanding regular expression syntax and how Splunk extracts fields, allowing for a more tailored approach to field extraction that accounts for variations in the data that the automatic process might miss.

Options B and C are not typically related to improving field extraction within the Field Extractor tool. Re-ingesting data (B) does not directly impact the extraction process, and changing to a delimited extraction method (C) is not always applicable, as it depends on the specific data format and might not resolve the issue of missing values across events.

The correct answer is D. Search.

A workflow action is a knowledge object that enables a variety of interactions between fields in events and other web resources. Workflow actions can create HTML links, generate HTTP POST requests, or launch secondary searches based on field values1.

There are three types of workflow actions that can be set up using Splunk Web: GET, POST, and Search2.

GET workflow actions create typical HTML links to do things like perform Google searches on specific values or run domain name queries against external WHOIS databases2.

POST workflow actions generate an HTTP POST request to a specified URI. This action type enables you to do things like creating entries in external issue management systems using a set of relevant field values2.

Search workflow actions launch secondary searches that use specific field values from an event, such as a search that looks for the occurrence of specific combinations of ipaddress and http_status field values in your index over a specific time range2.

Therefore, the workflow action type that performs a secondary search is Search.

To create a tag, the user must have the tag capability associated with their user role. The tag capability allows the user to create, edit, and delete tags. The user does not need to identify a field:value pair, have the Power role, or be able to edit the sourcetype the tag applies to.ReferencesSee Define and manage tags in Settings and [About capabilities] in the Splunk Documentation.

Event types allow users to assign labels to events based on predefined search strings. This helps categorize data and makes it easier to reference specific sets of events in future searches.

The transaction command is used to group events that are related by some common fields or conditions, such as start/end values, time span, or pauses. The stats command is used to calculate statistics on a group of events by a common field value.

References

Splunk Community

Splunk Transaction - Exact Details You Need

The Splunk Common Information Model (CIM) is a collection of data models that apply a common structure and naming convention to data from any source. A data model is a type of knowledge object that defines the structure and relationships of fields in a dataset. A data model can have one or more datasets, which are subsets of the data model that represent different aspects of the data. For example, the Network Traffic data model has datasets such as All Traffic, DNS, HTTP, etc. The CIM contains 28 pre-configured data models that cover various domains such as authentication, network traffic, web, email, etc. The CIM is implemented as an add-on that contains the JSON files for the data models, documentation, and tools that support the consistent, normalized treatment of data for maximum efficiency at search time23

1: Splunk Core Certified Power User Track, page 10. 2: Splunk Documentation, Overview of the Splunk Common Information Model 1. 3: Splunkbase, Splunk Common Information Model (CIM) 2.