The answer is to use GlideRecord with newRecord() and set values, then call insert() within the same Business Rule. This is correct because it ensures the new 'task' record is created in the same database transaction as the current record, guaranteeing atomicity—if the insert fails, the entire transaction rolls back, preventing orphaned records. The reference field linking back to the current record is set synchronously before the insert, maintaining data integrity. On the ServiceNow Certified Application Developer CAD exam, this tests your understanding of transaction boundaries and the GlideRecord insert in same transaction concept, often appearing as a trap where developers mistakenly use a separate asynchronous Business Rule or a Flow. A common memory tip is "newRecord before insert, same transaction keeps it tight"—think of it as building the record in the same sandbox before the save.
SNOW-CAD Core Application Development Practice Question
This SNOW-CAD practice question tests your understanding of core application development. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 developer needs to create a record in the 'task' table when a specific condition is met in a Business Rule. The new record should be linked back to the current record via a reference field. What is the best practice to ensure the new record is created in the same transaction?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use GlideRecord with newRecord() and set values, then call insert().
Option A is correct because using GlideRecord with newRecord() and insert() within the same Business Rule ensures the new 'task' record is created in the same database transaction as the current record. This guarantees atomicity: if the insert fails, the entire transaction rolls back, preventing orphaned records. The reference field linking back to the current record is set synchronously before the insert, maintaining data integrity.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 GlideRecord with newRecord() and set values, then call insert().
Why this is correct
This is the standard way to create records in the same transaction within a Business Rule.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use Flow Designer to create the record asynchronously.
Why it's wrong here
Flow Designer actions are asynchronous and run in a different transaction, which may cause timing issues.
✗
Use the GlideRecord updateMultiple() method.
Why it's wrong here
updateMultiple() updates existing records, not inserts new ones.
✗
Call a Scripted REST API to insert the record.
Why it's wrong here
Using a REST API is inefficient and also runs in a separate transaction.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think asynchronous methods like Flow Designer are 'best practice' for decoupling, but the question explicitly requires same-transaction creation, which only synchronous GlideRecord insert provides.
Detailed technical explanation
How to think about this question
Under the hood, GlideRecord insert() uses the platform's internal database abstraction layer to execute an INSERT SQL statement within the current database transaction context. The Business Rule runs in the same transaction as the triggering record's save operation, so any GlideRecord insert performed here is automatically part of that transaction. A real-world scenario is creating a follow-up task when a high-priority incident is raised; if the task insert fails, the incident should not be saved, preventing incomplete data.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the SNOW-CAD exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Core Application Development — This question tests Core Application Development — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use GlideRecord with newRecord() and set values, then call insert(). — Option A is correct because using GlideRecord with newRecord() and insert() within the same Business Rule ensures the new 'task' record is created in the same database transaction as the current record. This guarantees atomicity: if the insert fails, the entire transaction rolls back, preventing orphaned records. The reference field linking back to the current record is set synchronously before the insert, maintaining data integrity.
What should I do if I get this SNOW-CAD question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
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.
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.
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.