SNOW-CAD Core Application Development Practice Question
A senior developer is troubleshooting a performance issue in a Production instance. The instance has a large number of Business Rules that run on the incident table. One particular Business Rule, 'Update CI Impact', runs on the 'After Update' order and performs a GlideRecord query on the cmdb_ci table based on the incident's configuration item (ci) field. The query uses a filter to find all CIs related to the same location as the incident. Recently, users have reported that saving an incident takes over 30 seconds. The developer suspects this Business Rule is the cause. The developer examines the script and finds it uses a synchronous GlideRecord query with no scoping on the query. The developer wants to minimize impact on performance without removing the functionality. Which approach should the developer take?
⚠ Common exam trap
It's easy for candidates to assume performance issues are always solved by optimizing the query (indexing) rather than recognizing that moving the execution out of the synchronous transaction path is the correct architectural fix for blocking delays.
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
✓
Change the Business Rule to run asynchronously using the 'Async' checkbox in the Business Rule form.
Enabling the 'Async' checkbox on the Business Rule moves the execution to the background job scheduler, allowing the incident save transaction to complete immediately without waiting for the GlideRecord query to finish. This eliminates the synchronous delay that causes the 30-second save time, while preserving the functionality of updating CI impact.
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 Business Rule to run asynchronously using the 'Async' checkbox in the Business Rule form.
Why this is correct
Correct: Async execution prevents blocking the user transaction.
- ✗
Add an index on the cmdb_ci table for the location field and use an efficient query.
Why it's wrong here
Plausible but still synchronous; performance gain may be insufficient.
- ✗
Move the logic to a scheduled job that runs every hour instead of on every update.
Why it's wrong here
Incorrect: Changes functionality by delaying updates, likely unacceptable.
- ✗
Convert the GlideRecord query to use GlideRecordSecure to limit access.
Why it's wrong here
Incorrect: GlideRecordSecure is for security, not performance.
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.