Microsoft SC-200 Practice Test 23
Question 220
The original problem was: A legacy on-premises Windows fleet sends selected events to one collection server. The solution is operating, but a new network segment cannot reach the original collector. What should change next?
- A sample event from a remote host reaches the collector and target workspace
- Deploy or configure an appropriately reachable approved collector path
- Assume every legacy server can write directly into Sentinel without a defined collector path
- Plan Windows Event Forwarding to a collector with supported AMA ingestion
Explanation
Correct Answer
B:Correct follow-up. The requirement changed to: A new network segment cannot reach the original collector. Therefore Deploy or configure an appropriately reachable approved collector path is appropriate for A legacy on-premises Windows fleet sends selected events to one collection server, in addition to the previous measure.
Incorrect Answers
A:An observation is not the additional configuration or response action requested. The change is A new network segment cannot reach the original collector, so the proper follow-up must address it rather than merely note A sample event from a remote host reaches the collector and target workspace.
C:This was already unsuitable under the original condition because unsupported or unconfigured forwarding leaves gaps in the intended telemetry. It also fails after the change affecting A legacy on-premises Windows fleet sends selected events to one collection server.
D:This was the original control already implemented: Plan Windows Event Forwarding to a collector with supported AMA ingestion. Its original rationale was: WEF centralizes Windows event forwarding before collection to the monitoring workspace. For the initial setting (A legacy on-premises Windows fleet sends selected events to one collection server), that does not itself meet the new condition: A new network segment cannot reach the original collector.
Question 221
A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events. Select TWO entries that identify a sound initial security action and evidence that it worked. (Select TWO.)
- Investigate token-based access, sessions and affected applications and revoke where supported
- A sample event from a remote host reaches the collector and target workspace
- Assume every legacy server can write directly into Sentinel without a defined collector path
- Plan Windows Event Forwarding to a collector with supported AMA ingestion
- Deploy or configure an appropriately reachable approved collector path
Explanation
Correct Answers
B:Correct validation criterion. A sample event from a remote host reaches the collector and target workspace. This observable finding confirms the goal in the scenario: A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events.
D:WEF centralizes Windows event forwarding before collection to the monitoring workspace. The selected action is: Plan Windows Event Forwarding to a collector with supported AMA ingestion.
Incorrect Answers
A:That action serves a separate case (A stolen session token permits access even though an account's password was changed) in the Respond to security incidents domain. It does not specifically address the initial case.
C:Unsupported or unconfigured forwarding leaves gaps in the intended telemetry. The shortcut Assume every legacy server can write directly into Sentinel without a defined collector path does not resolve the case involving A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events.
E:This action would become suitable if a later condition arose: A new network segment cannot reach the original collector. It is not the immediate answer to A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events.
Question 222
A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events. Which statement BEST explains why the proposed approach (Assume every legacy server can write directly into Sentinel without a defined collector path) fails?
- WEF centralizes Windows event forwarding before collection to the monitoring workspace
- Unsupported or unconfigured forwarding leaves gaps in the intended telemetry
- A familiar product name alone establishes that the proposal is safe.
- Session and application tokens may have separate revocation behavior
Explanation
Correct Answer
B:Unsupported or unconfigured forwarding leaves gaps in the intended telemetry. This directly explains the defect in Assume every legacy server can write directly into Sentinel without a defined collector path for A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events.
Incorrect Answers
A:This describes the reason for the preferred control, Plan Windows Event Forwarding to a collector with supported AMA ingestion: WEF centralizes Windows event forwarding before collection to the monitoring workspace. It is not the direct defect in the proposed shortcut for A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events.
C:Product-name familiarity cannot validate a proposed security action. For A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events, the actual issue is that unsupported or unconfigured forwarding leaves gaps in the intended telemetry.
D:That concern applies to another security scenario (A stolen session token permits access even though an account's password was changed). Here, A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events, the specified proposal fails because unsupported or unconfigured forwarding leaves gaps in the intended telemetry.
Question 223
A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events. Which operational finding would validate the selected solution, Plan Windows Event Forwarding to a collector with supported AMA ingestion?
- Post-remediation session evidence shows unauthorized requests cease
- The team schedules a future check of whether a sample event from a remote host reaches the collector and target workspace, without recording any observed result.
- A sample event from a remote host reaches the collector and target workspace
- The SOC approves Plan Windows Event Forwarding to a collector with supported AMA ingestion on paper but has not tested its operation.
Explanation
Correct Answer
C:Correct observed evidence. A sample event from a remote host reaches the collector and target workspace. Given the original requirement, that result would substantiate the selected action, Plan Windows Event Forwarding to a collector with supported AMA ingestion.
Incorrect Answers
A:This observation fits another setting (A stolen session token permits access even though an account's password was changed). It does not verify Plan Windows Event Forwarding to a collector with supported AMA ingestion against the original need.
B:A future validation plan is not an observed result. The actual verification should establish that a sample event from a remote host reaches the collector and target workspace, in the scenario involving A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events.
D:Approval records intent but not actual protection or investigation. For A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events, an operational outcome must demonstrate that a sample event from a remote host reaches the collector and target workspace.
Question 224
A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events. After the initial control is implemented, a new network segment cannot reach the original collector. What is the best follow-up action?
- Post-remediation session evidence shows unauthorized requests cease
- Plan Windows Event Forwarding to a collector with supported AMA ingestion
- Assume every legacy server can write directly into Sentinel without a defined collector path
- Deploy or configure an appropriately reachable approved collector path
Explanation
Correct Answer
D:Correct follow-up. The requirement changed to: A new network segment cannot reach the original collector. Therefore Deploy or configure an appropriately reachable approved collector path is appropriate for A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events, in addition to the previous measure.
Incorrect Answers
A:An observation is not the additional configuration or response action requested. The change is A new network segment cannot reach the original collector, so the proper follow-up must address it rather than merely note Post-remediation session evidence shows unauthorized requests cease.
B:This was the original control already implemented: Plan Windows Event Forwarding to a collector with supported AMA ingestion. Its original rationale was: WEF centralizes Windows event forwarding before collection to the monitoring workspace. For the initial setting (A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events), that does not itself meet the new condition: A new network segment cannot reach the original collector.
C:This was already unsuitable under the original condition because unsupported or unconfigured forwarding leaves gaps in the intended telemetry. It also fails after the change affecting A hybrid enterprise wants to reduce per-host complexity when forwarding on-prem security events.
Question 225
A Linux bastion host must send authentication and sudo events into Sentinel. Which action BEST addresses this Microsoft security operations requirement?
- Configure Syslog via AMA and select relevant facilities and severities in the DCR
- Add that syslog facility and severity to the DCR and test ingestion
- Review file evidence, prevalence and trusted certificate metadata in Defender
- Configure Windows Event Forwarding as the sole Linux log connector
Explanation
Correct Answer
A:Syslog via AMA collects selected Linux facility and severity events into workspace tables. The selected action is: Configure Syslog via AMA and select relevant facilities and severities in the DCR.
Incorrect Answers
B:This action would become suitable if a later condition arose: The fleet emits an important new custom local facility. It is not the immediate answer to A Linux bastion host must send authentication and sudo events into Sentinel.
C:That action serves a separate case (An investigator needs file prevalence and certificate information before deciding scope) in the Respond to security incidents domain. It does not specifically address the initial case.
D:Windows forwarding mechanisms do not ingest Linux syslog by themselves. The shortcut Configure Windows Event Forwarding as the sole Linux log connector does not resolve the case involving A Linux bastion host must send authentication and sudo events into Sentinel.
Question 226
A Linux bastion host must send authentication and sudo events into Sentinel. A colleague suggests: Configure Windows Event Forwarding as the sole Linux log connector. What is the MOST important technical defect in this suggestion?
- Syslog via AMA collects selected Linux facility and severity events into workspace tables
- A familiar product name alone establishes that the proposal is safe.
- Windows forwarding mechanisms do not ingest Linux syslog by themselves
- Attackers can misuse signed binaries and legitimate dual-use utilities
Explanation
Correct Answer
C:Windows forwarding mechanisms do not ingest Linux syslog by themselves. This directly explains the defect in Configure Windows Event Forwarding as the sole Linux log connector for A Linux bastion host must send authentication and sudo events into Sentinel.
Incorrect Answers
A:This describes the reason for the preferred control, Configure Syslog via AMA and select relevant facilities and severities in the DCR: Syslog via AMA collects selected Linux facility and severity events into workspace tables. It is not the direct defect in the proposed shortcut for A Linux bastion host must send authentication and sudo events into Sentinel.
B:Product-name familiarity cannot validate a proposed security action. For A Linux bastion host must send authentication and sudo events into Sentinel, the actual issue is that windows forwarding mechanisms do not ingest Linux syslog by themselves.
D:That concern applies to another security scenario (An investigator needs file prevalence and certificate information before deciding scope). Here, A Linux bastion host must send authentication and sudo events into Sentinel, the specified proposal fails because windows forwarding mechanisms do not ingest Linux syslog by themselves.
Question 227
A Linux bastion host must send authentication and sudo events into Sentinel. After implementing Configure Syslog via AMA and select relevant facilities and severities in the DCR, what result would BEST establish that it worked?
- The team schedules a future check of whether test auth events appear in the expected Syslog table with host and severity, without recording any observed result.
- Test auth events appear in the expected Syslog table with host and severity
- The SOC approves Configure Syslog via AMA and select relevant facilities and severities in the DCR on paper but has not tested its operation.
- Evidence records hash, signature context, prevalence and execution chain
Explanation
Correct Answer
B:Correct observed evidence. Test auth events appear in the expected Syslog table with host and severity. Given the original requirement, that result would substantiate the selected action, Configure Syslog via AMA and select relevant facilities and severities in the DCR.
Incorrect Answers
A:A future validation plan is not an observed result. The actual verification should establish that test auth events appear in the expected Syslog table with host and severity, in the scenario involving A Linux bastion host must send authentication and sudo events into Sentinel.
C:Approval records intent but not actual protection or investigation. For A Linux bastion host must send authentication and sudo events into Sentinel, an operational outcome must demonstrate that test auth events appear in the expected Syslog table with host and severity.
D:This observation fits another setting (An investigator needs file prevalence and certificate information before deciding scope). It does not verify Configure Syslog via AMA and select relevant facilities and severities in the DCR against the original need.
Question 228
A Linux bastion host must send authentication and sudo events into Sentinel. The original measure is in place. A new requirement arises: The fleet emits an important new custom local facility. Which ADDITIONAL action BEST fits?
- Add that syslog facility and severity to the DCR and test ingestion
- Test auth events appear in the expected Syslog table with host and severity
- Configure Syslog via AMA and select relevant facilities and severities in the DCR
- Configure Windows Event Forwarding as the sole Linux log connector
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: The fleet emits an important new custom local facility. Therefore Add that syslog facility and severity to the DCR and test ingestion is appropriate for A Linux bastion host must send authentication and sudo events into Sentinel, in addition to the previous measure.
Incorrect Answers
B:An observation is not the additional configuration or response action requested. The change is The fleet emits an important new custom local facility, so the proper follow-up must address it rather than merely note Test auth events appear in the expected Syslog table with host and severity.
C:This was the original control already implemented: Configure Syslog via AMA and select relevant facilities and severities in the DCR. Its original rationale was: Syslog via AMA collects selected Linux facility and severity events into workspace tables. For the initial setting (A Linux bastion host must send authentication and sudo events into Sentinel), that does not itself meet the new condition: The fleet emits an important new custom local facility.
D:This was already unsuitable under the original condition because windows forwarding mechanisms do not ingest Linux syslog by themselves. It also fails after the change affecting A Linux bastion host must send authentication and sudo events into Sentinel.
Question 229
A security operations analyst must handle this situation: A security analyst wants Linux syslog facility filtering for an AMA-managed server. What is the BEST initial response?
- Assign suitable Purview audit or investigation roles and verify privacy requirements
- Configure Syslog via AMA and select relevant facilities and severities in the DCR
- Add that syslog facility and severity to the DCR and test ingestion
- Configure Windows Event Forwarding as the sole Linux log connector
Explanation
Correct Answer
B:Syslog via AMA collects selected Linux facility and severity events into workspace tables. The selected action is: Configure Syslog via AMA and select relevant facilities and severities in the DCR.
Incorrect Answers
A:That action serves a separate case (A SOC is asked to search Microsoft 365 user activity but lacks access to detailed audit results) in the Respond to security incidents domain. It does not specifically address the initial case.
C:This action would become suitable if a later condition arose: The fleet emits an important new custom local facility. It is not the immediate answer to A security analyst wants Linux syslog facility filtering for an AMA-managed server.
D:Windows forwarding mechanisms do not ingest Linux syslog by themselves. The shortcut Configure Windows Event Forwarding as the sole Linux log connector does not resolve the case involving A security analyst wants Linux syslog facility filtering for an AMA-managed server.
Question 230
A security analyst wants Linux syslog facility filtering for an AMA-managed server. Why should the SOC reject the proposed shortcut: Configure Windows Event Forwarding as the sole Linux log connector?
- Tenant-wide admin is excessive for narrowly scoped audit review
- A familiar product name alone establishes that the proposal is safe.
- Syslog via AMA collects selected Linux facility and severity events into workspace tables
- Windows forwarding mechanisms do not ingest Linux syslog by themselves
Explanation
Correct Answer
D:Windows forwarding mechanisms do not ingest Linux syslog by themselves. This directly explains the defect in Configure Windows Event Forwarding as the sole Linux log connector for A security analyst wants Linux syslog facility filtering for an AMA-managed server.
Incorrect Answers
A:That concern applies to another security scenario (A SOC is asked to search Microsoft 365 user activity but lacks access to detailed audit results). Here, A security analyst wants Linux syslog facility filtering for an AMA-managed server, the specified proposal fails because windows forwarding mechanisms do not ingest Linux syslog by themselves.
B:Product-name familiarity cannot validate a proposed security action. For A security analyst wants Linux syslog facility filtering for an AMA-managed server, the actual issue is that windows forwarding mechanisms do not ingest Linux syslog by themselves.
C:This describes the reason for the preferred control, Configure Syslog via AMA and select relevant facilities and severities in the DCR: Syslog via AMA collects selected Linux facility and severity events into workspace tables. It is not the direct defect in the proposed shortcut for A security analyst wants Linux syslog facility filtering for an AMA-managed server.