The correct approach is to create two separate analytics rules: one that runs every hour during business hours and another that runs but suppresses alerts outside business hours. This workaround is necessary because Microsoft Sentinel scheduled analytics rules do not natively support time-based scheduling restrictions like “only during business hours.” Instead, you configure the first rule to trigger alerts normally between 8 AM and 6 PM, and the second rule to run on the same hourly cadence outside that window but with alert suppression enabled—for example, by setting a low severity or using a suppression query. On the SC-200 exam, this scenario tests your understanding of Sentinel’s rule limitations and your ability to implement creative detection logic without built-in time filters. A common trap is assuming you can simply set a schedule condition like “run only between 8 AM and 6 PM,” which does not exist. Memory tip: think “two rules, one window” — duplicate the schedule, then mute the off-hours copy.
SC-200 Manage a security operations environment Practice Question
This SC-200 practice question tests your understanding of manage a security operations environment. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
Your SOC team uses Microsoft Sentinel analytics rules. You need to ensure that a scheduled rule runs every hour, but only during business hours (8 AM to 6 PM). What configuration should you use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create two rules: one that runs every hour during business hours and another that runs but suppresses alerts outside business hours.
Option C is correct because Microsoft Sentinel scheduled analytics rules do not natively support time-based scheduling restrictions like 'only during business hours'. The recommended workaround is to create two separate rules: one that runs every hour during business hours to generate alerts, and another that runs every hour outside business hours but is configured to suppress alerts (e.g., by setting a low severity or using a suppression query). This ensures detection logic runs continuously while avoiding alert fatigue outside the desired window.
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.
✗
Use a custom log with a logic app to only trigger the rule during business hours.
Why it's wrong here
Logic apps can trigger, but not pause a scheduled rule.
✗
Configure the rule to run continuously with an alert threshold of 0.
Why it's wrong here
Continuous rules are not available for scheduled rules.
✓
Create two rules: one that runs every hour during business hours and another that runs but suppresses alerts outside business hours.
Why this is correct
You can have a rule run continuously but use suppression or separate rules for time-based scheduling.
Related concept
Read the scenario before looking for a memorised answer.
✗
Set the rule to run every hour and use a KQL query to filter events outside business hours.
Why it's wrong here
The rule would still run and generate alerts outside business hours.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume a single rule can be configured with a time-based schedule filter, but Microsoft Sentinel does not support conditional scheduling; the only way to achieve time-restricted alerting is by using multiple rules with suppression logic.
Detailed technical explanation
How to think about this question
Under the hood, Microsoft Sentinel scheduled analytics rules use a fixed schedule (e.g., every hour) with no built-in 'business hours' toggle. The two-rule approach leverages the 'Alert suppression' setting in the rule configuration, which can be set to suppress alerts based on a KQL query or a fixed time window. In practice, you would set the suppression rule to run with a query that always returns results (e.g., 'let _ = true;') and set the suppression duration to cover the entire non-business hours period, effectively silencing alerts while the rule still runs for detection continuity.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SC-200 question in full detail.
Manage a security operations environment — This question tests Manage a security operations environment — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create two rules: one that runs every hour during business hours and another that runs but suppresses alerts outside business hours. — Option C is correct because Microsoft Sentinel scheduled analytics rules do not natively support time-based scheduling restrictions like 'only during business hours'. The recommended workaround is to create two separate rules: one that runs every hour during business hours to generate alerts, and another that runs every hour outside business hours but is configured to suppress alerts (e.g., by setting a low severity or using a suppression query). This ensures detection logic runs continuously while avoiding alert fatigue outside the desired window.
What should I do if I get this SC-200 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 →
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.
This SC-200 practice question is part of Courseiva's free Microsoft 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 SC-200 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.