100% Latest & Updated Microsoft AZ-801 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 80
An engineer attempts to remove old NTLM support before verifying that every forest trust path handles required Kerberos flows. What change should be prioritized to restore the intended behavior?
- Audit NTLM authentication usage and migrate dependencies before selecting explicit deny policies.
- Validate cross-domain trust/authentication scenarios in audit before enforcing the NTLM restriction.
- Migrate that service to supported Kerberos or other stronger authentication then restrict NTLM at its boundary.
- Enable and centrally collect the required directory and security-group change audit events.
Explanation
Correct Answer
B:Cross-forest and legacy application flows may have different authentication requirements from local DC tests. A suitable corrective action is to validate cross-domain trust/authentication scenarios in audit before enforcing the NTLM restriction.
Incorrect Answers
A:Abruptly disabling NTLM can break services relying on legacy authentication. In this situation, cross-forest and legacy application flows may have different authentication requirements from local DC tests.
C:NTLM auditing identifies exact dependencies that can be removed without domain-wide outage. Here, cross-forest and legacy application flows may have different authentication requirements from local DC tests.
D:Account lockout telemetry does not record all privileged membership modifications. In this situation, cross-forest and legacy application flows may have different authentication requirements from local DC tests.
Question 81
An Azure Arc-connected branch server sends AMA heartbeats to Log Analytics but has no Windows Security Events DCR association and no security events in Sentinel. What should the administrator change first?
- Confirm the Azure Monitor Agent heartbeat and restart the agent, but leave Windows Security Events via AMA collection unconfigured.
- Check the Sentinel workspace dashboard but leave the Windows Security Events collection rule absent.
- Configure the Windows Security Events connector and Azure Monitor Agent data collection rules for that machine.
- Broaden a Sentinel KQL query to include every table while leaving the branch server without the required Security Events collection configuration.
Explanation
Correct Answer
C:Heartbeat connectivity does not mean the Windows Security event stream is selected for collection. The targeted remedy is to configure the Windows Security Events connector and Azure Monitor Agent data collection rules for that machine.
Incorrect Answers
A:Heartbeat data shows that the monitored machine communicates with a workspace; it doesn't establish that Security audit events are selected by a rule and routed to Sentinel's SecurityEvent table. Without the connector and collection configuration, the missing event stream remains missing.
B:Workspace monitoring cannot generate events the Azure Monitor Agent was never instructed to collect. An associated security-event DCR is required in addition to a working heartbeat.
D:A wider query cannot display an event that no connector and data collection rule sent to the workspace. Agent heartbeat demonstrates connectivity, not the SecurityEvent collection configuration.
Question 82
A Sentinel query returns Windows Security logs from domain controllers but no 4625 failures from new member servers. Which configuration or recovery action best matches this evidence?
- Change the event ID filter on the domain controllers' already-working rule without associating the new member servers with a suitable DCR.
- Modify the existing domain-controller-only Security Events connector to collect additional event IDs while excluding the new member-server resource scope.
- Add the appropriate PowerShell operational/security logging sources and ingest the supported event channels.
- Check the affected machines' DCR association and Windows Security event selection.
Explanation
Correct Answer
D:Check the affected machines' DCR association and Windows Security event selection. This addresses the condition because collection rules must be associated with each data source and include the desired event set.
Incorrect Answers
A:Domain-controller data is already arriving. Editing its working selection does not cause unassociated member servers to send security failures; collection scope and association must include those machines.
B:The domain controllers already supply the relevant failures. The missing member servers need a security-event collection association; changing the working controller filters cannot create events for excluded machines.
C:Threat-detection coverage depends on the selected event channels rather than generic Windows uptime metrics. However, collection rules must be associated with each data source and include the desired event set.
Question 83
The SOC enables Windows Security Events collection but only one Azure workspace receives data while detections run in another. Which administrative change most directly resolves the documented failure?
- Validate the data collection destination workspace and route the affected server events to the intended Sentinel-connected workspace.
- Configure the Windows Security Events connector and Azure Monitor Agent data collection rules for that machine.
- Check the affected machines' DCR association and Windows Security event selection.
- Map the Azure Monitor DCR destination region, retention and access scope to the approved governance requirements.
Explanation
Correct Answer
A:A working agent can send data to the wrong Log Analytics workspace without populating the detection environment. For that reason, validate the data collection destination workspace and route the affected server events to the intended Sentinel-connected workspace.
Incorrect Answers
B:Heartbeat connectivity does not mean the Windows Security event stream is selected for collection. However, a working agent can send data to the wrong Log Analytics workspace without populating the detection environment.
C:Collection rules must be associated with each data source and include the desired event set. Here, a working agent can send data to the wrong Log Analytics workspace without populating the detection environment.
D:The workspace and data collection destination define where security telemetry is stored and controlled. In this situation, a working agent can send data to the wrong Log Analytics workspace without populating the detection environment.
Question 84
A Windows server is fully offline and its security logs cannot reach the Sentinel ingestion endpoint, but analysts edit KQL detections. Which implementation step directly corrects the underlying problem?
- Compare TimeGenerated, ingestion delay and source timestamps before adjusting detection windows.
- Restore the appropriate agent network connectivity and ingestion path before changing detection queries.
- Inspect Azure Monitor Agent extension health, machine identity and secure endpoint connectivity.
- Check the affected machines' DCR association and Windows Security event selection.
Explanation
Correct Answer
B:Restore the appropriate agent network connectivity and ingestion path before changing detection queries. The underlying technical reason is that search logic cannot find source events that were never transmitted or indexed.
Incorrect Answers
A:Event-time versus ingestion-time mismatch can hide or duplicate incidents in time-bounded queries. However, search logic cannot find source events that were never transmitted or indexed.
C:A healthy KQL rule cannot compensate for a broken collection agent or authentication channel. In this situation, search logic cannot find source events that were never transmitted or indexed.
D:Collection rules must be associated with each data source and include the desired event set. However, search logic cannot find source events that were never transmitted or indexed.
Question 85
A custom Sentinel analytics rule relies on raw EventID strings but the data source is WindowsEvent rather than SecurityEvent. Which configuration or recovery action best matches this evidence?
- Configure the Windows Security Events connector and Azure Monitor Agent data collection rules for that machine.
- Inspect Azure Monitor Agent extension health, machine identity and secure endpoint connectivity.
- Match the KQL query to the actual table and schema produced by the enabled connector.
- Map the Azure Monitor DCR destination region, retention and access scope to the approved governance requirements.
Explanation
Correct Answer
C:Correct detection logic must use the event table and field names populated by the selected collection path. A suitable corrective action is to match the KQL query to the actual table and schema produced by the enabled connector.
Incorrect Answers
A:Heartbeat connectivity does not mean the Windows Security event stream is selected for collection. Here, correct detection logic must use the event table and field names populated by the selected collection path.
B:A healthy KQL rule cannot compensate for a broken collection agent or authentication channel. In this situation, correct detection logic must use the event table and field names populated by the selected collection path.
D:The workspace and data collection destination define where security telemetry is stored and controlled. Here, correct detection logic must use the event table and field names populated by the selected collection path.
Question 86
After reducing event volume, administrators remove logon event categories and complain that suspicious login detections stopped firing. Which administrative change most directly resolves the documented failure?
- Associate additional machines with the same DCR while leaving the logon event category removed from its selection.
- Configure the Windows Security Events connector and Azure Monitor Agent data collection rules for that machine.
- Add the appropriate PowerShell operational/security logging sources and ingest the supported event channels.
- Restore the minimally required Windows Security event selection and validate an intentional test logon.
Explanation
Correct Answer
D:Excluding the signal at collection time prevents any downstream alert from evaluating it. The targeted remedy is to restore the minimally required Windows Security event selection and validate an intentional test logon.
Incorrect Answers
A:A data collection rule cannot forward an event category it no longer selects, regardless of how many machines are associated. The missing logon events need to be restored in the rule first.
B:Heartbeat connectivity does not mean the Windows Security event stream is selected for collection. However, excluding the signal at collection time prevents any downstream alert from evaluating it.
C:Threat-detection coverage depends on the selected event channels rather than generic Windows uptime metrics. Here, excluding the signal at collection time prevents any downstream alert from evaluating it.
Question 87
A Sentinel alert is based on events delayed twenty minutes but rules treat ingestion time as event occurrence time. What would be the most defensible next action based on the observed symptoms?
- Compare TimeGenerated, ingestion delay and source timestamps before adjusting detection windows.
- Restore the appropriate agent network connectivity and ingestion path before changing detection queries.
- Map the Azure Monitor DCR destination region, retention and access scope to the approved governance requirements.
- Check the affected machines' DCR association and Windows Security event selection.
Explanation
Correct Answer
A:Compare TimeGenerated, ingestion delay and source timestamps before adjusting detection windows. This addresses the condition because event-time versus ingestion-time mismatch can hide or duplicate incidents in time-bounded queries.
Incorrect Answers
B:Search logic cannot find source events that were never transmitted or indexed. Here, event-time versus ingestion-time mismatch can hide or duplicate incidents in time-bounded queries.
C:The workspace and data collection destination define where security telemetry is stored and controlled. In this situation, event-time versus ingestion-time mismatch can hide or duplicate incidents in time-bounded queries.
D:Collection rules must be associated with each data source and include the desired event set. However, event-time versus ingestion-time mismatch can hide or duplicate incidents in time-bounded queries.
Question 88
A hybrid server sends events to Sentinel but some sensitive event records should not leave the region according to policy. What should the administrator change first to correct this specific issue?
- Inspect Azure Monitor Agent extension health, machine identity and secure endpoint connectivity.
- Map the Azure Monitor DCR destination region, retention and access scope to the approved governance requirements.
- Configure the Windows Security Events connector and Azure Monitor Agent data collection rules for that machine.
- Check the affected machines' DCR association and Windows Security event selection.
Explanation
Correct Answer
B:The workspace and data collection destination define where security telemetry is stored and controlled. For that reason, map the Azure Monitor DCR destination region, retention and access scope to the approved governance requirements.
Incorrect Answers
A:A healthy KQL rule cannot compensate for a broken collection agent or authentication channel. Here, the workspace and data collection destination define where security telemetry is stored and controlled.
C:Heartbeat connectivity does not mean the Windows Security event stream is selected for collection. However, the workspace and data collection destination define where security telemetry is stored and controlled.
D:Collection rules must be associated with each data source and include the desired event set. Here, the workspace and data collection destination define where security telemetry is stored and controlled.
Question 89
One Arc server reports periodic agent errors after a certificate rotation; Sentinel rules have not changed. Which configuration or recovery action best matches this evidence?
- Create a second Windows Security Events data collection rule without checking the certificate-related agent and machine-identity errors.
- Map the Azure Monitor DCR destination region, retention and access scope to the approved governance requirements.
- Inspect Azure Monitor Agent extension health, machine identity and secure endpoint connectivity.
- Restore the appropriate agent network connectivity and ingestion path before changing detection queries.
Explanation
Correct Answer
C:Inspect Azure Monitor Agent extension health, machine identity and secure endpoint connectivity. The underlying technical reason is that a healthy KQL rule cannot compensate for a broken collection agent or authentication channel.
Incorrect Answers
A:Adding a collection definition doesn't repair an agent that is failing after an identity/certificate change. Check the extension, machine registration and secure transport first; the agent must be able to authenticate and deliver events before a new rule can help.
B:The workspace and data collection destination define where security telemetry is stored and controlled. However, a healthy KQL rule cannot compensate for a broken collection agent or authentication channel.
D:Search logic cannot find source events that were never transmitted or indexed. In this situation, a healthy KQL rule cannot compensate for a broken collection agent or authentication channel.
Question 90
A company wants to detect PowerShell abuse but the DCR captures only Windows System and Application logs. Which Windows Server or Azure operation best addresses the reported fault?
- Check the affected machines' DCR association and Windows Security event selection.
- Restore the minimally required Windows Security event selection and validate an intentional test logon.
- Configure the Windows Security Events connector and Azure Monitor Agent data collection rules for that machine.
- Add the appropriate PowerShell operational/security logging sources and ingest the supported event channels.
Explanation
Correct Answer
D:Threat-detection coverage depends on the selected event channels rather than generic Windows uptime metrics. A suitable corrective action is to add the appropriate PowerShell operational/security logging sources and ingest the supported event channels.
Incorrect Answers
A:Collection rules must be associated with each data source and include the desired event set. However, threat-detection coverage depends on the selected event channels rather than generic Windows uptime metrics.
B:Excluding the signal at collection time prevents any downstream alert from evaluating it. Here, threat-detection coverage depends on the selected event channels rather than generic Windows uptime metrics.
C:Heartbeat connectivity does not mean the Windows Security event stream is selected for collection. In this situation, threat-detection coverage depends on the selected event channels rather than generic Windows uptime metrics.
Configuring Windows Server Hybrid Advanced Services (AZ-801) Practice Tests