SNOW-CAD Creating and customizing tables and data Practice Question
A ServiceNow administrator is responsible for setting up a custom table called 'u_incident_change' to track incidents that require a change request. Each 'u_incident_change' record must be linked to exactly one incident and one change request. The administrator creates two reference fields: 'incident_ref' pointing to the 'Incident' table, and 'change_ref' pointing to the 'Change Request' table. However, after deployment, users report that when they create a new 'u_incident_change' record from an incident form (using a related list), the 'incident_ref' field is automatically populated, but the 'change_ref' field is empty. The users want to be able to create a change request directly from that same form and have the reference automatically filled. What configuration should the administrator use to achieve this?
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
✓
Create a UI Action labeled 'Create Change Request' on the incident form that runs a script to create a new 'u_incident_change' record with both references populated and then opens the change request form
A UI Action with a script creates the change request and sets the reference fields accordingly. Option B is wrong because referenced records don't auto-populate. Option C is wrong because business rules run on records, not UI. Option D is wrong because related lists don't create records with cross-reference.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a UI Action labeled 'Create Change Request' on the incident form that runs a script to create a new 'u_incident_change' record with both references populated and then opens the change request form
Why this is correct
This UI Action can script the creation of the change request and the junction record, setting both references, and provide a seamless user experience.
- ✗
Configure the related list to automatically create the 'u_incident_change' record with both references when a change request is added
Why it's wrong here
Related lists do not have built-in behavior to create junction records with cross-references; this requires scripting.
- ✗
Use a business rule on the 'u_incident_change' table that auto-populates the 'change_ref' when the record is created from a related list
Why it's wrong here
Business rules can auto-populate fields, but they cannot create a change request record automatically without additional logic.
- ✗
Add a reference field on the Incident table that points to the 'u_incident_change' table
Why it's wrong here
This would create a one-to-many relationship in the wrong direction and does not automate the creation of the change request.
Go deeper
Related to this question
About these practice questions
This SNOW-CAD question is part of Courseiva's 481-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.