You save $69.98
AZ-801 Premium Bundle
- Premium File 326 Questions & Answers
- Last Update: Nov 11, 2026
- Training Course 122 Lectures
- Study Guide 387 Pages
You save $69.98
Azure-hosted Windows Server workloads need endpoint threat alerts and vulnerability assessment beyond configuration-only review.
Which configuration change best addresses this specific requirement?
Enable the appropriate Microsoft Defender for Servers plan and verify deployment of its supported protective components. This addresses the stated situation: Azure-hosted Windows Server workloads need endpoint threat alerts and vulnerability assessment beyond configuration-only review. Defender for Servers provides server workload protection features that differ from posture-only inventory and depend on plan and agent configuration. Confirm the outcome by checking that the targeted VM shows healthy coverage and a representative alert or assessment becomes available in the security workflow. If the control is skipped, enabling a subscription label without confirming actual server onboarding can leave coverage gaps undetected.
Configure the appropriate Microsoft Sentinel data connector and collection path for Windows Server security events. This is more relevant to Microsoft Sentinel security telemetry, such as when security operations must correlate Windows Server security events from multiple sites with cloud identity alerts. Sentinel analytics relies on ingested telemetry, usually routed through Azure Monitor components and supported connectors. The appropriate action here is to enable the appropriate Microsoft Defender for Servers plan and verify deployment of its supported protective components.
Configure appropriate SmartScreen reputation checks and enforce the related security settings through scoped Group Policy. This is more relevant to SmartScreen and Group Policy controls, such as when users on an administrative jump host routinely open downloaded files from unknown websites. SmartScreen helps identify suspicious downloaded content while Group Policy centrally distributes supported client security settings. The appropriate action here is to enable the appropriate Microsoft Defender for Servers plan and verify deployment of its supported protective components.
Onboard supported servers to Microsoft Defender for Cloud and remediate assessed security recommendations by priority. This is more relevant to Microsoft Defender for Cloud posture findings, such as when hybrid Windows Servers have inconsistent hardening and central security needs risk-ranked recommendations. Defender for Cloud combines posture assessment and workload protection insights, including supported hybrid servers through Azure Arc. The appropriate action here is to enable the appropriate Microsoft Defender for Servers plan and verify deployment of its supported protective components.
A clustered file-server role must be moved away from a node scheduled for hardware maintenance.
Which technical principle best explains why the correct solution works?
Cluster roles have owners and placement constraints; coordinated moves differ from uncontrolled service shutdowns. This mechanism is relevant because a clustered file-server role must be moved away from a node scheduled for hardware maintenance. The administrator should use Failover Cluster Manager or supported PowerShell to drain or move the selected clustered workload to a healthy node. Validate the decision by confirming that the role comes online on the target owner and clients reconnect within the workload's agreed service objective.
Rolling upgrades preserve service during supported mixed-version transitions, but cluster functional-level changes have defined ordering constraints. This explains Cluster rolling operating-system upgrade, for example: A supported failover cluster must upgrade Windows Server without one large application outage. The decisive mechanism is that cluster roles have owners and placement constraints; coordinated moves differ from uncontrolled service shutdowns.
Cluster node recovery requires compatible software, communication and storage paths; simply restoring the machine name is insufficient. This explains Recover and rejoin a failed node, for example: A Windows Server cluster node has been rebuilt after disk failure and must be safely returned to membership. The decisive mechanism is that cluster roles have owners and placement constraints; coordinated moves differ from uncontrolled service shutdowns.
CAU coordinates node maintenance and workload movement to preserve service availability during supported cluster updates. This explains Cluster-Aware Updating maintenance, for example: A production Windows failover cluster needs monthly patches without stopping every hosted workload at once. The decisive mechanism is that cluster roles have owners and placement constraints; coordinated moves differ from uncontrolled service shutdowns.
Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised.
Which failure mode is most relevant if the required control is omitted?
A common or never-rotated local administrator password allows compromise of one host to spread to others. This is the direct risk of the described condition: Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised. Windows LAPS manages distinct rotating local administrator credentials and protects their recovery through supported directory permissions. The corrective approach is to configure Windows LAPS backup, rotation and authorized password retrieval for each managed Windows Server computer.
Assuming the feature is active without checking hardware and virtualization prerequisites can leave reusable credentials exposed. This is a risk associated with Credential Guard for reusable secrets, such as when privileged support staff sign in to Windows Server and attackers might attempt to dump reusable domain credentials from memory. For this case, the main exposure is that a common or never-rotated local administrator password allows compromise of one host to spread to others.
Enabling an untested restrictive policy can prevent service startup while failing to enforce it permits untrusted code execution. This is a risk associated with Application control allowlist, such as when a file server must run only signed approved administration utilities and vetted service binaries. For this case, the main exposure is that a common or never-rotated local administrator password allows compromise of one host to spread to others.
Publishing a baseline without applying or validating it allows insecure configuration drift to persist unnoticed. This is a risk associated with OSConfig baseline drift, such as when security policy requires a consistent Windows Server 2025 configuration despite manual changes by server operators. For this case, the main exposure is that a common or never-rotated local administrator password allows compromise of one host to spread to others.
Tier-zero administrator credentials must not be exposed through legacy NTLM authentication on member machines.
Which configuration change best addresses this specific requirement?
Evaluate and add eligible privileged accounts to the Protected Users security group after validating their authentication dependencies. This addresses the stated situation: Tier-zero administrator credentials must not be exposed through legacy NTLM authentication on member machines. Protected Users imposes authentication protections including restrictions on NTLM and credential caching that can affect unsupported legacy workflows. Confirm the outcome by checking that protected administrators authenticate with supported Kerberos paths and the required older authentication flows are appropriately blocked. If the control is skipped, adding incompatible service identities blindly can disrupt logons while omitting eligible privileged accounts leaves weaker credential handling.
Deploy Microsoft Entra Password Protection proxy and DC agents, configure global and custom banned passwords, and test enforcement. This is more relevant to Entra Password Protection for AD DS, such as when a hybrid AD organization finds that users can choose predictable passwords containing the company name. Password Protection DC agents evaluate password changes in AD DS against the synchronized banned-password policy; proxy services support policy distribution. The appropriate action here is to evaluate and add eligible privileged accounts to the Protected Users security group after validating their authentication dependencies.
Configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts. This is more relevant to RODC password replication policy, such as when a branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch. An RODC caches only permitted account credentials, reducing exposure if a physically less-secure branch controller is stolen. The appropriate action here is to evaluate and add eligible privileged accounts to the Protected Users security group after validating their authentication dependencies.
Design and enforce supported AD authentication policies and authentication policy silos for the privileged identities and eligible hosts. This is more relevant to Authentication policy silos, such as when tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. Authentication policy silos restrict where qualifying Kerberos-authenticated privileged identities can authenticate, reducing credential exposure. The appropriate action here is to evaluate and add eligible privileged accounts to the Protected Users security group after validating their authentication dependencies.
Azure IaaS Windows VMs need daily protected recovery points retained independently of their production resource group.
Which supported approach best meets the stated operational need?
Create an appropriate Recovery Services vault backup policy and enable Azure VM backup for the intended VM scope. This addresses the stated situation: Azure IaaS Windows VMs need daily protected recovery points retained independently of their production resource group. Azure Backup coordinates policy-based recovery points in a Recovery Services vault independently of ordinary VM restart operations. Confirm the outcome by checking that the target VM reports successful protected backup jobs and a test restore point is available under the intended retention policy. If the control is skipped, a VM without verified backups can lose recoverable application state when its disks or resource group are damaged.
Restore the VM with the required supported encryption dependencies, key-vault access and recovery procedure. This is more relevant to Azure encrypted VM restore, such as when a protected Azure Windows VM uses disk encryption and must be recovered after storage corruption. Encrypted VM recovery depends on both recoverable disk data and access to the appropriate cryptographic keys or protectors. The appropriate action here is to create an appropriate Recovery Services vault backup policy and enable Azure VM backup for the intended VM scope.
Deploy a supported Microsoft Azure Backup Server configuration and register it for appropriate off-site protection. This is more relevant to Azure Backup Server for workload protection, such as when an on-premises application server requires centrally scheduled backups with off-site Azure retention. Azure Backup Server coordinates supported workload backups and can protect selected recovery data in Azure while local recovery is available. The appropriate action here is to create an appropriate Recovery Services vault backup policy and enable Azure VM backup for the intended VM scope.
Use a suitable Azure Backup file recovery workflow from a validated restore point and restore only the required content. This is more relevant to Azure Backup file and folder restore, such as when a finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM. Azure Backup file-level recovery allows targeted restoration when the backed-up recovery point includes the needed files. The appropriate action here is to create an appropriate Recovery Services vault backup policy and enable Azure VM backup for the intended VM scope.
An AD restructuring project finds that cross-forest applications cannot locate domain controllers despite a configured trust.
What risk should be highlighted in the change assessment?
Moving directory identities before validating trust and DNS paths can produce prolonged access failures. This is the direct risk of the described condition: An AD restructuring project finds that cross-forest applications cannot locate domain controllers despite a configured trust. Cross-forest identities rely on name resolution and trust paths to authenticate resources during coexistence. The corrective approach is to validate DNS resolution, forest trust scope and authentication routing before migrating AD objects.
Raising functional levels before clearing incompatible controllers can block operations or create rollback limits. This is a risk associated with AD forest functional level readiness, such as when a Windows Server 2025 domain controller has been introduced but older DC versions remain and administrators want a higher forest functional level. For this case, the main exposure is that moving directory identities before validating trust and DNS paths can produce prolonged access failures.
Recreating users without preserving required access mappings can orphan permissions and interrupt sign-ins. This is a risk associated with ADMT cross-forest object migration, such as when two AD forests are consolidating but users must retain access to existing departmental resources during transition. For this case, the main exposure is that moving directory identities before validating trust and DNS paths can produce prolonged access failures.
Copying GPOs without translating source identities may silently drop or misapply security policies. This is a risk associated with Group Policy migration cross-forest, such as when a user migration into a new AD forest requires the same approved workstation policy without retaining obsolete security principals. For this case, the main exposure is that moving directory identities before validating trust and DNS paths can produce prolonged access failures.
A finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM.
Which acceptance result most directly demonstrates a working configuration?
The specified folder is recovered with correct content and permissions while unrelated current application files stay intact. This specifically verifies the case: A finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM. Azure Backup file-level recovery allows targeted restoration when the backed-up recovery point includes the needed files. The matching action is to use a suitable Azure Backup file recovery workflow from a validated restore point and restore only the required content.
A controlled restored VM boots and mounts its intended encrypted volumes under approved identity access. This would validate Azure encrypted VM restore, as in this different situation: A protected Azure Windows VM uses disk encryption and must be recovered after storage corruption. It is not the most direct evidence for the case: A finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM. Here, successful verification means that the specified folder is recovered with correct content and permissions while unrelated current application files stay intact.
A supported workload backup completes and an authorized restore test verifies application-consistent data under the retention policy. This would validate Azure Backup Server for workload protection, as in this different situation: An on-premises application server requires centrally scheduled backups with off-site Azure retention. It is not the most direct evidence for the case: A finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM. Here, successful verification means that the specified folder is recovered with correct content and permissions while unrelated current application files stay intact.
The target VM reports successful protected backup jobs and a test restore point is available under the intended retention policy. This would validate Recovery Services vault VM backup, as in this different situation: Azure IaaS Windows VMs need daily protected recovery points retained independently of their production resource group. It is not the most direct evidence for the case: A finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM. Here, successful verification means that the specified folder is recovered with correct content and permissions while unrelated current application files stay intact.
Users still access an application through NTLM, and security wants a safe migration toward Kerberos.
What is the most direct consequence of leaving this problem unresolved?
Disabling NTLM everywhere without inventorying dependencies can interrupt legacy services and create an unplanned outage. This is the direct risk of the described condition: Users still access an application through NTLM, and security wants a safe migration toward Kerberos. NTLM audit events reveal remaining consumers; staged restrictions avoid assuming all applications already support Kerberos. The corrective approach is to enable relevant NTLM auditing, identify dependencies, remediate application configuration, and enforce restrictions in phases.
Installing generic host monitoring without identity-specific telemetry can leave credential and directory attack behaviors undetected. This is a risk associated with Defender for Identity directory sensors, such as when security analysts need to detect suspicious AD reconnaissance and lateral-movement activity around domain controllers. For this case, the main exposure is that disabling NTLM everywhere without inventorying dependencies can interrupt legacy services and create an unplanned outage.
Using group membership alone without restricting privileged logon destinations leaves the account exposed on untrusted hosts. This is a risk associated with Authentication policy silos, such as when tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. For this case, the main exposure is that disabling NTLM everywhere without inventorying dependencies can interrupt legacy services and create an unplanned outage.
Treating domain controllers as generic member servers exposes the central identity infrastructure to avoidable attack paths. This is a risk associated with Domain controller hardening, such as when a new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions. For this case, the main exposure is that disabling NTLM everywhere without inventorying dependencies can interrupt legacy services and create an unplanned outage.
Recovery coordinators need one runbook that groups several replicated VMs and includes manual approval checkpoints.
Which technical principle best explains why the correct solution works?
ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions. This mechanism is relevant because recovery coordinators need one runbook that groups several replicated VMs and includes manual approval checkpoints. The administrator should build and test an Azure Site Recovery recovery plan with dependency-appropriate groups and supported automation or manual steps. Validate the decision by confirming that a controlled drill starts tiers in the intended order and records successful steps and required operator approvals.
Azure Site Recovery orchestrates supported machine replication and recovery between target sites or regions for business continuity. This explains Azure Site Recovery region replication, for example: A business requires a protected Azure Windows VM to survive loss of its primary Azure region. The decisive mechanism is that ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions.
ASR network mappings associate source environments with intended recovery networks; replicated disks alone do not restore application connectivity. This explains Azure Site Recovery network mapping, for example: A replicated application VM starts during a recovery drill but its virtual network cannot reach dependent services. The decisive mechanism is that ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions.
ASR replication policy and recovery-point configuration affect the available recovery points and how far data might lag the source. This explains ASR replication policy and recovery points, for example: A recovery auditor requires a measurable RPO and enough recovery history for a Windows application VM. The decisive mechanism is that ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions.
An organization must migrate user and group accounts into a new AD DS forest without manually recreating every identity.
What is the most direct consequence of leaving this problem unresolved?
Recreating users without preserving required access mappings can orphan permissions and interrupt sign-ins. This is the direct risk of the described condition: An organization must migrate user and group accounts into a new AD DS forest without manually recreating every identity. Cross-forest AD migration must address SID/history, trusts, name conflicts and target permissions rather than only copying user names. The corrective approach is to plan a supported ADMT-based cross-forest user/group migration with trusts, identity mapping and access-continuity tests.
Moving directory identities before validating trust and DNS paths can produce prolonged access failures. This is a risk associated with Forest restructure trust and DNS, such as when two companies merging must establish identity coexistence before moving accounts across forests. For this case, the main exposure is that recreating users without preserving required access mappings can orphan permissions and interrupt sign-ins.
Raising functional levels before clearing incompatible controllers can block operations or create rollback limits. This is a risk associated with AD forest functional level readiness, such as when a Windows Server 2025 domain controller has been introduced but older DC versions remain and administrators want a higher forest functional level. For this case, the main exposure is that recreating users without preserving required access mappings can orphan permissions and interrupt sign-ins.
Copying GPOs without translating source identities may silently drop or misapply security policies. This is a risk associated with Group Policy migration cross-forest, such as when a user migration into a new AD forest requires the same approved workstation policy without retaining obsolete security principals. For this case, the main exposure is that recreating users without preserving required access mappings can orphan permissions and interrupt sign-ins.
A Windows Server file host repeatedly approaches free-space alerts without reliable forecasting.
Which finding should be recorded as evidence of success?
Forecasted disk consumption aligns with observed trends and triggers an actionable capacity response before thresholds are exceeded. This specifically verifies the case: A Windows Server file host repeatedly approaches free-space alerts without reliable forecasting. System Insights uses local machine data to generate forecasts for resource trends that inform proactive capacity planning. The matching action is to use supported Windows Server System Insights forecasting capabilities and validate its predictive data quality.
The selected Azure VM shows expected CPU, disk and guest-performance measurements over the diagnostic interval. This would validate VM Insights performance monitoring, as in this different situation: Azure IaaS Windows VMs need consistent memory, disk and process-performance dashboards across a subscription. It is not the most direct evidence for the case: A Windows Server file host repeatedly approaches free-space alerts without reliable forecasting. Here, successful verification means that forecasted disk consumption aligns with observed trends and triggers an actionable capacity response before thresholds are exceeded.
A known test event appears in the intended workspace table from a correctly associated Windows Server. This would validate Azure Monitor data collection rules, as in this different situation: Azure Arc-enabled Windows Servers are connected to Azure but their security and performance events are not arriving in Log Analytics. It is not the most direct evidence for the case: A Windows Server file host repeatedly approaches free-space alerts without reliable forecasting. Here, successful verification means that forecasted disk consumption aligns with observed trends and triggers an actionable capacity response before thresholds are exceeded.
A selected Windows event is queryable centrally with accurate source identity and timestamp within retention requirements. This would validate Event log forwarding and retention, as in this different situation: Investigators cannot reconstruct a server failure because system logs were overwritten before analysis. It is not the most direct evidence for the case: A Windows Server file host repeatedly approaches free-space alerts without reliable forecasting. Here, successful verification means that forecasted disk consumption aligns with observed trends and triggers an actionable capacity response before thresholds are exceeded.
Please check your mailbox for a message from support@examlabs.com and follow the directions.