hardmultiple choiceObjective-mapped

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?

Question 1hardmultiple choice
Full question →

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?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Use Azure Lighthouse to delegate management and then create rules in the managing workspace that use workspace() expressions

Azure Lighthouse provides cross-tenant management but analytics rules still run within a single workspace's context; workspace() is available regardless of Lighthouse.

B

Best answer

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

A saved function can union data from multiple workspaces. The analytics rule can then query this function, effectively querying across workspaces.

C

Distractor review

Configure the analytics rule to run in Log Analytics workspace manager and use cross-workspace queries native to Copilot for Security

There is no 'Log Analytics workspace manager' feature for Sentinel; Copilot for Security is not used for cross-workspace analytics rules.

D

Distractor review

Enable cross-workspace incident view in Sentinel settings and define the rule in the central workspace to automatically query all linked workspaces

The cross-workspace incident view only aggregates incidents, not the underlying data for analytics rules.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

Question 1

A Microsoft Sentinel scheduled analytics rule detects impossible travel but creates too many duplicate incidents for the same user within a short period. Which two rule settings should you tune? (Choose 2.)

Question 2

A phishing email was delivered to several users. The analyst wants to find all messages in the campaign, see delivery actions, and perform remediation from the Microsoft 365 Defender portal. Which tool should they use?

Question 3

A security analyst in Microsoft Defender for Cloud receives an alert that an Azure VM has a vulnerability with a high severity. The analyst wants to see the detailed finding, including the steps to remediate. Which blade or page should the analyst open?

Question 4

A company uses Microsoft Defender for Cloud to protect an Azure Kubernetes Service (AKS) cluster. The security team wants to receive security alerts about suspicious activities within the cluster, such as a container running with root privileges or attempts to read sensitive host paths. Which Defender for Cloud plan must be enabled to generate these alerts?

Question 5

A security analyst is configuring Microsoft Sentinel scheduled analytics rules to detect brute-force attacks on Microsoft Entra ID. Arrange the steps in the correct order from first to last.

Question 6

An organization uses Microsoft 365 Defender. A security analyst is investigating a malware incident on a user's device. The automated investigation and response (AIR) has already isolated the device from the network. The analyst now needs to collect a copy of a specific suspicious file from the device for further analysis. Which action should the analyst initiate from the device's entity page?

FAQ

Questions learners often ask

What does this SC-200 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: 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 — Microsoft Sentinel supports cross-workspace querying through the use of workspace() expressions in KQL or by creating a function that unions tables from multiple workspaces. However, analytics rules can only run queries within the same workspace by default. To create an analytics rule that queries multiple workspaces, the best practice is to create a saved function that uses the union operator with workspace() to combine data from multiple workspaces, and then reference that function in the analytics rule query. Option A (Azure Lighthouse) allows managing multiple workspaces from one view but does not enable cross-workspace querying in analytics rules. Option B (Log Analytics workspace manager) is not a real feature; Copilot for Security is for natural language investigations. Option D (Sentinel's cross-workspace incident view) displays incidents from multiple workspaces but does not allow analytics rules to query across workspaces. The correct approach is to use KQL functions and union.

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

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.