SC-200 Question #257: Real Exam Question with Answer & Explanation

Question

Case Study 4 - Litware Inc Overview Adatum Corporation is a United States-based financial services company that has regional offices in New York, Chicago, and San Francisco. Existing Environment Identity Environment The on-premises network contains an Active Directory Domain Services (AD DS) forest named corp.adatum.com that syncs with an Azure AD tenant named adatum.com. All user and group management tasks are performed in corp.adatum.com. The corp.adatum.com domain contains a group named Group1 that syncs with adatum.com. Licensing Status All the users at Adatum are assigned a Microsoft 365 ES license and an Azure Active Directory Premium P2 license. Cloud Environment The cloud environment contains a Microsoft 365 subscription, an Azure subscription linked to the adatum.com tenant, and the resources shown in the following table. On-premises Environment The on-premises network contains the resources shown in the following table. Requirements Planned changes Adatum plans to perform the following changes: - Implement a query named rulequery1 that will include the following KQL query. - Implement a Microsoft Sentinel scheduled rule that generates incidents based on rulequery1. Microsoft Defender for Cloud Requirements Adatum identifies the following Microsoft Defender for Cloud requirements: - The members of Group1 must be able to enable Defender for Cloud plans and apply regulatory compliance initiatives. - Microsoft Defender for Servers Plan 2 must be enabled on all the Azure virtual machines. - Server2 must be excluded from agentless scanning. Microsoft Sentinel Requirements Adatum identifies the following Microsoft Sentinel requirements: - Implement an Advanced Security Information Model (ASIM) query that will return a count of DNS requests that results in an NXDOMAIN response from Infoblox1. - Ensure that multiple alerts generated by rulequery1 in response to a single user launching Azure Cloud Shell multiple times are consolidated as a single incident. - Implement the Windows Security Events via AMA connector for Microsoft Sentinel and configure it to monitor the Security event log of Server1. - Ensure that incidents generated by rulequery1 are closed automatically if Azure Cloud Shell is launched by the company's SecOps team. - Implement a custom Microsoft Sentinel workbook named Workbook1 that will include a query to dynamically retrieve data from Webapp1. - Implement a Microsoft Sentinel near-real-time (NRT) analytics rule that detects sign-ins to a designated break glass account. - Ensure that HuntingQuery1 runs automatically when the Hunting page of Microsoft Sentinel in the Azure portal is accessed. - Ensure that higher than normal volumes of password resets for corp.adatum.com user accounts are detected. - Minimize the overhead associated with queries that use ASIM parsers. - Ensure that the Group1 members can create and edit playbooks. - Use built-in ASIM parsers whenever possible. Business Requirements Adatum identifies the following business requirements: - Follow the principle of least privilege whenever possible. - Minimize administrative effort whenever possible. You need to ensure that the processing of incidents generated by rulequery1 meets the Microsoft Sentinel requirements. What should you create first?

Options

• Aa playbook with an incident trigger
• Ba playbook with an alert trigger
• Can Azure Automation rule
• Da playbook with an entity trigger

Explanation

This question is a partial prompt from a case study, implying a task related to automating actions based on security events. A playbook with an incident trigger is used when automation needs to be initiated by the creation or update of a Microsoft Sentinel incident.

Common mistakes.

• B. A playbook with an alert trigger initiates automation when a single alert is generated, which is less granular than an incident trigger that can aggregate multiple related alerts. Incident-based automation is generally preferred for broader security response workflows.
• C. An Azure Automation rule is a broader concept for automating tasks in Azure, but in the context of Sentinel's security orchestration, automation, and response (SOAR), playbooks (Logic Apps) are the dedicated solution.
• D. There is no standard "entity trigger" for Microsoft Sentinel playbooks; playbooks are primarily triggered by alerts or incidents.

Concept tested. Microsoft Sentinel playbook triggers

Reference. https://learn.microsoft.com/en-us/azure/sentinel/playbooks

No community discussion yet for this question.