SC500-SENTWS-001SC-500Study guide skill: Create and connect workspaces in Microsoft SentinelReviewed

Contoso has Microsoft Defender XDR and two Microsoft Sentinel workspaces in one tenant, WS-Global for the global SOC and WS-EU for an autonomous regional team. You're onboarding both workspaces to the Defender portal. The global SOC must see Defender XDR alerts correlated with its Sentinel alerts, and incidents in WS-EU must not include Defender XDR data. What should you do?

  1. A. Onboard WS-EU as the primary workspace and WS-Global as a secondary workspaceIncorrect
  2. B. Onboard WS-Global as the primary workspace and WS-EU as a secondary workspace.Correct
  3. C. Onboard both WS-Global and WS-EU as primary workspaces.Incorrect
  4. D. Onboard both WS-Global and WS-EU as secondary workspacesIncorrect
Show answer and explanation

Answer: B

Explanation

Alerts from the primary workspace are correlated with Defender XDR data, and all Defender XDR alerts and incidents are synced to the primary workspace only.[1] Incidents in secondary workspaces don’t include data from any other workspace or from Defender XDR, and the article suggests using the primary workspace for the global SOC, so B is correct.[1]

In A, WS-EU becomes the primary workspace, so its incidents include Defender XDR alerts, and WS-Global as a secondary workspace doesn’t receive Defender XDR alerts or incidents, because the Defender XDR connector for incidents and alerts is connected to the primary workspace only.[1] The Defender portal supports one primary workspace per tenant, so C isn’t possible.[1] One primary workspace must always be connected to the Defender portal, so D isn’t possible either.[1]


Sources

  1. Multiple Microsoft Sentinel workspaces in the Defender portalMicrosoft Learn · Location: Primary and secondary workspaces · Checked