The answer is an invalid or non-existent caller_id sys_id. A 201 Created response confirms the REST API call was syntactically correct and the server accepted the payload, but the incident record is not visible because ServiceNow silently fails to resolve the caller_id reference against the sys_user table during creation. This means the record is stored but lacks a valid user link, causing it to be filtered out of standard views or default queries. On the ServiceNow Certified Application Developer CAD exam, this scenario tests your understanding of reference field validation and silent failures—a common trap where candidates assume a 201 status guarantees a fully functional record. Remember that ServiceNow creates the record even with a bad reference, but the record becomes orphaned and hidden. Memory tip: “201 doesn’t mean visible—check your references.”
SNOW-CAD Platform Features and Integration Practice Question
This SNOW-CAD practice question tests your understanding of platform features and integration. 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.
Refer to the exhibit. A developer is making a REST API call to create an incident. The call returns a 201 Created response, but the incident record is not visible in the instance. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The 'caller_id' sys_id is invalid or points to a non-existent user.
A 201 Created response indicates the REST API call was syntactically correct and the server accepted the payload, but the incident record is not visible. The most likely cause is an invalid caller_id sys_id, because ServiceNow validates the caller_id field against the sys_user table during record creation. If the sys_id does not exist or is malformed, the record is created but the caller_id reference fails silently, often causing the record to be hidden from standard views or filtered out by default queries.
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.
✓
The 'caller_id' sys_id is invalid or points to a non-existent user.
Why this is correct
An invalid sys_id can cause the record to be created without proper assignment, possibly hidden.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The request method should be PUT instead of POST.
Why it's wrong here
POST is correct for creating records.
✗
The field 'short_description' is misspelled.
Why it's wrong here
It is correctly spelled.
✗
The instance has an ACL that prevents creating incidents via REST.
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume a 201 Created response guarantees the record is fully functional and visible, but ServiceNow's reference validation can silently fail, leaving the record orphaned and hidden from standard views.
Detailed technical explanation
How to think about this question
ServiceNow's REST API for table records (e.g., /api/now/table/incident) performs a GlideRecord insert() operation. When a reference field like caller_id contains an invalid sys_id, the insert succeeds but the reference is not resolved, leaving the field empty or with a broken link. This can cause the record to be excluded from list views that filter by caller or from reports, even though the record exists in the database. In production, this often happens when an integration passes a hardcoded or outdated sys_id from a different environment.
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 security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
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.
Platform Features and Integration — This question tests Platform Features and Integration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The 'caller_id' sys_id is invalid or points to a non-existent user. — A 201 Created response indicates the REST API call was syntactically correct and the server accepted the payload, but the incident record is not visible. The most likely cause is an invalid caller_id sys_id, because ServiceNow validates the caller_id field against the sys_user table during record creation. If the sys_id does not exist or is malformed, the record is created but the caller_id reference fails silently, often causing the record to be hidden from standard views or filtered out by default queries.
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: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.