SNOW-CAD Working with Data Practice Question
A ServiceNow instance is configured with a custom table 'u_asset_history' that stores historical records for asset changes. This table has a reference field 'u_asset' pointing to the 'alm_asset' table, and a date field 'u_change_date'. The application uses a business rule that runs on 'alm_asset' after update, querying the 'u_asset_history' table to find the most recent change for that asset. The business rule is declared as 'async' to improve performance. However, recently the async business rule has been failing frequently with an 'async queue limit reached' error. The instance has default configuration for transaction quotas. The team suspects that the async queue is getting overloaded because many asset updates are happening simultaneously. Which action should the administrator take to resolve this issue while minimizing impact on other processes?
⚠ Common exam trap
ServiceNow often tests the distinction between performance optimization (indexing) and capacity management (quotas), leading candidates to mistakenly choose indexing when the error is explicitly a queue limit, not a slow query.
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
✓
Increase the system property 'glide.scope.async.quota' to allow more async transactions.
The error 'async queue limit reached' indicates that the instance's asynchronous transaction queue is full, which is a quota issue. Increasing the system property 'glide.scope.async.quota' raises the maximum number of concurrent asynchronous transactions allowed, directly addressing the overload without changing the business logic or impacting other processes. This is the correct approach because the business rule is already optimized to run asynchronously for performance, and the root cause is a capacity limit, not a query or design flaw.
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 an index on the 'u_asset' and 'u_change_date' fields in the 'u_asset_history' table to optimize the query.
Why it's wrong here
Adding an index optimizes queries but does not address the async queue limit issue.
- ✓
Increase the system property 'glide.scope.async.quota' to allow more async transactions.
Why this is correct
Increasing the async quota allows more concurrent async transactions, resolving the 'async queue limit reached' error.
- ✗
Rewrite the business rule to run synchronously with a background script to avoid async queue limits.
Why it's wrong here
Running synchronously could cause delays in the main transaction and may not improve overall performance.
- ✗
Disable the business rule and implement a scheduled job to perform the same logic during off-peak hours.
Why it's wrong here
Disabling the rule loses real-time update capabilities; a scheduled job may not meet the requirement for immediate updates.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 481 original SNOW-CAD practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.