The answer is to create a database index on the 'u_project' field in the 'u_project_task' table. This directly addresses the related list slow performance by enabling the database to use an index seek instead of a full table scan when joining the 2-million-record task table with the 50,000-record project table. Without that index, every time a user opens a project record, the database must scan every row in 'u_project_task' to find matching tasks, causing the 30-second delay. On the ServiceNow Certified Application Developer CAD exam, this scenario tests your understanding of how database indexes optimize foreign key joins in large tables—a common trap is assuming hardware or caching fixes are needed when the real bottleneck is a missing index. Remember the memory tip: "Index the foreign key, or the query will be slow as a key."
SNOW-CAD Working with Data Practice Question
This SNOW-CAD practice question tests your understanding of working with 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 large enterprise runs ServiceNow on a single instance. They have a custom table 'u_project_task' that stores task details for projects. Each project task has a reference field to the 'u_project' table. The 'u_project' table has approximately 50,000 records, and the 'u_project_task' table has about 2 million records. Users report that opening a project record and viewing its related tasks takes over 30 seconds. The system uses an out-of-box related list to display tasks. The instance has standard hardware resources. The administrator has already confirmed that there are no performance issues with the database server or network. Which course of action should the administrator take to improve the performance of the related list?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a database index on the 'u_project' field in the 'u_project_task' table to speed up the join.
The performance bottleneck is the database query that joins the large 'u_project_task' table (2M records) with the 'u_project' table on the reference field. Without an index on the 'u_project' field in 'u_project_task', the database must perform a full table scan for each related list query. Creating a database index on that foreign key column allows the database to use an index seek, dramatically reducing query time.
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.
✗
Archive project tasks older than 1 year to a separate table to reduce the data volume.
Why it's wrong here
Archiving is a long-term solution and may not address the immediate performance issue.
✓
Create a database index on the 'u_project' field in the 'u_project_task' table to speed up the join.
Why this is correct
An index on the foreign key can significantly improve query performance for related lists.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the glide.ui.related_list.max_timeout property to allow the query more time.
Why it's wrong here
Timeout increase only masks slowness, does not improve query speed.
✗
Add additional application nodes to the instance to distribute the load.
Why it's wrong here
Horizontal scaling may not help if the bottleneck is database query performance.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse performance tuning with scaling infrastructure or extending timeouts, failing to recognize that the root cause is a missing database index on the foreign key column used in the JOIN.
Detailed technical explanation
How to think about this question
Under the hood, ServiceNow uses a relational database (MySQL or MariaDB) where related lists are fetched via SQL JOINs. Without an index on the foreign key column, the database engine performs a full table scan of the 2M-row table, which is O(n) complexity. A B-tree index on that column reduces the lookup to O(log n), and the database can retrieve matching rows in milliseconds. In real-world scenarios, even a single missing index on a high-volume reference field can cause related lists to time out, while adding the index resolves the issue without any other changes.
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.
Working with Data — This question tests Working with Data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a database index on the 'u_project' field in the 'u_project_task' table to speed up the join. — The performance bottleneck is the database query that joins the large 'u_project_task' table (2M records) with the 'u_project' table on the reference field. Without an index on the 'u_project' field in 'u_project_task', the database must perform a full table scan for each related list query. Creating a database index on that foreign key column allows the database to use an index seek, dramatically reducing query time.
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 →
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.