Sentinel Windows Security Events Connector for 200 Azure VMs

SC-500 By islever Editorial Last updated

Implement activity and event collection in Microsoft Sentinel

Short answer

B Use the Windows Security Events via AMA connector so the Azure Monitor Agent on each of the 200 Azure Windows Server VMs streams SecurityEvent data into the Sentinel workspace.

Question

You have a Microsoft Sentinel workspace.
You need to collect Windows security events from 200 Azure virtual machines that run Windows Server. The solution must meet the following requirements:
Use direct agent-based data collection from each virtual machine.
Use a supported agent for new virtual machine deployments.
Which Microsoft Sentinel connector should you use?
  1. Windows Forwarded Events
  2. Windows Security Events via AMA Correct Answer
  3. Security Events via Legacy Agent
  4. Syslog via AMA
  5. Azure Resource Graph

Key Takeaways

This question tests selecting modern AMA-based Windows Security Events collection over the legacy agent or forwarded-events paths, with traps around unsupported agents and non-Windows Syslog.

For 200 Azure Windows Server VMs requiring direct agent-based collection and a supported agent for new deployments, Microsoft Sentinel should use the Windows Security Events via AMA connector.

Common mistake: Choosing Security Events via Legacy Agent because it sounds like the classic Sentinel connector; the legacy Log Analytics agent is deprecated for new deployments and does not meet the supported-agent requirement.

Expert Analysis

Trace the ingestion path This question is about how Sentinel receives Windows event data, not about querying or forwarding. You have 200 Azure VMs running Windows Server, and the requirements force direct agent-based collection from each VM plus an agent that is supported for new deployments. In the AMA path, the Azure Monitor Agent extension is installed on each VM, a data collection rule (DCR) defines which Windows Security events to collect, and the agent sends those events to the Log Analytics workspace that backs Microsoft Sentinel. The events land in the SecurityEvent table for analytics rules and hunting queries.

Why option B is the match B, Windows Security Events via AMA, is the Sentinel connector built for this exact path. It uses the Azure Monitor Agent rather than the retired legacy agent, and it satisfies 'direct' because every Azure VM runs its own agent and streams from its local Windows Event Log without an intermediate forwarder. Comments on this question make the same point: the connector deploys the agent onto each VM and streams local event-log data into the workspace's SecurityEvent storage, with DCRs controlling collection. That is the mechanism the scenario asks you to select.

Eliminate the alternatives A, Windows Forwarded Events, depends on Windows Event Forwarding and a collector/forwarder tier, so it is not direct per-VM agent collection. C, Security Events via Legacy Agent, uses the deprecated Log Analytics agent and is a poor fit for 'supported agent for new virtual machine deployments.' D, Syslog via AMA, is for Syslog sources such as Linux or network appliances, not Windows Security event logs. E, Azure Resource Graph, is an inventory/query service and does not ingest event data into Sentinel at all.

Decision rule When the wording combines Windows Security events, Azure VMs, direct agent collection, and new deployments, choose the AMA-based Windows Security Events connector, B.

Official Reference

Exam Strategy

When a Sentinel question says direct agent-based collection and supported agent for new deployments, map both phrases to Azure Monitor Agent (AMA) and its DCR-based connector. Eliminate legacy Log Analytics agent options and collection paths that depend on forwarding servers or Syslog. Confirm the data source is Windows Security Events and that Azure VMs, not non-Azure hosts or network appliances, are in scope before choosing the connector.

Frequently Asked Questions

Does Windows Security Events via AMA collect from each Azure VM directly?

Yes. The AMA extension runs on each VM and uses a data collection rule to send Windows Security event data to the Sentinel workspace's SecurityEvent table.

Why not use Windows Forwarded Events for 200 Azure VMs?

Windows Forwarded Events depends on Windows Event Forwarding and a collector tier, not direct agent-based collection from each VM, so it does not meet the direct requirement.

Can Security Events via Legacy Agent be used for new Sentinel deployments?

It relies on the deprecated Log Analytics agent, so new deployments should use AMA-based Windows Security Events collection instead.

More SC-500 FAQ →

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 2 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 2

  1. Eltooth 👍 1 Answered B
    Direct Event Collection: The Windows Security Events via AMA connector deploys the agent directly onto each of your 200 virtual machines. It streams events cleanly from the local Windows Event Log systems straight into the workspace's designated SecurityEvent storage table. https://learn.microsoft.com/en-us/azure/azure-monitor/vm/data-collection-windows-events
  2. M15tin 👍 1 Answered B
    AMA (Azure Monitor Agent) permite recopilar directamente los eventos de seguridad de Windows desde cada una de las 200 máquinas virtuales y enviarlos a Microsoft Sentinel. AMA es el agente compatible para nuevas implementaciones y utiliza Data Collection Rules (DCR) para definir qué datos se recopilan.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Practice All SC-500 Questions

Access 100 questions with complete answers and detailed explanations.

View Full SC-500 Practice Test →

← Back to SC-500 Study Guide