SPLK-1001 Practice Test 3 — 10 Questions

Question 1

A team uses a lookup to map IP addresses to geographic locations. The lookup is large and updated weekly. Which lookup type is best suited?

Accepted Answer

File-based CSV lookup. A file-based CSV lookup is best suited for this use case because it is static, large, and updated on a schedule. CSV lookups are loaded into memory and can handle large datasets efficiently, and they are easily replaced or updated weekly by overwriting the file. This approach avoids the overhead of a KV store or external service for a dataset that does not require real-time updates or complex queries.

Answer

External lookup

Answer

Scripted lookup

Answer

KV store lookup

Question 2

Which of the following is a default field that is automatically extracted by Splunk?

Accepted Answer

`host`. The `host` field is a default field that Splunk automatically extracts from every event, typically derived from the hostname of the machine that generated the data. It is one of the three default fields (along with `source` and `sourcetype`) that Splunk uses to categorize and search events, and it is always available without any custom field extraction or configuration.

Answer

`department`

Answer

`error_code`

Answer

`user_id`

Question 3

Which TWO of the following commands can be used to create a new field from existing fields?

Accepted Answer

rex. The `rex` command is correct because it uses regular expressions to extract new fields from existing field values. For example, `rex field=message "(?<newField>pattern)"` creates a new field named `newField` by matching a portion of the `message` field. This allows you to derive structured data from unstructured or semi-structured fields.

Answer

table

Answer

convert

Answer

fields

Question 4

Which of the following is the default time range in a new Splunk search?

Accepted Answer

All time. When you open a new search in Splunk, the default time range is set to 'All time' (no time filter), meaning the search will scan all indexed data unless you explicitly specify a time range. This is because Splunk defaults to showing all available events to avoid inadvertently excluding data, and it is the user's responsibility to narrow the search scope.

Answer

Last 24 hours

Answer

Last 7 days

Answer

Real-time

Question 5

A security team uses a KV Store lookup to track threat intelligence indicators (IPs, domains) with a field 'indicator' and a field 'threat_type'. They regularly update the KV Store with new indicators. The team notices that searches using the lookup are very slow when the KV Store contains over 100,000 entries. They want to improve lookup performance without losing the ability to update frequently. Which approach should they take?

Accepted Answer

Add an index on the 'indicator' field in the KV Store collection to speed up lookup queries. Adding an index on the 'indicator' field in the KV Store collection allows Splunk to perform faster lookups by using a B-tree or similar index structure, reducing the need for a full collection scan. This directly addresses the performance degradation seen with over 100,000 entries while still supporting frequent updates, as indexes are maintained dynamically.

Answer

Split the KV Store into multiple smaller KV Stores based on threat_type

Answer

Convert the KV Store to a CSV file and use the lookup command

Answer

Increase the memory allocation for the Splunk search head

Question 6

A user wants to see the list of all fields that are extracted from a specific sourcetype. Which command should they use?

Accepted Answer

| fieldsummary. The `fieldsummary` command provides a summary of all fields extracted from the events in the search results, including their count, distinct count, and percentage of events containing each field. When applied to a specific sourcetype, it lists every field that has been extracted from that sourcetype, making it the correct tool for this task.

Answer

| rex field=_raw ...

Answer

| fields *

Answer

| eval fields=...

Question 7

A small business uses Splunk to monitor their web server. They have a dashboard that shows daily page views. After a system update, the dashboard loads very slowly, often timing out. The dashboard uses a search that takes only 2 seconds when run manually. The dashboard has a time range picker set to 'Today'. The update changed some default settings. What is the most likely cause?

Accepted Answer

The time range picker default was reset to 'All Time'. The dashboard was configured with a time range picker set to 'Today', but the system update reset the default to 'All Time'. This causes the search to scan all indexed data, dramatically increasing the data volume and search time, leading to timeouts. A manual search taking 2 seconds on a small time range becomes extremely slow when applied to the entire dataset, which is why the dashboard fails while the manual search still works.

Answer

The index was renamed

Answer

The dashboard now uses real-time search

Answer

The search command changed to 'timechart'

Question 8

Refer to the exhibit. The user wants to display the count over time for each source. However, the chart shows only one line labeled 'MyCount'. What is the problem?

Accepted Answer

The `rename` command after `timechart` renames incorrectly; `timechart count by source` creates multiple fields, and `rename count as "MyCount"` does not rename them.. `timechart count by source` generates separate fields for each source value (e.g., `count: source1`, `count: source2`), not a single field named `count`. The subsequent `rename count as "MyCount"` fails to match any existing field, so the chart displays only one line labeled `MyCount` (which is actually a null or default aggregation). To rename all source-specific count fields, you must use a wildcard or rename each field individually.

Answer

The index name is misspelled.

Answer

The `timechart` command should not have `by source`.

Answer

The chart type is line chart by default.

Question 9

Refer to the exhibit. The search returns no results from the lookup. What is the most likely issue?

Accepted Answer

The lookup command references 'error_id' but the alias changed the field to 'error_code'. The search uses `lookup error_codes.csv error_id` but the FIELDALIAS in props.conf has renamed the field `error_id` to `error_code`. Since the lookup command references the original field name `error_id`, which no longer exists in the events after alias processing, the lookup cannot match any values and returns no results.

Answer

The FIELDALIAS syntax is incorrect

Answer

The lookup table is not defined in transforms.conf

Answer

The lookup file 'error_codes.csv' does not exist

Question 10

Which command is used to import an external CSV file into a Splunk lookup table for the first time?

Accepted Answer

`| outputlookup`. The `| outputlookup` command is used to create or overwrite a lookup table file in Splunk from search results. When importing an external CSV file into a Splunk lookup table for the first time, you would first ingest the CSV data (e.g., via `| inputcsv` or by uploading the file), then use `| outputlookup` to write that data into a lookup definition that Splunk can reference.

Answer

`| lookup`

Answer

`| inputlookup`

Answer

`| fields`