- A
Create summary fields on the incident table to pre-calculate counts and sums for the relevant filters.
Summary fields pre-aggregate data periodically, greatly speeding up report execution for large datasets.
- B
Remove the OR condition and split the report into two separate reports.
Why wrong: This changes the output and user experience; the requirement is to maintain the same output.
- C
Increase the report's timeout value to 60 minutes.
Why wrong: This does not solve the root performance issue; the report will still run slowly and may still time out if data grows.
- D
Add indexes to the fields used in the filters.
Why wrong: Indexes can improve performance but are less effective for complex OR conditions and join-heavy views.
SNOW-CSA Reporting, SLA and Imports Practice Question
This SNOW-CSA practice question tests your understanding of reporting, sla and imports. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 large organization uses a weekly scheduled report to analyze incident trends. The report queries a database view that joins several tables. The report has filters: ((category=Network OR category=Database) AND priority<=2) OR (assigned_to in (specific group)). The report takes over 30 minutes to run and often times out. The administrator wants to improve performance without altering the report's output. Which action should be taken?
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
Create summary fields on the incident table to pre-calculate counts and sums for the relevant filters.
Creating summary fields on the incident table pre-calculates aggregate values for the filters (category, priority, assigned_to), allowing the report to read precomputed data instead of scanning and joining large tables each time. This directly addresses the performance bottleneck without altering the report's output, as summary fields are updated incrementally and maintain the same logical results.
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.
- ✓
Create summary fields on the incident table to pre-calculate counts and sums for the relevant filters.
Why this is correct
Summary fields pre-aggregate data periodically, greatly speeding up report execution for large datasets.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Remove the OR condition and split the report into two separate reports.
Why it's wrong here
This changes the output and user experience; the requirement is to maintain the same output.
- ✗
Increase the report's timeout value to 60 minutes.
Why it's wrong here
This does not solve the root performance issue; the report will still run slowly and may still time out if data grows.
- ✗
Add indexes to the fields used in the filters.
Why it's wrong here
Indexes can improve performance but are less effective for complex OR conditions and join-heavy views.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume indexing is the universal solution for slow queries, but ServiceNow's summary fields are the designed mechanism for optimizing report performance on complex filters involving joins and aggregations.
Trap categories for this question
Command / output trap
This changes the output and user experience; the requirement is to maintain the same output.
Detailed technical explanation
How to think about this question
Summary fields in ServiceNow are stored as aggregate records that are updated via scheduled jobs or business rules, reducing the need to scan transactional tables. For reports with OR conditions across multiple tables, summary fields can be configured to match the exact filter logic, ensuring the precomputed data aligns with the report's conditions. In real-world scenarios, summary fields are especially effective for large datasets where joins and aggregations cause timeouts, as they shift the computational load to off-peak update intervals.
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-CSA 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.
- →
Reporting, SLA and Imports — study guide chapter
Learn the concepts, then practise the questions
- →
Reporting, SLA and Imports practice questions
Targeted practice on this topic area only
- →
All SNOW-CSA questions
510 questions across all exam domains
- →
ServiceNow Certified System Administrator CSA study guide
Full concept coverage aligned to exam objectives
- →
SNOW-CSA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SNOW-CSA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Reporting, SLA and Imports practice questions
Practise SNOW-CSA questions linked to Reporting, SLA and Imports.
Self-Service and Automation practice questions
Practise SNOW-CSA questions linked to Self-Service and Automation.
UI, Navigation and Forms practice questions
Practise SNOW-CSA questions linked to UI, Navigation and Forms.
Database Administration and CMDB practice questions
Practise SNOW-CSA questions linked to Database Administration and CMDB.
Service Catalog and Workflows practice questions
Practise SNOW-CSA questions linked to Service Catalog and Workflows.
Application Rules, ACL and Notifications practice questions
Practise SNOW-CSA questions linked to Application Rules, ACL and Notifications.
SNOW-CSA fundamentals practice questions
Practise SNOW-CSA questions linked to SNOW-CSA fundamentals.
SNOW-CSA scenario practice questions
Practise SNOW-CSA questions linked to SNOW-CSA scenario.
SNOW-CSA troubleshooting practice questions
Practise SNOW-CSA questions linked to SNOW-CSA troubleshooting.
Practice this exam
Start a free SNOW-CSA 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-CSA question test?
Reporting, SLA and Imports — This question tests Reporting, SLA and Imports — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create summary fields on the incident table to pre-calculate counts and sums for the relevant filters. — Creating summary fields on the incident table pre-calculates aggregate values for the filters (category, priority, assigned_to), allowing the report to read precomputed data instead of scanning and joining large tables each time. This directly addresses the performance bottleneck without altering the report's output, as summary fields are updated incrementally and maintain the same logical results.
What should I do if I get this SNOW-CSA 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 24, 2026
This SNOW-CSA 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-CSA 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.