Courseiva
Manage a security operations environmenthardMultiple SelectObjective-mapped

SC-200 Manage a security operations environment Practice Question

Your organization uses Microsoft Sentinel with multiple workspaces. You need to create a unified incident queue across all workspaces. Which TWO solutions should you consider?

⚠ Common exam trap

Many candidates think cross-workspace queries (Option A) can unify the incident queue, but they only provide a read-only, query-based view without the ability to manage or act on incidents as a single entity.

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

Consolidate all data into a single Log Analytics workspace.

Consolidating all data into a single Log Analytics workspace is the most straightforward and supported method to create a unified incident queue in Microsoft Sentinel. With a single workspace, all alerts and incidents are naturally aggregated, eliminating the need for cross-workspace synchronization. This approach simplifies management, ensures consistent analytics rules, and avoids the complexity of stitching incidents across multiple workspaces.

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 cross-workspace queries in workbooks.

    Why it's wrong here

    Queries don't create a unified incident queue; they only query data.

  • Consolidate all data into a single Log Analytics workspace.

    Why this is correct

    A single workspace provides a unified incident queue.

  • Configure incident grouping rules in Microsoft Sentinel.

    Why this is correct

    Grouping rules can correlate alerts from multiple workspaces into one incident.

  • Use Azure Policy to enforce workspace configuration.

    Why it's wrong here

    Policy doesn't unify incident queues.

  • Deploy multiple playbooks to synchronize incidents.

    Why it's wrong here

    Playbooks can't synchronize incident queues across workspaces.

About these practice questions

One of 209 original SC-200 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on SC-200

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Your organization uses Microsoft Sentinel with multiple workspaces. You need to ensure that incidents involving the same alert in different workspaces are automatically grouped into a single incident. What should you configure?

medium
  • A.Enable UEBA to correlate alerts across workspaces.
  • B.Set up an automation rule to merge incidents.
  • C.Create an analytics rule that runs across all workspaces.
  • D.Configure an incident grouping rule in Microsoft Sentinel.

Why C: You can create a scheduled analytics rule that queries across multiple workspaces (using the workspace() function or union operator) and if the same alert appears in multiple workspaces, the rule can generate a single incident. This allows automatic grouping of correlated alerts from different workspaces into one incident. Option D is incorrect because Microsoft Sentinel does not have a dedicated 'incident grouping rule' that groups alerts from multiple workspaces; that feature does not exist.

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.