Question 1,008 of 1,639
Mitigate threats using Microsoft SentinelmediumMultiple 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: microsoft Sentinel automation rules trigger playbooks based on incident properties.. 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 SOC analyst wants to automate a response in Microsoft Sentinel: whenever an incident is created that contains a compromised user entity (e.g., a user whose credentials were used in a breach), a playbook should run to disable that user in Microsoft Entra ID. Which condition should be configured in the automation rule to trigger this playbook?

Question 1mediummultiple 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

Set the condition to 'When incident is created with entity type Account'.

Option C is correct because the automation rule must trigger when an incident is created with an entity type of 'Account' to match the compromised user entity. In Microsoft Sentinel, a user whose credentials were used in a breach is represented as an 'Account' entity, not an 'IP' or 'Host'. The playbook to disable the user in Microsoft Entra ID requires this entity type to pass the user principal name (UPN) or object ID to the action.

Key principle: Microsoft Sentinel automation rules trigger playbooks based on incident properties.

Answer analysis

Option-by-option breakdown

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

  • Set the trigger to 'When incident is created' with no additional condition.

    Why it's wrong here

    This would run the playbook on every incident, not only those containing user entities, leading to unnecessary executions.

  • Set the condition to 'When incident is created with entity type IP'.

    Why it's wrong here

    An IP address entity represents a network host, not a user. This would not match incidents with compromised user entities.

  • Set the condition to 'When incident is created with entity type Account'.

    Why this is correct

    The Account entity type represents user accounts. This condition ensures the playbook runs only on incidents that include a user entity, which is appropriate for disabling a compromised user.

    Related concept

    Microsoft Sentinel automation rules trigger playbooks based on incident properties.

  • Set the condition to 'When incident is updated with entity type Host'.

    Why it's wrong here

    This triggers on updates and for Host entities (computers), not user accounts. It would not match the desired scenario.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse 'Account' with 'User' or assume 'IP' is sufficient for user compromise, but Microsoft Sentinel uses the specific entity type 'Account' for user identities, and the automation rule condition must match exactly that type to trigger the playbook correctly.

Trap categories for this question

  • Scenario analysis trap

    This triggers on updates and for Host entities (computers), not user accounts. It would not match the desired scenario.

Detailed technical explanation

How to think about this question

Under the hood, Microsoft Sentinel automation rules evaluate entity types based on the normalized schema defined in the Common Event Format (CEF) or Azure Monitor Agent. The 'Account' entity type includes properties like 'Name', 'UPN', and 'ObjectGuid', which are essential for the Microsoft Entra ID connector to disable the user via the 'Disable User' action in a playbook. A real-world scenario: if an incident is created from a sign-in risk detection (e.g., impossible travel), the entity is automatically mapped as 'Account', and the automation rule must match this type to trigger the correct response.

KKey Concepts to Remember

  • Microsoft Sentinel automation rules trigger playbooks based on incident properties.
  • The 'Account' entity type represents user identities in Sentinel incidents.
  • Automation rule conditions filter incidents to ensure relevant playbook execution.
  • Playbooks can perform actions like disabling users in Microsoft Entra ID.

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

Microsoft Sentinel automation rules trigger playbooks based on incident properties.

Real-world example

How this comes up in practice

A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

What to study next

Got this wrong? Here's your next step.

Review microsoft Sentinel automation rules trigger playbooks based on incident properties., 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 — Microsoft Sentinel automation rules trigger playbooks based on incident properties..

What is the correct answer to this question?

The correct answer is: Set the condition to 'When incident is created with entity type Account'. — Option C is correct because the automation rule must trigger when an incident is created with an entity type of 'Account' to match the compromised user entity. In Microsoft Sentinel, a user whose credentials were used in a breach is represented as an 'Account' entity, not an 'IP' or 'Host'. The playbook to disable the user in Microsoft Entra ID requires this entity type to pass the user principal name (UPN) or object ID to the action.

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

Review microsoft Sentinel automation rules trigger playbooks based on incident properties., then practise related SC-200 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Microsoft Sentinel automation rules trigger playbooks based on incident properties.

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.