Question 592 of 1,639
Mitigate threats using Microsoft SentinelhardMultiple ChoiceObjective-mapped

SC-200 Mitigate threats using Microsoft Sentinel Practice Question

This SC-200 practice question tests your understanding of mitigate threats using microsoft sentinel. 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. A key principle to apply: automation rules trigger on incident creation or update.. 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 security analyst is configuring a Microsoft Sentinel playbook to automatically respond to phishing incidents. The playbook should only run when an incident of severity 'High' is created and the incident is not already assigned to a user. Which automation rule condition and trigger configuration should the analyst use?

Question 1hardmultiple choice
Read the full Ansible explanation →

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

Configure an automation rule with trigger 'When incident is created', conditions for severity equals High and 'Assigned to' is empty, and action to run the playbook.

Option A is correct because the automation rule trigger 'When incident is created' ensures the playbook runs immediately upon incident creation, and the conditions for severity equals 'High' and 'Assigned to' is empty filter incidents precisely as required. This configuration offloads the filtering to Sentinel's automation rule engine, which is more efficient and reliable than handling it inside the playbook logic.

Key principle: Automation rules trigger on incident creation or update.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Configure an automation rule with trigger 'When incident is created', conditions for severity equals High and 'Assigned to' is empty, and action to run the playbook.

    Why this is correct

    This correctly triggers on incident creation with the specified conditions.

    Related concept

    Automation rules trigger on incident creation or update.

  • Configure a playbook trigger 'When an incident is updated' and add a condition in the playbook logic app to check severity and assignment.

    Why it's wrong here

    Using 'updated' trigger may also fire on other updates; the standard pattern is to use automation rule with creation trigger.

  • Schedule the playbook to run every 5 minutes and query for new incidents with required properties.

    Why it's wrong here

    Scheduled playbooks are inefficient and not event-driven; automation rules are the correct method.

  • Configure an automation rule with trigger 'When incident is created' and only condition for severity equals High; the playbook will handle unassigned checks internally.

    Why it's wrong here

    While the playbook can check assignment, best practice is to use conditions in the automation rule to reduce unnecessary playbook executions.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often think the playbook itself should handle all logic (like checking assignment) via conditions inside the Logic App, but the automation rule's condition engine is designed for this filtering and is more efficient, leading them to choose Option D instead of A.

Detailed technical explanation

How to think about this question

Automation rules in Microsoft Sentinel are evaluated at the incident creation or update time by the Sentinel backend, and they support multiple conditions including 'Assigned to' being empty (null). When a condition is met, the rule triggers a playbook via an Azure Logic Apps connector, which uses the Sentinel trigger 'When a response to a Microsoft Sentinel incident is triggered' — this is distinct from the Logic App's own incident triggers and ensures the playbook receives the incident context. In high-volume environments, filtering at the automation rule level reduces Logic App executions and associated costs.

KKey Concepts to Remember

  • Automation rules trigger on incident creation or update.
  • Multiple conditions can be combined in an automation rule.
  • Automation rules can run playbooks as an action.
  • Conditions in automation rules reduce unnecessary playbook executions.

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

Automation rules trigger on incident creation or update.

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. Automation rules trigger on incident creation or update. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Review automation rules trigger on incident creation or update., then practise related SC-200 questions on the same topic to reinforce the concept.

Related practice questions

Related SC-200 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SC-200 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 SC-200 question test?

Mitigate threats using Microsoft Sentinel — This question tests Mitigate threats using Microsoft Sentinel — Automation rules trigger on incident creation or update..

What is the correct answer to this question?

The correct answer is: Configure an automation rule with trigger 'When incident is created', conditions for severity equals High and 'Assigned to' is empty, and action to run the playbook. — Option A is correct because the automation rule trigger 'When incident is created' ensures the playbook runs immediately upon incident creation, and the conditions for severity equals 'High' and 'Assigned to' is empty filter incidents precisely as required. This configuration offloads the filtering to Sentinel's automation rule engine, which is more efficient and reliable than handling it inside the playbook logic.

What should I do if I get this SC-200 question wrong?

Review automation rules trigger on incident creation or update., then practise related SC-200 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Automation rules trigger on incident creation or update.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More SC-200 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.