Question 2 of 510
Using Fields and LookupshardMultiple ChoiceObjective-mapped

Quick Answer

The answer is a misconfiguration in props.conf for the intended sourcetype. When an automatic lookup works manually with the lookup command but fails at index time, the problem is almost always in the props.conf configuration—specifically, the TRANSFORMS directive is either missing, pointing to the wrong sourcetype like 'web_access', or has incorrect syntax. This is because automatic lookups require a transforms.conf stanza to define the lookup, and a props.conf stanza that correctly associates that transform with the exact sourcetype being indexed; if the sourcetype name in props.conf doesn’t match the data’s sourcetype, Splunk never applies the enrichment. On the SPLK-1002 exam, this tests your understanding of index-time field extraction versus search-time lookup commands, and the common trap is assuming a working manual lookup guarantees automatic enrichment. Remember the mnemonic: “Manual works, auto fails? Check your props and transforms trails.”

SPLK-1002 Using Fields and Lookups Practice Question

This SPLK-1002 practice question tests your understanding of using fields and lookups. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A company uses Splunk to monitor web server logs. They have a lookup table that maps IP addresses to geographic locations (city, country). The lookup is defined as a CSV file with fields: ip, city, country. The lookup definition is named 'geo'. The team wants to automatically add city and country to every web event at index time, so that all future searches have this enrichment without adding the lookup command. The team tries to set up an automatic lookup in props.conf for the sourcetype 'web_access', but the city and country fields still do not appear in the events. They verify that the lookup file exists and that the lookup definition works when used manually with the lookup command. What is the most likely cause of the automatic lookup not working?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

Question 1hardmultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

The automatic lookup definition in props.conf is not correctly configured for the intended sourcetype

Option D is correct because the automatic lookup definition in props.conf must be correctly configured for the intended sourcetype. The most common misconfiguration is specifying the wrong sourcetype or incorrect syntax in the TRANSFORMS directive, which prevents the lookup from being applied at index time. Since the lookup works manually, the issue is with the props.conf configuration, not the lookup file or definition itself.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Index-time lookups are not supported; enrichment can only be done at search time

    Why it's wrong here

    Splunk does support index-time lookups via automatic lookups in props.conf, though search-time is more common.

  • The lookup file must be in KV Store format for index-time lookups

    Why it's wrong here

    CSV files are acceptable for index-time lookups.

  • The lookup must be invoked with the 'lookup' command in the search to populate the fields

    Why it's wrong here

    Automatic lookups are designed to work without explicit commands.

  • The automatic lookup definition in props.conf is not correctly configured for the intended sourcetype

    Why this is correct

    If the props.conf stanza does not match the sourcetype, the lookup will not be applied.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume automatic lookups work identically to search-time lookups, but they require explicit configuration in props.conf and transforms.conf, and any syntax error or sourcetype mismatch will silently fail.

Trap categories for this question

  • Command / output trap

    Automatic lookups are designed to work without explicit commands.

Detailed technical explanation

How to think about this question

Index-time lookups in Splunk are implemented using the TRANSFORMS directive in props.conf, which references a transform in transforms.conf that specifies the lookup table and fields to add. The lookup file must be placed in the correct directory (e.g., $SPLUNK_HOME/etc/system/lookups or an app's lookups folder) and the transform must define the correct input and output fields. A common pitfall is forgetting to restart Splunk after modifying props.conf or transforms.conf, as these changes are not picked up dynamically.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the SPLK-1002 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SPLK-1002 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SPLK-1002 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SPLK-1002 question test?

Using Fields and Lookups — This question tests Using Fields and Lookups — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The automatic lookup definition in props.conf is not correctly configured for the intended sourcetype — Option D is correct because the automatic lookup definition in props.conf must be correctly configured for the intended sourcetype. The most common misconfiguration is specifying the wrong sourcetype or incorrect syntax in the TRANSFORMS directive, which prevents the lookup from being applied at index time. Since the lookup works manually, the issue is with the props.conf configuration, not the lookup file or definition itself.

What should I do if I get this SPLK-1002 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This SPLK-1002 practice question is part of Courseiva's free Splunk certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SPLK-1002 exam.