- A
9:45 AM Monday.
Correct calculation based on business hours.
- B
5:45 PM Friday.
Why wrong: This ignores the business schedule and assumes 24/7 counting.
- C
4:45 PM Saturday.
Why wrong: The schedule does not include weekends.
- D
4:45 PM Monday.
Why wrong: This would be if the full hour was counted from Monday start, but only 45 minutes remain.
Quick Answer
The answer is 9:45 AM Monday. This is correct because the SLA breach time calculation with a business schedule in ServiceNow only counts time within the defined schedule—9 AM to 5 PM, Monday through Friday. The incident entered 'In Progress' at 4:45 PM on Friday, leaving only 15 minutes of the 1-hour SLA duration before the schedule closes at 5 PM; the remaining 45 minutes must be fulfilled starting Monday at 9 AM, pushing the breach to 9:45 AM. On the ServiceNow Certified System Administrator CSA exam, this tests your understanding of how business schedules pause and resume SLA timers, a common trap where candidates forget to subtract the elapsed business time from the total duration. A helpful memory tip: think of the business schedule as a “time bank” that only opens during working hours—always calculate the remaining minutes after the schedule closes, then add them to the next opening time.
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.
An admin has set up an SLA on the Incident table with a condition 'Priority = 1' and a duration of 1 hour. The SLA is triggered when the incident state becomes 'In Progress'. The SLA definition includes a business schedule that only counts business hours (9 AM to 5 PM, Monday-Friday). An incident with Priority 1 is created at 4:30 PM on Friday and state is changed to 'In Progress' at 4:45 PM. At what time will the SLA breach if it is not resolved?
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
9:45 AM Monday.
The SLA has a duration of 1 hour but uses a business schedule that only counts hours between 9 AM and 5 PM, Monday through Friday. The incident entered 'In Progress' at 4:45 PM on Friday, so only 15 minutes of business time remain that day (4:45 PM to 5:00 PM). The remaining 45 minutes of SLA duration must be fulfilled starting Monday at 9:00 AM, pushing the breach time to 9:45 AM Monday.
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.
- ✓
9:45 AM Monday.
Why this is correct
Correct calculation based on business hours.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
5:45 PM Friday.
Why it's wrong here
This ignores the business schedule and assumes 24/7 counting.
- ✗
4:45 PM Saturday.
Why it's wrong here
The schedule does not include weekends.
- ✗
4:45 PM Monday.
Why it's wrong here
This would be if the full hour was counted from Monday start, but only 45 minutes remain.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates forget to account for the partial business hour consumed on Friday and instead assume the entire SLA duration starts fresh on Monday, leading them to pick 4:45 PM Monday.
Detailed technical explanation
How to think about this question
Under the hood, ServiceNow SLA timers use the business schedule's defined intervals to calculate elapsed time; only seconds within the schedule's active windows count toward the duration. A common subtlety is that the SLA starts counting from the trigger time (4:45 PM), not from the next business hour, so partial business hours at the end of a day are consumed first. In real-world scenarios, this behavior ensures that SLAs with limited support windows (e.g., 9-5) accurately reflect available working time, preventing unrealistic breach expectations outside of business hours.
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: 9:45 AM Monday. — The SLA has a duration of 1 hour but uses a business schedule that only counts hours between 9 AM and 5 PM, Monday through Friday. The incident entered 'In Progress' at 4:45 PM on Friday, so only 15 minutes of business time remain that day (4:45 PM to 5:00 PM). The remaining 45 minutes of SLA duration must be fulfilled starting Monday at 9:00 AM, pushing the breach time to 9:45 AM Monday.
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 →
Same concept, more angles
1 more ways this is tested on SNOW-CSA
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An organization has a Service Level Agreement (SLA) defined on the Incident table with a condition of 'Category is Network' and a duration of 4 hours. The SLA is triggered when the incident state changes from 'New' to 'In Progress'. A network incident is created and assigned to the Network Support group. The incident state is changed to 'In Progress' immediately. After 3 hours, the incident is resolved. However, the SLA shows a breach despite the resolution being within 4 hours. What is the most likely cause?
hard- ✓ A.The SLA stop condition is set to 'State is Resolved', but the SLA was paused due to a schedule (e.g., after-hours pause) and the pause time was not counted, causing the actual working time to exceed 4 hours.
- B.The SLA is assigned to the Network Support group, but the assignment group was changed during the incident.
- C.The SLA duration is defined in business hours, and the incident was created after business hours, so the elapsed time counted only business hours, making the 4-hour window longer in real time.
- D.The SLA condition 'Category is Network' was not evaluated correctly because the category field was updated after the SLA was triggered.
Why A: Option A is correct because the SLA breach occurred despite the incident being resolved within 4 hours of moving to 'In Progress'. The most likely cause is that the SLA stop condition is set to 'State is Resolved', but the SLA was paused due to a schedule (e.g., after-hours pause) and the pause time was not counted, causing the actual working time to exceed 4 hours. In ServiceNow, SLA schedules define when the clock is running; if the incident was resolved during a pause period, the SLA timer would have stopped only when the schedule resumed, and the elapsed working time could exceed the 4-hour duration.
Last reviewed: Jun 11, 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.