Microsoft SC-200 Practice Test 11
Question 100
The original problem was: A Sentinel workspace receives incidents that must be tagged for a specific service owner. The solution is operating, but the owner mapping changes from one team to another. What should change next?
- Update the automation rule action and verify priority relative to other rules
- Build a scheduled analytics rule solely to assign an existing incident owner
- A generated matching incident receives the planned tag or assignment
- Create an incident-created Sentinel automation rule with appropriate conditions and actions
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: The owner mapping changes from one team to another. Therefore Update the automation rule action and verify priority relative to other rules is appropriate for A Sentinel workspace receives incidents that must be tagged for a specific service owner, in addition to the previous measure.
Incorrect Answers
B:This was already unsuitable under the original condition because detection rule creation is not required to perform ordinary incident assignment. It also fails after the change affecting A Sentinel workspace receives incidents that must be tagged for a specific service owner.
C:An observation is not the additional configuration or response action requested. The change is The owner mapping changes from one team to another, so the proper follow-up must address it rather than merely note A generated matching incident receives the planned tag or assignment.
D:This was the original control already implemented: Create an incident-created Sentinel automation rule with appropriate conditions and actions. Its original rationale was: Automation rules can tag, assign, or change incidents when their supported triggers and filters match. For the initial setting (A Sentinel workspace receives incidents that must be tagged for a specific service owner), that does not itself meet the new condition: The owner mapping changes from one team to another.
Question 101
A security team wants newly created high-severity incidents automatically assigned to the on-call queue. Which configuration or investigation step is MOST appropriate?
- Create an incident-created Sentinel automation rule with appropriate conditions and actions
- Update the automation rule action and verify priority relative to other rules
- Build a scheduled analytics rule solely to assign an existing incident owner
- Apply the organization's approved secure evidence repository and chain-of-custody procedure
Explanation
Correct Answer
A:Automation rules can tag, assign, or change incidents when their supported triggers and filters match. The selected action is: Create an incident-created Sentinel automation rule with appropriate conditions and actions.
Incorrect Answers
B:This action would become suitable if a later condition arose: The owner mapping changes from one team to another. It is not the immediate answer to A security team wants newly created high-severity incidents automatically assigned to the on-call queue.
C:Detection rule creation is not required to perform ordinary incident assignment. The shortcut Build a scheduled analytics rule solely to assign an existing incident owner does not resolve the case involving A security team wants newly created high-severity incidents automatically assigned to the on-call queue.
D:That action serves a separate case (An incident package must be shared internally with a forensic team without exposing secrets) in the Respond to security incidents domain. It does not specifically address the initial case.
Question 102
A security team wants newly created high-severity incidents automatically assigned to the on-call queue. Which statement BEST explains why the proposed approach (Build a scheduled analytics rule solely to assign an existing incident owner) fails?
- A familiar product name alone establishes that the proposal is safe.
- Detection rule creation is not required to perform ordinary incident assignment
- Automation rules can tag, assign, or change incidents when their supported triggers and filters match
- Public sharing may disclose personal and security-sensitive information
Explanation
Correct Answer
B:Detection rule creation is not required to perform ordinary incident assignment. This directly explains the defect in Build a scheduled analytics rule solely to assign an existing incident owner for A security team wants newly created high-severity incidents automatically assigned to the on-call queue.
Incorrect Answers
A:Product-name familiarity cannot validate a proposed security action. For A security team wants newly created high-severity incidents automatically assigned to the on-call queue, the actual issue is that detection rule creation is not required to perform ordinary incident assignment.
C:This describes the reason for the preferred control, Create an incident-created Sentinel automation rule with appropriate conditions and actions: Automation rules can tag, assign, or change incidents when their supported triggers and filters match. It is not the direct defect in the proposed shortcut for A security team wants newly created high-severity incidents automatically assigned to the on-call queue.
D:That concern applies to another security scenario (An incident package must be shared internally with a forensic team without exposing secrets). Here, A security team wants newly created high-severity incidents automatically assigned to the on-call queue, the specified proposal fails because detection rule creation is not required to perform ordinary incident assignment.
Question 103
A security team wants newly created high-severity incidents automatically assigned to the on-call queue. Which operational finding would validate the selected solution, Create an incident-created Sentinel automation rule with appropriate conditions and actions?
- The team schedules a future check of whether a generated matching incident receives the planned tag or assignment, without recording any observed result.
- Access logs and checksums show controlled handling of the collected evidence
- The SOC approves Create an incident-created Sentinel automation rule with appropriate conditions and actions on paper but has not tested its operation.
- A generated matching incident receives the planned tag or assignment
Explanation
Correct Answer
D:Correct observed evidence. A generated matching incident receives the planned tag or assignment. Given the original requirement, that result would substantiate the selected action, Create an incident-created Sentinel automation rule with appropriate conditions and actions.
Incorrect Answers
A:A future validation plan is not an observed result. The actual verification should establish that a generated matching incident receives the planned tag or assignment, in the scenario involving A security team wants newly created high-severity incidents automatically assigned to the on-call queue.
B:This observation fits another setting (An incident package must be shared internally with a forensic team without exposing secrets). It does not verify Create an incident-created Sentinel automation rule with appropriate conditions and actions against the original need.
C:Approval records intent but not actual protection or investigation. For A security team wants newly created high-severity incidents automatically assigned to the on-call queue, an operational outcome must demonstrate that a generated matching incident receives the planned tag or assignment.
Question 104
A security team wants newly created high-severity incidents automatically assigned to the on-call queue. After the initial control is implemented, the owner mapping changes from one team to another. What is the best follow-up action?
- Access logs and checksums show controlled handling of the collected evidence
- Create an incident-created Sentinel automation rule with appropriate conditions and actions
- Update the automation rule action and verify priority relative to other rules
- Build a scheduled analytics rule solely to assign an existing incident owner
Explanation
Correct Answer
C:Correct follow-up. The requirement changed to: The owner mapping changes from one team to another. Therefore Update the automation rule action and verify priority relative to other rules is appropriate for A security team wants newly created high-severity incidents automatically assigned to the on-call queue, in addition to the previous measure.
Incorrect Answers
A:An observation is not the additional configuration or response action requested. The change is The owner mapping changes from one team to another, so the proper follow-up must address it rather than merely note Access logs and checksums show controlled handling of the collected evidence.
B:This was the original control already implemented: Create an incident-created Sentinel automation rule with appropriate conditions and actions. Its original rationale was: Automation rules can tag, assign, or change incidents when their supported triggers and filters match. For the initial setting (A security team wants newly created high-severity incidents automatically assigned to the on-call queue), that does not itself meet the new condition: The owner mapping changes from one team to another.
D:This was already unsuitable under the original condition because detection rule creation is not required to perform ordinary incident assignment. It also fails after the change affecting A security team wants newly created high-severity incidents automatically assigned to the on-call queue.
Question 105
A security operations team wants to alert a paging system and enrich new Sentinel incidents. Which action BEST addresses this Microsoft security operations requirement?
- Normalize timestamps and correlate operation, app ID, account and target across both sources
- Update the Logic Apps connection and retest the playbook trigger and action
- Expect an ordinary workbook visualization to send the incident to an external ticket queue
- Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule
Explanation
Correct Answer
D:Logic Apps playbooks implement connected response workflows beyond simple built-in incident actions. The selected action is: Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule.
Incorrect Answers
A:That action serves a separate case (A threat hunter needs a unified chronology from Purview Audit and Microsoft Graph activity logs) in the Respond to security incidents domain. It does not specifically address the initial case.
B:This action would become suitable if a later condition arose: The external system API begins requiring new authentication. It is not the immediate answer to A security operations team wants to alert a paging system and enrich new Sentinel incidents.
C:Workbooks visualize data but are not themselves orchestration workflows. The shortcut Expect an ordinary workbook visualization to send the incident to an external ticket queue does not resolve the case involving A security operations team wants to alert a paging system and enrich new Sentinel incidents.
Question 106
A security operations team wants to alert a paging system and enrich new Sentinel incidents. A colleague suggests: Expect an ordinary workbook visualization to send the incident to an external ticket queue. What is the MOST important technical defect in this suggestion?
- Time proximity alone does not establish a causal connection
- Logic Apps playbooks implement connected response workflows beyond simple built-in incident actions
- A familiar product name alone establishes that the proposal is safe.
- Workbooks visualize data but are not themselves orchestration workflows
Explanation
Correct Answer
D:Workbooks visualize data but are not themselves orchestration workflows. This directly explains the defect in Expect an ordinary workbook visualization to send the incident to an external ticket queue for A security operations team wants to alert a paging system and enrich new Sentinel incidents.
Incorrect Answers
A:That concern applies to another security scenario (A threat hunter needs a unified chronology from Purview Audit and Microsoft Graph activity logs). Here, A security operations team wants to alert a paging system and enrich new Sentinel incidents, the specified proposal fails because workbooks visualize data but are not themselves orchestration workflows.
B:This describes the reason for the preferred control, Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule: Logic Apps playbooks implement connected response workflows beyond simple built-in incident actions. It is not the direct defect in the proposed shortcut for A security operations team wants to alert a paging system and enrich new Sentinel incidents.
C:Product-name familiarity cannot validate a proposed security action. For A security operations team wants to alert a paging system and enrich new Sentinel incidents, the actual issue is that workbooks visualize data but are not themselves orchestration workflows.
Question 107
A security operations team wants to alert a paging system and enrich new Sentinel incidents. After implementing Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule, what result would BEST establish that it worked?
- An incident triggers a permitted playbook run and the external ticket receives intended fields
- The SOC approves Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule on paper but has not tested its operation.
- The team schedules a future check of whether an incident triggers a permitted playbook run and the external ticket receives intended fields, without recording any observed result.
- A verified actor or application link ties the two event streams into a timeline
Explanation
Correct Answer
A:Correct observed evidence. An incident triggers a permitted playbook run and the external ticket receives intended fields. Given the original requirement, that result would substantiate the selected action, Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule.
Incorrect Answers
B:Approval records intent but not actual protection or investigation. For A security operations team wants to alert a paging system and enrich new Sentinel incidents, an operational outcome must demonstrate that an incident triggers a permitted playbook run and the external ticket receives intended fields.
C:A future validation plan is not an observed result. The actual verification should establish that an incident triggers a permitted playbook run and the external ticket receives intended fields, in the scenario involving A security operations team wants to alert a paging system and enrich new Sentinel incidents.
D:This observation fits another setting (A threat hunter needs a unified chronology from Purview Audit and Microsoft Graph activity logs). It does not verify Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule against the original need.
Question 108
A security operations team wants to alert a paging system and enrich new Sentinel incidents. The original measure is in place. A new requirement arises: The external system API begins requiring new authentication. Which ADDITIONAL action BEST fits?
- Expect an ordinary workbook visualization to send the incident to an external ticket queue
- Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule
- An incident triggers a permitted playbook run and the external ticket receives intended fields
- Update the Logic Apps connection and retest the playbook trigger and action
Explanation
Correct Answer
D:Correct follow-up. The requirement changed to: The external system API begins requiring new authentication. Therefore Update the Logic Apps connection and retest the playbook trigger and action is appropriate for A security operations team wants to alert a paging system and enrich new Sentinel incidents, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because workbooks visualize data but are not themselves orchestration workflows. It also fails after the change affecting A security operations team wants to alert a paging system and enrich new Sentinel incidents.
B:This was the original control already implemented: Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule. Its original rationale was: Logic Apps playbooks implement connected response workflows beyond simple built-in incident actions. For the initial setting (A security operations team wants to alert a paging system and enrich new Sentinel incidents), that does not itself meet the new condition: The external system API begins requiring new authentication.
C:An observation is not the additional configuration or response action requested. The change is The external system API begins requiring new authentication, so the proper follow-up must address it rather than merely note An incident triggers a permitted playbook run and the external ticket receives intended fields.
Question 109
A security operations analyst must handle this situation: A customer response process needs an HTTP workflow after specific Sentinel incidents are created. What is the BEST initial response?
- Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule
- Expect an ordinary workbook visualization to send the incident to an external ticket queue
- Update the Logic Apps connection and retest the playbook trigger and action
- Investigate Defender for Cloud Apps activity and apply supported app or session controls
Explanation
Correct Answer
A:Logic Apps playbooks implement connected response workflows beyond simple built-in incident actions. The selected action is: Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule.
Incorrect Answers
B:Workbooks visualize data but are not themselves orchestration workflows. The shortcut Expect an ordinary workbook visualization to send the incident to an external ticket queue does not resolve the case involving A customer response process needs an HTTP workflow after specific Sentinel incidents are created.
C:This action would become suitable if a later condition arose: The external system API begins requiring new authentication. It is not the immediate answer to A customer response process needs an HTTP workflow after specific Sentinel incidents are created.
D:That action serves a separate case (Defender for Cloud Apps detects impossible-travel cloud sign-ins for a privileged account) in the Respond to security incidents domain. It does not specifically address the initial case.
Question 110
A customer response process needs an HTTP workflow after specific Sentinel incidents are created. Why should the SOC reject the proposed shortcut: Expect an ordinary workbook visualization to send the incident to an external ticket queue?
- MFA does not rule out session hijacking or misuse of authorized access
- Workbooks visualize data but are not themselves orchestration workflows
- A familiar product name alone establishes that the proposal is safe.
- Logic Apps playbooks implement connected response workflows beyond simple built-in incident actions
Explanation
Correct Answer
B:Workbooks visualize data but are not themselves orchestration workflows. This directly explains the defect in Expect an ordinary workbook visualization to send the incident to an external ticket queue for A customer response process needs an HTTP workflow after specific Sentinel incidents are created.
Incorrect Answers
A:That concern applies to another security scenario (Defender for Cloud Apps detects impossible-travel cloud sign-ins for a privileged account). Here, A customer response process needs an HTTP workflow after specific Sentinel incidents are created, the specified proposal fails because workbooks visualize data but are not themselves orchestration workflows.
C:Product-name familiarity cannot validate a proposed security action. For A customer response process needs an HTTP workflow after specific Sentinel incidents are created, the actual issue is that workbooks visualize data but are not themselves orchestration workflows.
D:This describes the reason for the preferred control, Use a Sentinel playbook based on Azure Logic Apps and invoke it through an appropriate automation rule: Logic Apps playbooks implement connected response workflows beyond simple built-in incident actions. It is not the direct defect in the proposed shortcut for A customer response process needs an HTTP workflow after specific Sentinel incidents are created.