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
Operators currently restart all cluster nodes together during routine security maintenance.
Which configuration change best addresses this specific requirement?
Configure Cluster-Aware Updating or a supported rolling patch workflow that drains and patches cluster nodes sequentially. This addresses the stated situation: Operators currently restart all cluster nodes together during routine security maintenance. CAU coordinates node maintenance and workload movement to preserve service availability during supported cluster updates. Confirm the outcome by checking that each patched node returns healthy before the next is drained and application resources remain available throughout the sequence. If the control is skipped, simultaneous node restarts can exhaust cluster capacity and cause preventable application downtime.
Use Failover Cluster Manager or supported PowerShell to drain or move the selected clustered workload to a healthy node. This is more relevant to Cluster workload and role movement, such as when a clustered file-server role must be moved away from a node scheduled for hardware maintenance. Cluster roles have owners and placement constraints; coordinated moves differ from uncontrolled service shutdowns. The appropriate action here is to configure Cluster-Aware Updating or a supported rolling patch workflow that drains and patches cluster nodes sequentially.
Follow the supported cluster operating-system rolling-upgrade sequence with workload drains, node upgrades and cluster functional-level updates. This is more relevant to Cluster rolling operating-system upgrade, such as when a supported failover cluster must upgrade Windows Server without one large application outage. Rolling upgrades preserve service during supported mixed-version transitions, but cluster functional-level changes have defined ordering constraints. The appropriate action here is to configure Cluster-Aware Updating or a supported rolling patch workflow that drains and patches cluster nodes sequentially.
Repair and validate the node, confirm cluster configuration compatibility and safely rejoin it before failing back services. This is more relevant to Recover and rejoin a failed node, such as when a Windows Server cluster node has been rebuilt after disk failure and must be safely returned to membership. Cluster node recovery requires compatible software, communication and storage paths; simply restoring the machine name is insufficient. The appropriate action here is to configure Cluster-Aware Updating or a supported rolling patch workflow that drains and patches cluster nodes sequentially.
A virtualization cluster is being refreshed and planners need to preserve guest availability during host migration.
Which failure mode is most relevant if the required control is omitted?
Assuming live migration works across all CPU and Windows version combinations can cause service interruption. This is the direct risk of the described condition: A virtualization cluster is being refreshed and planners need to preserve guest availability during host migration. Hyper-V migration methods have distinct availability, storage and compatibility requirements; an unsupported live move may fail. The corrective approach is to choose supported Hyper-V live migration, storage migration or export/import according to CPU, version and storage compatibility.
Moving only the printer name without driver and port configuration can leave end-user printing unavailable. This is a risk associated with Print server migration, such as when an office has hundreds of printer queues tied to a Windows Server scheduled for decommissioning. For this case, the main exposure is that assuming live migration works across all CPU and Windows version combinations can cause service interruption.
Replacing session hosts without checking brokers and licensing can deny users remote application access. This is a risk associated with Remote Desktop Services session host migration, such as when a legacy RDS deployment must replace its session hosts while retaining user access and application behavior. For this case, the main exposure is that assuming live migration works across all CPU and Windows version combinations can cause service interruption.
Turning on a new server with overlapping scopes before disabling the old one can issue conflicting leases. This is a risk associated with DHCP migration with leases and options, such as when a new Windows Server will replace a legacy DHCP server serving multiple network scopes. For this case, the main exposure is that assuming live migration works across all CPU and Windows version combinations can cause service interruption.
A finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM.
What is the most directly justified remediation?
Use a suitable Azure Backup file recovery workflow from a validated restore point and restore only the required content. This addresses the stated situation: 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. Confirm the outcome by checking that the specified folder is recovered with correct content and permissions while unrelated current application files stay intact. If the control is skipped, restoring an entire VM unnecessarily can overwrite legitimate changes made after the backup point.
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 use a suitable Azure Backup file recovery workflow from a validated restore point and restore only the required content.
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 use a suitable Azure Backup file recovery workflow from a validated restore point and restore only the required content.
Create an appropriate Recovery Services vault backup policy and enable Azure VM backup for the intended VM scope. This is more relevant to Recovery Services vault VM backup, such as when 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. The appropriate action here is to use a suitable Azure Backup file recovery workflow from a validated restore point and restore only the required content.
A branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch.
Which implementation step should the Windows Server administrator prioritize?
Configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts. This addresses the stated situation: 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. Confirm the outcome by checking that approved branch accounts can log on under the intended network conditions, while denied privileged credentials are not cached. If the control is skipped, overbroad password caching on an RODC can expose privileged credentials when the branch server is compromised.
Evaluate and add eligible privileged accounts to the Protected Users security group after validating their authentication dependencies. This is more relevant to Protected Users account group, such as when 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. The appropriate action here is to configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts.
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 configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts.
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 configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts.
A standalone Hyper-V host needs asynchronous VM recovery at a second on-premises site.
Which acceptance result most directly demonstrates a working configuration?
Replication state is healthy and a scheduled test failover boots an isolated replica without impacting production. This specifically verifies the case: A standalone Hyper-V host needs asynchronous VM recovery at a second on-premises site. Hyper-V Replica asynchronously copies supported VM changes to a recovery host and requires compatible permissions and connectivity. The matching action is to enable and configure Hyper-V Replica on source and replica hosts, choose transport authentication and initialize replication.
The rehearsal VM starts in an isolated network without affecting production, or the planned failover completes with expected replication state. This would validate Hyper-V Replica test versus planned failover, as in this different situation: A team wants to verify that a Hyper-V Replica VM can boot without disrupting the running production VM. It is not the most direct evidence for the case: A standalone Hyper-V host needs asynchronous VM recovery at a second on-premises site. Here, successful verification means that replication state is healthy and a scheduled test failover boots an isolated replica without impacting production.
Both configured relationships report healthy states and a controlled downstream test recovers the intended VM version. This would validate Hyper-V extended replica and health, as in this different situation: A high-priority VM already replicates to a secondary host but needs a third off-site recovery copy. It is not the most direct evidence for the case: A standalone Hyper-V host needs asynchronous VM recovery at a second on-premises site. Here, successful verification means that replication state is healthy and a scheduled test failover boots an isolated replica without impacting production.
A controlled drill starts tiers in the intended order and records successful steps and required operator approvals. This would validate ASR recovery plan orchestration, as in this different situation: A three-tier service must recover database, application and web tiers in a dependency-aware order. It is not the most direct evidence for the case: A standalone Hyper-V host needs asynchronous VM recovery at a second on-premises site. Here, successful verification means that replication state is healthy and a scheduled test failover boots an isolated replica without impacting production.
A new Windows Server will replace a legacy DHCP server serving multiple network scopes.
What technical distinction explains the intended control?
DHCP continuity relies on valid scopes, reservations, options and directory authorization where required. This mechanism is relevant because a new Windows Server will replace a legacy DHCP server serving multiple network scopes. The administrator should export and import DHCP configuration through a supported migration method and authorize the replacement DHCP service. Validate the decision by confirming that test clients receive addresses and expected gateway/DNS options from the intended new server without conflicting leases.
Windows Server upgrade paths and application dependencies constrain which versions can be upgraded directly; side-by-side replacement isolates risk. This explains Choose in-place upgrade versus side-by-side migration, for example: A very old Windows Server installation hosts an application that cannot tolerate an unsupported direct OS upgrade. The decisive mechanism is that dHCP continuity relies on valid scopes, reservations, options and directory authorization where required.
Print workloads depend on queue definitions, printer drivers, ports and sharing configuration beyond spool data. This explains Print server migration, for example: An office has hundreds of printer queues tied to a Windows Server scheduled for decommissioning. The decisive mechanism is that dHCP continuity relies on valid scopes, reservations, options and directory authorization where required.
IIS application function depends on web-server configuration and runtime identity in addition to static website files. This explains Migrate IIS site configuration, for example: An older IIS server runs several applications with custom bindings, certificates and authentication settings. The decisive mechanism is that dHCP continuity relies on valid scopes, reservations, options and directory authorization where required.
Two Windows Server nodes will host a SQL workload and the architect needs supportable shared failover clustering.
Which explanation most directly supports the appropriate decision?
Validation evaluates network, system and storage prerequisites; clustering nodes without testing can conceal unsupported configurations. This mechanism is relevant because two Windows Server nodes will host a SQL workload and the architect needs supportable shared failover clustering. The administrator should run supported Failover Cluster Validation tests, remediate blocking results and then create the Windows Server failover cluster. Validate the decision by confirming that the validation report passes required checks and the new cluster shows healthy membership and functional workload placement.
A Cloud Witness uses an Azure storage blob for cluster quorum arbitration without requiring a full witness server. This explains Azure cloud witness placement, for example: A two-site cluster has no dependable independent third datacenter for a file-share witness. The decisive mechanism is that validation evaluates network, system and storage prerequisites; clustering nodes without testing can conceal unsupported configurations.
Workgroup clusters can operate outside AD DS when their specific authentication, name and workload limitations are addressed. This explains Workgroup cluster identity design, for example: A small isolated application cluster must be built without an Active Directory domain membership dependency. The decisive mechanism is that validation evaluates network, system and storage prerequisites; clustering nodes without testing can conceal unsupported configurations.
A quorum witness contributes votes or arbitration in supported topologies and reduces split-brain or unavailability risks. This explains Cluster quorum and witness planning, for example: A two-node Windows failover cluster needs to survive the loss of one node without unnecessary loss of quorum. The decisive mechanism is that validation evaluates network, system and storage prerequisites; clustering nodes without testing can conceal unsupported configurations.
A cluster build team wants to convert eligible local drives into clustered Storage Spaces Direct capacity.
Which finding should be recorded as evidence of success?
The storage pool shows healthy eligible disks and resilient volumes remain available under a planned disk or node failure. This specifically verifies the case: A cluster build team wants to convert eligible local drives into clustered Storage Spaces Direct capacity. S2D pools supported local disks across clustered hosts and exposes resilient virtual disks; disk and network prerequisites are essential. The matching action is to validate supported S2D hardware and enable Storage Spaces Direct on eligible cluster nodes before creating resilient volumes.
Repair jobs complete and virtual disks return to healthy redundancy without storage exhaustion. This would validate Storage Spaces Direct repair and capacity reserve, as in this different situation: A node in a Storage Spaces Direct cluster fails and the remaining hosts must rebuild missing data copies. It is not the most direct evidence for the case: A cluster build team wants to convert eligible local drives into clustered Storage Spaces Direct capacity. Here, successful verification means that the storage pool shows healthy eligible disks and resilient volumes remain available under a planned disk or node failure.
The replacement joins the cluster, the pool redistributes data and all virtual disks show healthy resiliency. This would validate Upgrade an S2D storage node safely, as in this different situation: An S2D cluster must replace an aging node without sacrificing data integrity during the transition. It is not the most direct evidence for the case: A cluster build team wants to convert eligible local drives into clustered Storage Spaces Direct capacity. Here, successful verification means that the storage pool shows healthy eligible disks and resilient volumes remain available under a planned disk or node failure.
Adapter and SMB performance counters show expected RDMA use while storage latency and dropped traffic return to baseline. This would validate RDMA traffic health for Storage Spaces Direct, as in this different situation: An S2D cluster suffers intermittent storage pauses while CPU utilization rises during large east-west transfers. It is not the most direct evidence for the case: A cluster build team wants to convert eligible local drives into clustered Storage Spaces Direct capacity. Here, successful verification means that the storage pool shows healthy eligible disks and resilient volumes remain available under a planned disk or node failure.
A new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions.
Which explanation most directly supports the appropriate decision?
Domain controllers hold directory authentication and replication responsibilities, so tier-zero hardening reduces the blast radius of compromise. This mechanism is relevant because a new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions. The administrator should apply a domain-controller security baseline, restrict privileged access paths, remove unnecessary services, and validate changes. Validate the decision by confirming that baseline review and connectivity tests show only required directory services and approved administrative endpoints remain accessible.
Authentication policy silos restrict where qualifying Kerberos-authenticated privileged identities can authenticate, reducing credential exposure. This explains Authentication policy silos, for example: Tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. The decisive mechanism is that domain controllers hold directory authentication and replication responsibilities, so tier-zero hardening reduces the blast radius of compromise.
NTLM audit events reveal remaining consumers; staged restrictions avoid assuming all applications already support Kerberos. This explains NTLM auditing and phased restriction, for example: A domain modernization team must locate legacy NTLM consumers before disabling weaker authentication. The decisive mechanism is that domain controllers hold directory authentication and replication responsibilities, so tier-zero hardening reduces the blast radius of compromise.
An RODC caches only permitted account credentials, reducing exposure if a physically less-secure branch controller is stolen. This explains RODC password replication policy, for example: A branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch. The decisive mechanism is that domain controllers hold directory authentication and replication responsibilities, so tier-zero hardening reduces the blast radius of compromise.
A development team plans to containerize a compatible Windows web workload instead of maintaining a full IIS VM.
Which technical principle best explains why the correct solution works?
Windows containers bundle compatible application dependencies while still depending on supported host/image versions and persistent-data design. This mechanism is relevant because a development team plans to containerize a compatible Windows web workload instead of maintaining a full IIS VM. The administrator should evaluate supported Windows container images and package the IIS application with its required runtime and configuration. Validate the decision by confirming that the container image launches the IIS workload under the target orchestrator with validated storage and network configuration.
Azure App Service provides managed web hosting and optional deployment slots, but application configuration and state require migration. This explains Migrate IIS application to Azure App Service, for example: A stateless ASP.NET application on IIS needs staging deployment slots and managed web hosting. The decisive mechanism is that Windows containers bundle compatible application dependencies while still depending on supported host/image versions and persistent-data design.
App Service hosts compatible web applications as managed platform services; Windows-specific dependencies may require code changes. This explains IIS workload assessment for App Service, for example: An IIS web app is a possible candidate for Azure App Service but uses unsupported local Windows components. The decisive mechanism is that Windows containers bundle compatible application dependencies while still depending on supported host/image versions and persistent-data design.
Azure Files is a managed file service with its own SMB authentication, storage-account connectivity and ACL requirements. This explains Azure Files destination migration, for example: An on-premises Windows file share must move to Azure Files with SMB access and retained permissions. The decisive mechanism is that Windows containers bundle compatible application dependencies while still depending on supported host/image versions and persistent-data design.
A protected VM has replication enabled but no documented retention and consistency requirements.
Why is the proposed approach appropriate to this Windows Server problem?
ASR replication policy and recovery-point configuration affect the available recovery points and how far data might lag the source. This mechanism is relevant because a protected VM has replication enabled but no documented retention and consistency requirements. The administrator should set Azure Site Recovery policy settings for compatible replication and recovery-point retention and monitor resulting RPO. Validate the decision by confirming that replication monitoring and a test failover confirm a recovery point meets the documented freshness and application consistency objective.
ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions. This explains ASR recovery plan orchestration, for example: A three-tier service must recover database, application and web tiers in a dependency-aware order. The decisive mechanism is that ASR replication policy and recovery-point configuration affect the available recovery points and how far data might lag the source.
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 replication policy and recovery-point configuration affect the available recovery points and how far data might lag the source.
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 replication policy and recovery-point configuration affect the available recovery points and how far data might lag the source.
Please check your mailbox for a message from support@examlabs.com and follow the directions.