SC-200 Manage a security operations environment Practice Question
Exhibit
Refer to the exhibit.
```json
{
"properties": {
"displayName": "Block Malicious IP",
"logicAppResourceId": "/subscriptions/.../providers/Microsoft.Logic/workflows/BlockIP",
"triggerConditions": [
{
"property": "Microsoft.Security.Incident",
"condition": "Equals",
"value": "High"
}
]
}
}
```Refer to the exhibit. You are reviewing a playbook configuration for Microsoft Sentinel. What does this playbook do?
⚠ Common exam trap
Many exam-takers confuse the trigger for incident creation versus alert generation, or overlook the severity filter in the condition, leading them to incorrectly select option B or C.
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
✓
It runs when a high severity incident is created
The playbook is configured with a trigger condition that specifies 'When a high severity incident is created'. This means the playbook will only execute when an incident with a severity level of 'High' is generated in Microsoft Sentinel. The condition filters out incidents of other severity levels, ensuring the playbook runs exclusively for high-severity incidents.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It runs only on medium severity incidents
Why it's wrong here
This is incorrect because the playbook's trigger condition explicitly filters for incident severity equal to 'High,' not 'Medium.' A medium-severity incident would fail the condition check and the playbook would not execute for it. The only severity that satisfies the configured trigger is High, so the playbook never runs on medium severity incidents.
- ✗
It runs when a new alert is generated with high severity
Why it's wrong here
This is incorrect because the playbook is triggered by incident creation, not by alert generation. While a high-severity alert may contribute to an incident, the playbook's condition operates on the incident's severity property after the incident is created, not on the alert's properties at the moment the alert fires. Alerts that do not become incidents will never invoke this playbook.
- ✗
It runs on all incidents regardless of severity
Why it's wrong here
This is incorrect because the playbook does not run on all incidents; it has a condition that restricts execution to incidents whose severity is exactly 'High.' Incidents classified as Low, Medium, or any other severity value will be filtered out and will not trigger the playbook. Therefore, it is not severity-agnostic; it is specifically scoped to high severity incidents only.
- ✓
It runs when a high severity incident is created
Why this is correct
This is correct because the playbook's trigger condition checks the incident severity field and only allows execution when the value is 'High.' It is configured to run at incident creation time, so whenever a new incident with high severity is generated, the playbook will execute. Any incident created with a severity other than High will not satisfy the condition and will not run the playbook.
Go deeper
Related to this question
About these practice questions
This SC-200 question is part of Courseiva's 1,303-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.