SNOW-CAD Platform Features and Integration Practice Question
A developer needs to import CSV data into a custom table using Import Sets. The data contains a reference field to a user record. Which configuration ensures that the user record is correctly matched?
⚠ Common exam trap
Watch out — candidates often confuse 'coalesce' with a field that must be set on the source field (Option B) or think that a script is always required for reference resolution (Option D), when in fact the coalesce field is a declarative, target-side configuration that handles matching automatically.
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
✓
Set the target field 'email' as coalesce on the transform map.
Setting the 'email' field as a coalesce field on the transform map tells the Import Set engine to use that field to match incoming records against existing target table records. When the reference field points to a user record, the coalesce field (e.g., email) is used to look up the sys_user table and automatically populate the correct sys_id, ensuring the reference is properly resolved without manual scripting.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Set the target field 'email' as coalesce on the transform map.
Why this is correct
Using a unique identifier like email as coalesce ensures proper matching.
- ✗
Set the source field as coalesce on the transform map.
Why it's wrong here
Coalesce is set on the target field, not source field.
- ✗
Configure the import set row to be ignored if the user is not found.
Why it's wrong here
This would skip the row without matching, not correct for reference resolution.
- ✗
Use a script in the 'on before' transform script to find the user.
Why it's wrong here
Using an 'on before' transform script to find the user record fails because Import Sets require a dedicated **coalescence field** or **exact match condition** defined on the table map to automatically link incoming data to existing records; a script alone cannot establish the persistent matching rule that the import engine uses for deduplication. This approach is tempting because 'on before' scripts are commonly employed to populate or transform field values before the record is written, and they would be correct if the goal were to derive a user's sys_id from a lookup table rather than to define the matching criterion itself.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every SNOW-CAD question from scratch — 481 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SNOW-CAD practice question is part of Courseiva's free ServiceNow 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 SNOW-CAD exam.