SNOW-CAD Working with Data Practice Question
An administrator notices that a scheduled job, 'Update Asset Status', fails every night with a 'Script timeout' error. The job updates a large number of records in the Asset table. Which approach should the administrator take to resolve the timeout issue?
⚠ Common exam trap
ServiceNow often tests the misconception that increasing timeouts or splitting jobs is a valid fix, when the correct answer always involves using bulk database operations like GlideAggregate to reduce processing overhead.
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 job to use GlideAggregate with query and update in bulk
The script timeout error indicates that the scheduled job is taking too long to process individual record updates. Rewriting the job to use GlideAggregate with bulk update operations reduces the number of database round-trips and processes records in batches, which is the standard approach for handling large data sets in ServiceNow without hitting script timeout limits.
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 business rule to run asynchronously for each update
Why it's wrong here
Business rules run on each record, not solving the timeout of the job itself.
- ✗
Increase the timeout value in the scheduled job configuration
Why it's wrong here
This only delays the failure, not solving the root cause.
- ✗
Split the job into multiple smaller jobs running sequentially
Why it's wrong here
Splitting the job into multiple sequential smaller jobs does not address the root cause of the script timeout, which is the total execution duration exceeding the platform’s governor limit for a single script. Running jobs sequentially still accumulates the same total processing time across the sequence, so the timeout will merely shift to whichever individual job takes longest. This approach is tempting because it is a standard pattern for breaking large data operations into manageable batches to avoid transaction size limits or record-locking contention, and it would be correct if the error were a 'Script too large' or a database deadlock rather than a timeout.
- ✓
Rewrite the job to use GlideAggregate with query and update in bulk
Why this is correct
Bulk database operations reduce script execution time.
Visual reference
Go deeper
Related to this question
About these practice questions
This SNOW-CAD question is part of Courseiva's 481-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.