Question 709 of 1,639
Manage a security operations environmenthardMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the automation rule never triggers because its condition requires an incident status of 'Active', but incidents in Microsoft Sentinel are always created with a status of 'New'. This is a fundamental behavior of the incident lifecycle: when a new incident is generated, its status field is set to 'New' by default, and it only transitions to 'Active' after a user manually triages or investigates it. Since the rule is set to trigger on incident creation, the condition checks the status at that exact moment, finds it to be 'New' rather than 'Active', and therefore the condition is never satisfied. On the SC-200 exam, this scenario tests your understanding of automation rule conditions and the default incident status flow—a common trap is assuming 'Active' is the initial state. To remember, think "New before Active, like a newborn before it can run."

SC-200 Manage a security operations environment Practice Question

This SC-200 practice question tests your understanding of manage a security operations environment. 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.

Exhibit

{
  "properties": {
    "displayName": "Test Automation Rule",
    "order": 1,
    "triggers": [
      {
        "type": "IncidentCreated",
        "conditions": [
          {
            "property": "IncidentStatus",
            "operator": "Equals",
            "value": "Active"
          },
          {
            "property": "Severity",
            "operator": "Equals",
            "value": "High"
          }
        ]
      }
    ],
    "actions": [
      {
        "type": "RunPlaybook",
        "order": 1,
        "playbookId": "/subscriptions/.../providers/Microsoft.Logic/workflows/MyPlaybook"
      }
    ]
  }
}

Refer to the exhibit. You have an automation rule defined as shown. The rule is enabled but never triggers. What is the most likely reason?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

  • Clue: "never"

    Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.

Question 1hardmultiple choice
Full question →

Exhibit

{
  "properties": {
    "displayName": "Test Automation Rule",
    "order": 1,
    "triggers": [
      {
        "type": "IncidentCreated",
        "conditions": [
          {
            "property": "IncidentStatus",
            "operator": "Equals",
            "value": "Active"
          },
          {
            "property": "Severity",
            "operator": "Equals",
            "value": "High"
          }
        ]
      }
    ],
    "actions": [
      {
        "type": "RunPlaybook",
        "order": 1,
        "playbookId": "/subscriptions/.../providers/Microsoft.Logic/workflows/MyPlaybook"
      }
    ]
  }
}

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

The condition requires incident status 'Active', but incidents start as 'New'.

The automation rule triggers on incident creation, but the condition requires the incident status to be 'Active'. In Microsoft Sentinel, incidents are created with a status of 'New', not 'Active'. Therefore, the condition is never met, and the rule never triggers. To fix this, the condition should either be removed or changed to include 'New' status.

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.

  • The playbook resource ID is incomplete.

    Why it's wrong here

    The ID is present; the rule would still trigger but fail.

  • The condition requires incident status 'Active', but incidents start as 'New'.

    Why this is correct

    Incidents are created with status 'New', so the condition never matches.

    Clue confirmation

    The clue words "most likely", "never" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The trigger type should be 'AlertCreated' instead of 'IncidentCreated'.

    Why it's wrong here

    IncidentCreated is correct for incident-based automation.

  • The rule order is set to 1, which is too low.

    Why it's wrong here

    Order 1 is fine; it runs first.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Microsoft often tests the subtle difference between incident status values ('New' vs 'Active') and the fact that incidents are created as 'New', not 'Active', causing candidates to overlook the condition mismatch.

Detailed technical explanation

How to think about this question

Microsoft Sentinel automation rules evaluate conditions at the time of incident creation or update. The incident status field is a system-managed property that transitions from 'New' to 'Active' only when an analyst manually changes it or via an automated action. This design ensures that initial triage actions (like assignment or classification) occur before automation rules that require an 'Active' status. A common real-world scenario is using a rule to auto-assign incidents to a tier-2 team only after initial triage has moved the incident to 'Active'.

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.

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.

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?

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: The condition requires incident status 'Active', but incidents start as 'New'. — The automation rule triggers on incident creation, but the condition requires the incident status to be 'Active'. In Microsoft Sentinel, incidents are created with a status of 'New', not 'Active'. Therefore, the condition is never met, and the rule never triggers. To fix this, the condition should either be removed or changed to include 'New' status.

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.

Are there clue words in this question I should notice?

Yes — watch for: "most likely", "never". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 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.