SNOW-CAD Integrating and managing application data Practice Question
A large enterprise uses a scheduled import to retrieve order data from an external ERP system every night at 2 AM. The import runs a REST API call that returns JSON data, which is processed by an Import Set Row and a Transform Map to populate the custom table 'u_order'. Recently, the import completed with errors: some orders were not imported, and the error log shows 'Record already exists' for those orders. However, when the developer checks the 'u_order' table, the referenced orders do not exist. The developer reviews the Import Set Row and finds that the 'Coalesce' field is set to 'u_order_number', but further investigation reveals that the 'u_order_number' field is not unique in the table; multiple records can have the same order number because they are from different regions. The Transform Map is configured with 'On Success' = 'Update'. What is the best course of action to resolve the issue?
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
✓
Modify the Coalesce field to use a combination of fields (e.g., order number and region) that uniquely identifies each record, or create a dedicated unique identifier.
The coalesce field must uniquely identify records to avoid false positive matches. Using a combination of fields (e.g., order number and region) ensures each record is uniquely identified. Option A would cause duplicates if the same logical order is reimported. Option B would also cause duplicates because coalesce is disabled. Option D does not address the root cause of incorrect matching.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Remove the Coalesce field from the Transform Map so that duplicate detection is disabled.
Why it's wrong here
Removing coalesce would cause every import to insert a new record, even if a record with the same logical key already exists, resulting in duplicates.
- ✗
Change the 'On Success' action on the Transform Map to 'Insert' to ensure all incoming records are treated as new.
Why it's wrong here
This would cause duplicate records if the same order is imported again, leading to data integrity issues.
- ✓
Modify the Coalesce field to use a combination of fields (e.g., order number and region) that uniquely identifies each record, or create a dedicated unique identifier.
Why this is correct
A unique coalesce field ensures that the system correctly matches existing records, preventing false 'already exists' errors and allowing proper updates.
- ✗
Increase the frequency of the scheduled import to run every hour so that errors are minimized.
Why it's wrong here
Frequency does not fix the matching logic; errors would persist regardless of timing.
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.