- A
Rename the 'username' field to 'user_id' using `rename username as user_id`
Why wrong: Renaming only renames an existing field; it does not populate user_id from the regex extraction.
- B
Use `eval user_id=mvindex(split(user_id+" "+username," "),0)` to combine the two fields
Why wrong: This approach is convoluted and may break if either field is missing; `coalesce` is simpler and more robust.
- C
Use `fillnull value=N/A user_id` to handle missing values
Why wrong: `fillnull` only replaces null values; it does not populate user_id from username.
- D
Use `eval user_id=coalesce(user_id, username)` to take the first non-null value
`coalesce` returns the first non-null value among the fields, effectively unifying the field.
Quick Answer
The correct answer is to use `eval user_id=coalesce(user_id, username)`. This approach works because the `coalesce` function returns the first non-null value from a list of fields, allowing you to combine fields from different extractions into a single unified field—perfect for scenarios where a regex extraction like `rex` might fail to capture a pattern, but a default extraction like `username` still exists. On the Splunk SPLK-1002 exam, this tests your understanding of how to handle missing or inconsistent field values when combining fields with coalesce, a common task when normalizing data from mixed log sources. A frequent trap is assuming `eval user_id=user_id OR username` works, but logical OR in `eval` treats non-null strings as true and can produce unexpected boolean results instead of field values. Remember the memory tip: “Coalesce catches the first non-null—like a safety net for missing fields.”
SPLK-1002 Using Fields and Lookups Practice Question
This SPLK-1002 practice question tests your understanding of using fields and lookups. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 security analyst is investigating a breach and needs to extract the 'user_id' field from raw log events. The logs contain both structured and unstructured data. The analyst uses the following search: `index=security sourcetype=syslog | rex field=_raw "user_id=(?<user_id>\w+)" | stats count by user_id`. However, some events do not contain the 'user_id' pattern, but they have a 'username' field extracted by a default extraction. The analyst wants to create a unified field 'user_id' that includes values from both. Which approach should the analyst take?
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
Use `eval user_id=coalesce(user_id, username)` to take the first non-null value
Option C is correct because using `coalesce` allows combining fields from different extractions into a single field. Option A is wrong because renaming only works if the field already exists, and the regex extraction may not always produce a value. Option B is wrong because the `eval` function with logical OR does not handle missing fields correctly. Option D is wrong because `fillnull` only replaces null values, not combine fields.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Rename the 'username' field to 'user_id' using `rename username as user_id`
Why it's wrong here
Renaming only renames an existing field; it does not populate user_id from the regex extraction.
- ✗
Use `eval user_id=mvindex(split(user_id+" "+username," "),0)` to combine the two fields
Why it's wrong here
This approach is convoluted and may break if either field is missing; `coalesce` is simpler and more robust.
- ✗
Use `fillnull value=N/A user_id` to handle missing values
Why it's wrong here
`fillnull` only replaces null values; it does not populate user_id from username.
- ✓
Use `eval user_id=coalesce(user_id, username)` to take the first non-null value
Why this is correct
`coalesce` returns the first non-null value among the fields, effectively unifying the field.
Related concept
Static NAT maps one inside address to one outside address.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
- Static NAT maps one inside address to one outside address.
- PAT allows many inside hosts to share one public address using ports.
- Inside local and inside global describe the private and translated addresses.
- NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
- Identify inside and outside interfaces first.
- Check whether the scenario needs static NAT, dynamic NAT or PAT.
- Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SPLK-1002 NAT questions on configuration and troubleshooting.
- →
Using Fields and Lookups — study guide chapter
Learn the concepts, then practise the questions
- →
Using Fields and Lookups practice questions
Targeted practice on this topic area only
- →
All SPLK-1002 questions
510 questions across all exam domains
- →
Splunk Core Certified User SPLK-1002 study guide
Full concept coverage aligned to exam objectives
- →
SPLK-1002 practice test guide
How to use practice tests most effectively before exam day
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.
Splunk Basics and Interface Navigation practice questions
Practise SPLK-1002 questions linked to Splunk Basics and Interface Navigation.
Basic Searching and Transforming Commands practice questions
Practise SPLK-1002 questions linked to Basic Searching and Transforming Commands.
Using Fields and Lookups practice questions
Practise SPLK-1002 questions linked to Using Fields and Lookups.
Creating Reports, Dashboards and Visualizations practice questions
Practise SPLK-1002 questions linked to Creating Reports, Dashboards and Visualizations.
Data Models and Best Practices practice questions
Practise SPLK-1002 questions linked to Data Models and Best Practices.
SPLK-1002 fundamentals practice questions
Practise SPLK-1002 questions linked to SPLK-1002 fundamentals.
SPLK-1002 scenario practice questions
Practise SPLK-1002 questions linked to SPLK-1002 scenario.
SPLK-1002 troubleshooting practice questions
Practise SPLK-1002 questions linked to SPLK-1002 troubleshooting.
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 — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Use `eval user_id=coalesce(user_id, username)` to take the first non-null value — Option C is correct because using `coalesce` allows combining fields from different extractions into a single field. Option A is wrong because renaming only works if the field already exists, and the regex extraction may not always produce a value. Option B is wrong because the `eval` function with logical OR does not handle missing fields correctly. Option D is wrong because `fillnull` only replaces null values, not combine fields.
What should I do if I get this SPLK-1002 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SPLK-1002 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 →
Last reviewed: Jun 24, 2026
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.
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.
Sign in to join the discussion.