Question 15 of 1,639

Mitigate threats using Microsoft Sentinel →hardMultiple ChoiceObjective-mapped

Quick Answer

The recommended approach is to use cross-workspace queries in a single analytics rule with the workspace() function. This is correct because the workspace() function allows a single Kusto Query Language (KQL) query to reference tables from up to 100 different Microsoft Sentinel workspaces, even across regions, without needing to centralize data ingestion or duplicate rules. On the SC-200 exam, this concept tests your understanding of how to scale threat detection across distributed environments while avoiding the cost and complexity of data consolidation. A common trap is assuming you must create separate rules per workspace or use a union operator without the workspace() function, which would fail to resolve cross-tenant table references. Memory tip: think of workspace() as a “phone book” for your KQL query—it dials into each workspace’s tables directly, so you only write one rule to cover many locations.

SC-200 Mitigate threats using Microsoft Sentinel Practice Question

This SC-200 practice question tests your understanding of mitigate threats using microsoft sentinel. 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.

A SOC team uses Microsoft Sentinel with multiple workspaces distributed across different regions. They need to create a single analytics rule that can query data from multiple workspaces to detect cross-tenant attacks. What is the recommended approach?

Question 1hardmultiple choice

Full question →

A
Create separate analytics rules for each workspace
Why wrong: This would require managing multiple rules and would not allow correlation across workspaces in a single detection.
B
Use cross-workspace queries in a single analytics rule with the workspace() function
The KQL workspace() function allows a single analytics rule to query tables from multiple Log Analytics workspaces, enabling cross-workspace detection.
C
Create a union workspace that ingests data from all workspaces
Why wrong: Sentinel does not have a built-in 'union workspace' concept; data resides in separate workspaces.
D
Use Azure Lighthouse to manage multiple workspaces and create rules on each
Why wrong: Azure Lighthouse allows centralized management but does not allow a single rule to query multiple workspaces without cross-workspace queries.

Full breakdown with real-world context →

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

✓

Use cross-workspace queries in a single analytics rule with the workspace() function

The recommended approach is to use cross-workspace queries in a single analytics rule with the workspace() function. This allows the rule to query data from multiple Sentinel workspaces in different regions without duplicating rules or ingesting data centrally. The workspace() function enables a single KQL query to reference tables from up to 100 workspaces, making it ideal for detecting cross-tenant attacks across distributed environments.

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.

✗
Create separate analytics rules for each workspace
Why it's wrong here
This would require managing multiple rules and would not allow correlation across workspaces in a single detection.
✓
Use cross-workspace queries in a single analytics rule with the workspace() function
Why this is correct
The KQL workspace() function allows a single analytics rule to query tables from multiple Log Analytics workspaces, enabling cross-workspace detection.
Related concept
Read the scenario before looking for a memorised answer.
✗
Create a union workspace that ingests data from all workspaces
Why it's wrong here
Sentinel does not have a built-in 'union workspace' concept; data resides in separate workspaces.
✗
Use Azure Lighthouse to manage multiple workspaces and create rules on each
Why it's wrong here
Azure Lighthouse allows centralized management but does not allow a single rule to query multiple workspaces without cross-workspace queries.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may think Azure Lighthouse alone solves the problem, but it only provides management plane access; the actual query logic still requires the workspace() function to combine data in a single rule.

Detailed technical explanation

How to think about this question

The workspace() function in Kusto Query Language (KQL) allows you to reference a specific workspace by its resource ID or name within a query, e.g., `workspace('workspace1').SecurityEvent | union workspace('workspace2').SecurityEvent`. This function works across regions and tenants, but the analytics rule must be created in a workspace that has access to the referenced workspaces (e.g., via Lighthouse or explicit permissions). A real-world scenario is detecting a user authenticating from an IP in one workspace and then accessing resources in another workspace, which requires correlating data across workspaces without moving the data.

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 SC-200 practice-question pages

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

Manage a security operations environment practice questions

Practise SC-200 questions linked to Manage a security operations environment.

Respond to security incidents practice questions

Practise SC-200 questions linked to Respond to security incidents.

Perform threat hunting practice questions

Practise SC-200 questions linked to Perform threat hunting.

Mitigate threats using Microsoft Defender XDR practice questions

Practise SC-200 questions linked to Mitigate threats using Microsoft Defender XDR.

Mitigate threats using Microsoft Defender for Cloud practice questions

Practise SC-200 questions linked to Mitigate threats using Microsoft Defender for Cloud.

Mitigate threats using Microsoft Sentinel practice questions

Practise SC-200 questions linked to Mitigate threats using Microsoft Sentinel.

SC-200 fundamentals practice questions

Practise SC-200 questions linked to SC-200 fundamentals.

SC-200 scenario practice questions

Practise SC-200 questions linked to SC-200 scenario.

SC-200 troubleshooting practice questions

Practise SC-200 questions linked to SC-200 troubleshooting.

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.

10 questions 20 questions 30 questions 50 questions Timed 30

SC-200 practice-test guide →Study guide →Browse all practice tests

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 — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use cross-workspace queries in a single analytics rule with the workspace() function — The recommended approach is to use cross-workspace queries in a single analytics rule with the workspace() function. This allows the rule to query data from multiple Sentinel workspaces in different regions without duplicating rules or ingesting data centrally. The workspace() function enables a single KQL query to reference tables from up to 100 workspaces, making it ideal for detecting cross-tenant attacks across distributed environments.

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.

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

Same concept, more angles

1 more ways 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. A SOC team uses Microsoft Sentinel with multiple workspaces in a single region. They have deployed Azure Policy to send all Azure resource logs to a central Log Analytics workspace. Now they want to create a set of analytics rules that run across multiple workspaces to detect cross-workspace attacks. However, they note that the built-in analytics rules can only query data within the workspace they are defined. Which solution should the team implement to efficiently query data from multiple workspaces for detection?

hard

A.Use Azure Lighthouse to delegate management and then create rules in the managing workspace that use workspace() expressions
✓ B.Create a KQL function that unions the relevant tables from all workspaces using the workspace() expression, then use that function in the analytics rule query
C.Configure the analytics rule to run in Log Analytics workspace manager and use cross-workspace queries native to Copilot for Security
D.Enable cross-workspace incident view in Sentinel settings and define the rule in the central workspace to automatically query all linked workspaces

Why B: Option B is correct because KQL functions can encapsulate cross-workspace queries using the `workspace()` expression, allowing an analytics rule to query multiple Log Analytics workspaces from a single rule definition. This approach efficiently reuses the union logic across rules without modifying each rule individually, addressing the limitation that built-in rules can only query their own workspace.

Keep practising

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…

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.