- A
Add an index on the 'u_asset' and 'u_change_date' fields in the 'u_asset_history' table to optimize the query.
Why wrong: Adding an index optimizes queries but does not address the async queue limit issue.
- B
Increase the system property 'glide.scope.async.quota' to allow more async transactions.
Increasing the async quota allows more concurrent async transactions, resolving the 'async queue limit reached' error.
- C
Rewrite the business rule to run synchronously with a background script to avoid async queue limits.
Why wrong: Running synchronously could cause delays in the main transaction and may not improve overall performance.
- D
Disable the business rule and implement a scheduled job to perform the same logic during off-peak hours.
Why wrong: Disabling the rule loses real-time update capabilities; a scheduled job may not meet the requirement for immediate updates.
Quick Answer
The correct action is to increase the system property 'glide.scope.async.quota' to allow more async transactions. This resolves the "async queue limit reached" error because ServiceNow enforces a default quota on concurrent asynchronous business rule executions, and when simultaneous asset updates flood the queue, the instance hits that capacity ceiling rather than a logic or performance issue. On the ServiceNow Certified Application Developer (CAD) exam, this scenario tests your understanding of transaction quotas and async processing limits—a common trap is to mistakenly try rewriting the business rule as synchronous or optimizing the query, but the root cause is purely a capacity constraint. Remember, the async queue is a shared resource, so raising the quota directly addresses the overload without altering business logic. Memory tip: think "Quota = Queue capacity"—when the async queue is full, raise the quota, not the query.
SNOW-CAD Working with Data Practice Question
This SNOW-CAD practice question tests your understanding of working with data. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 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?
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.
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.
- ✗
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.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
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.
Detailed technical explanation
How to think about this question
The 'glide.scope.async.quota' property controls the maximum number of asynchronous business rules that can be queued per scope; when this limit is exceeded, new async transactions are rejected with the 'async queue limit reached' error. Under the hood, ServiceNow uses a dedicated worker thread pool for async processing, and the quota prevents resource exhaustion across all scopes. In a real-world scenario, bulk asset imports or automated updates from integrations can spike the queue, and simply increasing the quota (while monitoring instance health) is the standard remediation.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Working with Data practice questions
Targeted practice on this topic area only
- →
All SNOW-CAD questions
500 questions across all exam domains
- →
ServiceNow Certified Application Developer CAD study guide
Full concept coverage aligned to exam objectives
- →
SNOW-CAD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SNOW-CAD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Working with Data practice questions
Practise SNOW-CAD questions linked to Working with Data.
Platform Features and Integration practice questions
Practise SNOW-CAD questions linked to Platform Features and Integration.
Integrating and managing application data practice questions
Practise SNOW-CAD questions linked to Integrating and managing application data.
Automating application logic with business rules and scripts practice questions
Practise SNOW-CAD questions linked to Automating application logic with business rules and scripts.
Application development using ServiceNow Studio practice questions
Practise SNOW-CAD questions linked to Application development using ServiceNow Studio.
Creating and customizing tables and data practice questions
Practise SNOW-CAD questions linked to Creating and customizing tables and data.
Designing interfaces and user experiences practice questions
Practise SNOW-CAD questions linked to Designing interfaces and user experiences.
Core Application Development practice questions
Practise SNOW-CAD questions linked to Core Application Development.
User Interface Development practice questions
Practise SNOW-CAD questions linked to User Interface Development.
SNOW-CAD fundamentals practice questions
Practise SNOW-CAD questions linked to SNOW-CAD fundamentals.
SNOW-CAD scenario practice questions
Practise SNOW-CAD questions linked to SNOW-CAD scenario.
SNOW-CAD troubleshooting practice questions
Practise SNOW-CAD questions linked to SNOW-CAD troubleshooting.
Practice this exam
Start a free SNOW-CAD practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SNOW-CAD question test?
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: 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.
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 →
Last reviewed: Jun 30, 2026
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.