SNOW-CAD Creating and customizing tables and data Practice Question
A large enterprise runs a ServiceNow instance with a heavily customized Task table. The 'Task' table has been extended to create 'u_WorkOrder', which is used by over 50,000 active records. Recently, users complain that when they open a WorkOrder record, the form takes more than 10 seconds to load. On investigation, you discover that the 'u_WorkOrder' table has 150 fields, many of which are UI policies and client scripts that trigger on load. Additionally, there is a business rule that runs 'after query' and dot-walks through multiple related tables (e.g., calling 'current.assigned_to.department.manager.email' in a loop for each record). The instance uses SQL Server as its database. Which action would most effectively reduce the form load time without losing required functionality?
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
✓
Rewrite the after query business rule to use GlideAggregate or avoid dot-walking in loops, and consider caching the dot-walked data
The most effective because it directly addresses the root cause: the after query business rule performing expensive dot-walking for every record. Rewriting it to use GlideAggregate or caching the dot-walked data will significantly reduce query time. Option A is wrong because changing the order of the business rule does not reduce its workload; it still runs after query. Option C is wrong because removing fields may cause loss of required functionality and does not target the primary performance issue (the business rule). Option D is wrong because converting to after update changes the trigger but does not solve the load-time problem; form load is a query action, not an update.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Change the order of the business rule to 100 so that it runs after other rules
Why it's wrong here
Ordering affects the sequence but does not reduce the processing time. The rule still runs and causes the same delay.
- ✓
Rewrite the after query business rule to use GlideAggregate or avoid dot-walking in loops, and consider caching the dot-walked data
Why this is correct
The dot-walking in a loop per record is extremely slow. Using GlideAggregate for batch queries or caching results in a system property can drastically reduce query time.
- ✗
Remove 50 of the 150 fields from the table to reduce data retrieval
Why it's wrong here
While reducing fields can help, it may remove required functionality and the main bottleneck is the business rule. Also, fields are not loaded until the form is opened, so the impact is limited.
- ✗
Convert the after query business rule to an after update business rule
Why it's wrong here
Changing the trigger to 'after update' would not fire on query, but the business rule's purpose may be to pre-fetch data for display; moving it to update might not help the load time.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SNOW-CAD question from scratch — 481 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.