SNOW-CSA Reporting, SLA and Imports Practice Question
A large import set of 10,000 user records from an HR system is failing intermittently during transformation to the sys_user table. Some rows are inserted successfully, but others show errors in the import log: 'Transform script error: null reference at line 15 of the transform map script.' The administrator reviews the transform map and finds a script that sets the department field by looking up a department table. The script assumes the department code always exists in the department table, but some records have codes that are not present. The administrator needs to ensure all rows are imported reliably, even if some data is missing. What is the best course of action?
⚠ Common exam trap
Watch out — candidates often choose to skip rows with null values (Option D) instead of handling the missing data gracefully, failing to recognize that the requirement is to import all rows reliably, not just those with complete data.
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
✓
Fix the transform script to check for the existence of the department code before using it, and set a default value or skip the field if not found. Then use an Import Set Row condition to only process rows that are valid.
It directly addresses the root cause: the transform script fails when a department code is missing from the reference table. By adding a null check before using the lookup result and providing a default or skipping the field, the script becomes resilient to missing data. Using an Import Set Row condition then ensures that only rows with valid department codes are processed, preventing the intermittent null reference errors while still importing all other rows successfully.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a 'Run as GlideRecord' operation in the transform map to ensure each row is processed individually.
Why it's wrong here
'Run as GlideRecord' is a database operation, not a transform map feature; it does not exist.
- ✗
Create a separate import set for each user record to isolate failures.
Why it's wrong here
This is impractical and does not address the underlying data issue.
- ✓
Fix the transform script to check for the existence of the department code before using it, and set a default value or skip the field if not found. Then use an Import Set Row condition to only process rows that are valid.
Why this is correct
This addresses the root cause by handling missing data in the script, and the row condition ensures only rows with sufficient data are transformed.
- ✗
Add a condition to skip rows that have null values in the department field.
Why it's wrong here
Skipping rows with null department would still not fix the null reference error if the department code is present but not found; the error occurs during lookup.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SNOW-CSA question from scratch — 504 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-CSA 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-CSA exam.