- A
Add a check in the integration script to query the incident table for an existing incident with the same external ticket ID before creating a new one.
This ensures that duplicates are prevented at creation time by checking a unique external ID field.
- B
Modify the integration to only create incidents if the ticket status is 'New'.
Why wrong: The status may not indicate uniqueness; the same ticket could still be returned with status 'New' multiple times.
- C
Increase the scheduled job interval to run every 2 hours.
Why wrong: This reduces frequency but does not prevent duplicates when the same ticket is returned in separate runs.
- D
Add a post-processing script that deletes duplicate incidents after each run.
Why wrong: This is inefficient and could cause data loss if legitimate duplicates are deleted.
Quick Answer
The answer is to add a check in the integration script that queries the incident table for an existing record with the same external ticket ID before creating a new one. This is correct because it directly addresses the root cause of duplicate incidents: the scheduled job’s failure to verify existing records before insertion. By using a GlideRecord lookup on a field storing the third-party system’s unique identifier, the script can conditionally skip creation when a match is found, making the integration idempotent regardless of the external system’s caching behavior. On the ServiceNow Certified Application Developer CAD exam, this scenario tests your understanding of integration best practices and the GlideRecord API, often appearing as a trap where candidates might mistakenly try to fix the third-party system or add a duplicate check after creation. The key insight is that preventing duplicates requires a proactive lookup before the insert, not a reactive cleanup. Memory tip: “Look up before you write up” — always query for the external ID first to keep your incidents unique.
SNOW-CAD Integrating and managing application data Practice Question
This SNOW-CAD practice question tests your understanding of integrating and managing application data. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 company has a ServiceNow instance integrated with a third-party ticket management system. The integration runs every hour via a scheduled job that calls a REST API to fetch new tickets and create incidents in ServiceNow. The administrator notices that some incidents are being created as duplicates. Investigation reveals that the third-party system sometimes returns the same ticket in multiple API calls due to caching. The scheduled job does not check for existing incidents before creating new ones. The administrator needs to modify the integration to prevent duplicate incidents without relying on the third-party system to change its behavior. Which action should the administrator take?
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
Add a check in the integration script to query the incident table for an existing incident with the same external ticket ID before creating a new one.
Option A is correct because the most reliable way to prevent duplicates is to check the incident table for an existing record with the same external ticket ID before creating a new incident. This leverages the unique identifier from the third-party system and avoids relying on the third-party's caching behavior. By querying the incident table using a GlideRecord lookup on a field that stores the external ID, the script can conditionally skip creation if a match is found.
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.
- ✓
Add a check in the integration script to query the incident table for an existing incident with the same external ticket ID before creating a new one.
Why this is correct
This ensures that duplicates are prevented at creation time by checking a unique external ID field.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Modify the integration to only create incidents if the ticket status is 'New'.
Why it's wrong here
The status may not indicate uniqueness; the same ticket could still be returned with status 'New' multiple times.
- ✗
Increase the scheduled job interval to run every 2 hours.
Why it's wrong here
This reduces frequency but does not prevent duplicates when the same ticket is returned in separate runs.
- ✗
Add a post-processing script that deletes duplicate incidents after each run.
Why it's wrong here
This is inefficient and could cause data loss if legitimate duplicates are deleted.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates might choose Option D (delete duplicates after creation) because it seems like a quick fix, but the SNOW-CAD exam emphasizes preventing errors at the point of data entry rather than relying on post-processing cleanup, which can lead to data inconsistency and performance issues.
Detailed technical explanation
How to think about this question
Under the hood, the integration script should use a GlideRecord query with an encoded query like 'u_external_ticket_id=EXTERNAL_ID' to check for existing incidents. The external ticket ID should be stored in a dedicated field (e.g., u_external_ticket_id) with a unique index to enforce database-level uniqueness as a secondary safeguard. In real-world scenarios, caching layers like CDNs or API gateways can cause stale data to be served, making a proactive deduplication check essential for data integrity.
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.
- →
Integrating and managing application data — study guide chapter
Learn the concepts, then practise the questions
- →
Integrating and managing application data practice questions
Targeted practice on this topic area only
- →
All SNOW-CAD questions
500 questions across all exam domains
- →
ServiceNow Certified Application Developer CAD study guide
Full concept coverage aligned to exam objectives
- →
SNOW-CAD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SNOW-CAD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Working with Data practice questions
Practise SNOW-CAD questions linked to Working with Data.
Platform Features and Integration practice questions
Practise SNOW-CAD questions linked to Platform Features and Integration.
Integrating and managing application data practice questions
Practise SNOW-CAD questions linked to Integrating and managing application data.
Automating application logic with business rules and scripts practice questions
Practise SNOW-CAD questions linked to Automating application logic with business rules and scripts.
Application development using ServiceNow Studio practice questions
Practise SNOW-CAD questions linked to Application development using ServiceNow Studio.
Creating and customizing tables and data practice questions
Practise SNOW-CAD questions linked to Creating and customizing tables and data.
Designing interfaces and user experiences practice questions
Practise SNOW-CAD questions linked to Designing interfaces and user experiences.
Core Application Development practice questions
Practise SNOW-CAD questions linked to Core Application Development.
User Interface Development practice questions
Practise SNOW-CAD questions linked to User Interface Development.
SNOW-CAD fundamentals practice questions
Practise SNOW-CAD questions linked to SNOW-CAD fundamentals.
SNOW-CAD scenario practice questions
Practise SNOW-CAD questions linked to SNOW-CAD scenario.
SNOW-CAD troubleshooting practice questions
Practise SNOW-CAD questions linked to SNOW-CAD troubleshooting.
Practice this exam
Start a free SNOW-CAD practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SNOW-CAD question test?
Integrating and managing application data — This question tests Integrating and managing application data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Add a check in the integration script to query the incident table for an existing incident with the same external ticket ID before creating a new one. — Option A is correct because the most reliable way to prevent duplicates is to check the incident table for an existing record with the same external ticket ID before creating a new incident. This leverages the unique identifier from the third-party system and avoids relying on the third-party's caching behavior. By querying the incident table using a GlideRecord lookup on a field that stores the external ID, the script can conditionally skip creation if a match is found.
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.
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 →
Last reviewed: Jun 11, 2026
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.