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
A node in a Storage Spaces Direct cluster fails and the remaining hosts must rebuild missing data copies.
Which acceptance result most directly demonstrates a working configuration?
Repair jobs complete and virtual disks return to healthy redundancy without storage exhaustion. This specifically verifies the case: A node in a Storage Spaces Direct cluster fails and the remaining hosts must rebuild missing data copies. S2D resiliency depends on free capacity and healthy fault domains for data repair after host or disk failure. The matching action is to monitor virtual disk health and repair jobs, preserve sufficient free pool capacity and restore the failed storage fault domain.
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 node in a Storage Spaces Direct cluster fails and the remaining hosts must rebuild missing data copies. Here, successful verification means that repair jobs complete and virtual disks return to healthy redundancy without storage exhaustion.
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 node in a Storage Spaces Direct cluster fails and the remaining hosts must rebuild missing data copies. Here, successful verification means that repair jobs complete and virtual disks return to healthy redundancy without storage exhaustion.
The storage pool shows healthy eligible disks and resilient volumes remain available under a planned disk or node failure. This would validate Storage Spaces Direct pool enablement, as in this different situation: Four qualified Windows Servers have local data disks and need resilient shared storage without a traditional SAN. It is not the most direct evidence for the case: A node in a Storage Spaces Direct cluster fails and the remaining hosts must rebuild missing data copies. Here, successful verification means that repair jobs complete and virtual disks return to healthy redundancy without storage exhaustion.
A Windows Server becomes unbootable immediately after a storage-driver change and must be recovered safely.
Which technical principle best explains why the correct solution works?
Windows startup depends on boot configuration, system partition access and compatible storage drivers; a running hypervisor does not imply a bootable guest. This mechanism is relevant because a Windows Server becomes unbootable immediately after a storage-driver change and must be recovered safely. The administrator should use supported Windows recovery environment diagnostics, boot repair or targeted rollback for the verified boot-failure cause. Validate the decision by confirming that the recovered guest reaches normal sign-in and the original application starts without unrelated data rollback.
Arc extension management depends on the connected agent, permitted identities and reachable management services. This explains Arc agent and extension troubleshooting, for example: An Azure Arc-enabled Windows Server reports extension provisioning failure despite healthy local network services. The decisive mechanism is that Windows startup depends on boot configuration, system partition access and compatible storage drivers; a running hypervisor does not imply a bootable guest.
Kerberos authentication and distributed logs depend on reasonably synchronized clocks; inconsistent time can cause ticket validation failures. This explains Windows Time synchronization failures, for example: Kerberos logons fail intermittently because a domain member's clock differs significantly from its domain controller. The decisive mechanism is that Windows startup depends on boot configuration, system partition access and compatible storage drivers; a running hypervisor does not imply a bootable guest.
Windows servicing requires healthy component metadata and a functional update source; retries alone do not fix corruption. This explains Windows Update servicing failures, for example: Security patches fail repeatedly on Windows Server even though clients can reach their configured update endpoint. The decisive mechanism is that Windows startup depends on boot configuration, system partition access and compatible storage drivers; a running hypervisor does not imply a bootable guest.
A third-party accounting executable must be hardened against memory-corruption exploits without blocking its approved workflow.
What would provide the strongest verification of the intended solution?
The protected executable launches and passes its critical business tests while the configured mitigations appear in effective policy. This specifically verifies the case: A third-party accounting executable must be hardened against memory-corruption exploits without blocking its approved workflow. Exploit Protection applies process-level mitigations such as DEP and CFG; untested settings can interfere with legacy application behavior. The matching action is to pilot Windows Exploit Protection mitigations for the executable, verify compatibility, and deploy the tested policy by management tools.
System information reports Credential Guard running and a supported validation confirms the protected logon scenario remains functional. This would validate Credential Guard for reusable secrets, as in this different situation: Privileged support staff sign in to Windows Server and attackers might attempt to dump reusable domain credentials from memory. It is not the most direct evidence for the case: A third-party accounting executable must be hardened against memory-corruption exploits without blocking its approved workflow. Here, successful verification means that the protected executable launches and passes its critical business tests while the configured mitigations appear in effective policy.
The server rotates its local password, authorized recovery succeeds and an unrelated operator cannot retrieve the secret. This would validate Windows LAPS local administrator passwords, as in this different situation: Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised. It is not the most direct evidence for the case: A third-party accounting executable must be hardened against memory-corruption exploits without blocking its approved workflow. Here, successful verification means that the protected executable launches and passes its critical business tests while the configured mitigations appear in effective policy.
An allowed signed utility runs, an unapproved binary is denied, and code-integrity logs explain the decisions. This would validate Application control allowlist, as in this different situation: A file server must run only signed approved administration utilities and vetted service binaries. It is not the most direct evidence for the case: A third-party accounting executable must be hardened against memory-corruption exploits without blocking its approved workflow. Here, successful verification means that the protected executable launches and passes its critical business tests while the configured mitigations appear in effective policy.
A file server must run only signed approved administration utilities and vetted service binaries.
Which test result would best confirm the requirement has been met?
An allowed signed utility runs, an unapproved binary is denied, and code-integrity logs explain the decisions. This specifically verifies the case: A file server must run only signed approved administration utilities and vetted service binaries. WDAC enforces code-integrity policy during loading or execution, and audit mode helps discover required applications before enforcement. The matching action is to deploy a staged Windows Defender Application Control policy that permits approved code and blocks untrusted executables.
The protected executable launches and passes its critical business tests while the configured mitigations appear in effective policy. This would validate Exploit Protection mitigation policy, as in this different situation: A third-party accounting executable must be hardened against memory-corruption exploits without blocking its approved workflow. It is not the most direct evidence for the case: A file server must run only signed approved administration utilities and vetted service binaries. Here, successful verification means that an allowed signed utility runs, an unapproved binary is denied, and code-integrity logs explain the decisions.
The server rotates its local password, authorized recovery succeeds and an unrelated operator cannot retrieve the secret. This would validate Windows LAPS local administrator passwords, as in this different situation: Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised. It is not the most direct evidence for the case: A file server must run only signed approved administration utilities and vetted service binaries. Here, successful verification means that an allowed signed utility runs, an unapproved binary is denied, and code-integrity logs explain the decisions.
System information reports Credential Guard running and a supported validation confirms the protected logon scenario remains functional. This would validate Credential Guard for reusable secrets, as in this different situation: Privileged support staff sign in to Windows Server and attackers might attempt to dump reusable domain credentials from memory. It is not the most direct evidence for the case: A file server must run only signed approved administration utilities and vetted service binaries. Here, successful verification means that an allowed signed utility runs, an unapproved binary is denied, and code-integrity logs explain the decisions.
A new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions.
What is the most appropriate next administrative action?
Apply a domain-controller security baseline, restrict privileged access paths, remove unnecessary services, and validate changes. This addresses the stated situation: A new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions. Domain controllers hold directory authentication and replication responsibilities, so tier-zero hardening reduces the blast radius of compromise. Confirm the outcome by checking that baseline review and connectivity tests show only required directory services and approved administrative endpoints remain accessible. If the control is skipped, treating domain controllers as generic member servers exposes the central identity infrastructure to avoidable attack paths.
Enable relevant NTLM auditing, identify dependencies, remediate application configuration, and enforce restrictions in phases. This is more relevant to NTLM auditing and phased restriction, such as when a domain modernization team must locate legacy NTLM consumers before disabling weaker authentication. NTLM audit events reveal remaining consumers; staged restrictions avoid assuming all applications already support Kerberos. The appropriate action here is to apply a domain-controller security baseline, restrict privileged access paths, remove unnecessary services, and validate changes.
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 apply a domain-controller security baseline, restrict privileged access paths, remove unnecessary services, and validate changes.
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 apply a domain-controller security baseline, restrict privileged access paths, remove unnecessary services, and validate changes.
Two companies merging must establish identity coexistence before moving accounts across forests.
Which implementation step should the Windows Server administrator prioritize?
Validate DNS resolution, forest trust scope and authentication routing before migrating AD objects. This addresses the stated situation: Two companies merging must establish identity coexistence before moving accounts across forests. Cross-forest identities rely on name resolution and trust paths to authenticate resources during coexistence. Confirm the outcome by checking that test users can resolve partner domains and authenticate to explicitly authorized resources across the intended trust boundary. If the control is skipped, moving directory identities before validating trust and DNS paths can produce prolonged access failures.
Plan a supported ADMT-based cross-forest user/group migration with trusts, identity mapping and access-continuity tests. This is more relevant to ADMT cross-forest object migration, such as when two AD forests are consolidating but users must retain access to existing departmental resources during transition. Cross-forest AD migration must address SID/history, trusts, name conflicts and target permissions rather than only copying user names. The appropriate action here is to validate DNS resolution, forest trust scope and authentication routing before migrating AD objects.
Inventory domain controller versions, replication health and feature requirements before a supported functional-level increase. This is more relevant to 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. AD forest or domain functional level changes require compatible controller versions and healthy directory replication. The appropriate action here is to validate DNS resolution, forest trust scope and authentication routing before migrating AD objects.
Use supported Group Policy migration tables and target-domain security-principal mappings, then validate resulting policy application. This is more relevant to 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. GPO settings can contain domain-specific references that must be translated when moved between independent forests. The appropriate action here is to validate DNS resolution, forest trust scope and authentication routing before migrating AD objects.
A campus cluster must tolerate a whole-building outage without losing data consistency.
Which supported approach best meets the stated operational need?
Assign supported S2D site or fault-domain awareness and choose storage resiliency suited to the campus topology. This addresses the stated situation: A campus cluster must tolerate a whole-building outage without losing data consistency. Storage Spaces Direct uses fault-domain and resiliency settings to decide data placement and survivability across failures. Confirm the outcome by checking that a supported fault-domain validation and controlled site-loss test show retained storage accessibility and correct placement. If the control is skipped, ignoring physical failure domains can place redundant copies together and undermine site resilience.
Use supported Network ATC intent policies to deploy consistent management, compute and storage network settings. This is more relevant to Cluster network intent with Network ATC, such as when a new Azure Stack HCI-style Windows Server cluster has inconsistent adapter configuration for storage and management. Network ATC expresses host networking intent and applies consistent configuration across eligible cluster nodes. The appropriate action here is to assign supported S2D site or fault-domain awareness and choose storage resiliency suited to the campus topology.
Design a supported stretched cluster with storage replication or mirrored storage, suitable site networks and tested failover rules. This is more relevant to Stretch cluster across facilities, such as when an application must fail over between two physically separate datacenters while minimizing data loss. A stretched failover cluster spans fault domains, but application continuity depends on storage consistency, quorum and supported connectivity. The appropriate action here is to assign supported S2D site or fault-domain awareness and choose storage resiliency suited to the campus topology.
Configure an Azure Cloud Witness using supported storage-account access, connectivity and cluster settings. This is more relevant to Azure cloud witness placement, such as when a two-site cluster has no dependable independent third datacenter for a file-share witness. A Cloud Witness uses an Azure storage blob for cluster quorum arbitration without requiring a full witness server. The appropriate action here is to assign supported S2D site or fault-domain awareness and choose storage resiliency suited to the campus topology.
A physical Windows Server must protect its system volume while supporting disaster recovery after motherboard replacement.
What technical distinction explains the intended control?
BitLocker encrypts volumes at rest, while recovery requires access to stored key material if normal TPM unlocking fails. This mechanism is relevant because a physical Windows Server must protect its system volume while supporting disaster recovery after motherboard replacement. The administrator should enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement. Validate the decision by confirming that encryption reports protection active and a controlled recovery drill retrieves the correct authorized recovery key.
Encrypted Azure disks depend on their configured key model and access path; changing key grants without dependency analysis can break availability. This explains IaaS VM encryption key governance, for example: A security team needs controlled rotation and access auditing for keys protecting managed Azure VM disks. The decisive mechanism is that bitLocker encrypts volumes at rest, while recovery requires access to stored key material if normal TPM unlocking fails.
Domain controllers hold directory authentication and replication responsibilities, so tier-zero hardening reduces the blast radius of compromise. This explains Domain controller hardening, for example: A new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions. The decisive mechanism is that bitLocker encrypts volumes at rest, while recovery requires access to stored key material if normal TPM unlocking fails.
Azure Disk Encryption relies on supported in-guest encryption and associated secrets/keys; extension health alone does not guarantee recoverability. This explains Azure Disk Encryption implementation, for example: A team maintaining an existing Azure VM deployment uses the Azure Disk Encryption extension and needs to validate key access. The decisive mechanism is that bitLocker encrypts volumes at rest, while recovery requires access to stored key material if normal TPM unlocking fails.
A small fleet of Windows Servers needs centralized health inspection and alert thresholds without signing into every host.
What is the most directly justified remediation?
Use supported Windows Admin Center monitoring features and configure appropriate server health or alert integrations. This addresses the stated situation: A small fleet of Windows Servers needs centralized health inspection and alert thresholds without signing into every host. Windows Admin Center provides centralized Windows Server administration and insight but depends on properly scoped remote access and telemetry. Confirm the outcome by checking that approved operators can view health for each managed server and a controlled alert condition is reported as designed. If the control is skipped, assuming centralized alerts are configured merely because servers appear in the console can delay incident detection.
Create and run a Performance Monitor Data Collector Set using workload-relevant counters over representative intervals. This is more relevant to Performance Monitor counters and baselines, such as when an IIS server intermittently slows at peak load but operators have only single-point CPU measurements. PerfMon Data Collector Sets gather time-series counter evidence that can distinguish transient CPU, disk, memory and network bottlenecks. The appropriate action here is to use supported Windows Admin Center monitoring features and configure appropriate server health or alert integrations.
Configure an Azure Monitor data collection rule and association for supported agents, target machines and required data streams. This is more relevant to Azure Monitor data collection rules, such as when Azure Arc-enabled Windows Servers are connected to Azure but their security and performance events are not arriving in Log Analytics. Azure Monitor DCRs determine what telemetry an associated agent collects and routes to selected destinations. The appropriate action here is to use supported Windows Admin Center monitoring features and configure appropriate server health or alert integrations.
Enable supported Azure Monitor VM Insights data collection and validate guest performance coverage on target VMs. This is more relevant to VM Insights performance monitoring, such as when Azure IaaS Windows VMs need consistent memory, disk and process-performance dashboards across a subscription. VM Insights aggregates supported virtual-machine guest metrics and dependency information when required monitoring components are installed. The appropriate action here is to use supported Windows Admin Center monitoring features and configure appropriate server health or alert integrations.
The source data center has no hypervisor management plane for several servers selected for cloud migration.
Which underlying service behavior is most relevant?
Physical server replication to Azure uses compatible migration components and differs from a VM discovery-only inventory. This mechanism is relevant because the source data center has no hypervisor management plane for several servers selected for cloud migration. The administrator should use a supported Azure Migrate physical-server migration or agent-based approach with the correct source prerequisites. Validate the decision by confirming that the physical machine replicates successfully and a test Azure VM boots with correct drivers, network and application data.
Azure workload sizing depends on actual demand and supported target capabilities rather than simply preserving source hardware dimensions. This explains Azure VM readiness and right-sizing, for example: A legacy application runs on an oversized source VM but the migration team has no throughput or memory baseline. The decisive mechanism is that physical server replication to Azure uses compatible migration components and differs from a VM discovery-only inventory.
Azure Migrate discovery and assessment uses inventory and utilization evidence to inform sizing, readiness and cost recommendations. This explains Azure Migrate discovery appliance, for example: An organization plans to migrate VMware VMs but lacks inventory data about dependencies and utilization. The decisive mechanism is that physical server replication to Azure uses compatible migration components and differs from a VM discovery-only inventory.
Azure Migrate migration coordinates replication and target VM creation; test migration helps validate network and service behavior before committing. This explains Azure Migrate VM replication and cutover, for example: A verified on-premises Windows Server VM must be migrated to Azure with a controlled application cutover. The decisive mechanism is that physical server replication to Azure uses compatible migration components and differs from a VM discovery-only inventory.
A protected Azure Windows VM uses disk encryption and must be recovered after storage corruption.
What is the most directly justified remediation?
Restore the VM with the required supported encryption dependencies, key-vault access and recovery procedure. This addresses the stated situation: 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. Confirm the outcome by checking that a controlled restored VM boots and mounts its intended encrypted volumes under approved identity access. If the control is skipped, restoring encrypted disks without required keys can leave the recovery VM unusable despite healthy backups.
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 restore the VM with the required supported encryption dependencies, key-vault access and recovery procedure.
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 restore the VM with the required supported encryption dependencies, key-vault access and recovery procedure.
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 restore the VM with the required supported encryption dependencies, key-vault access and recovery procedure.
Please check your mailbox for a message from support@examlabs.com and follow the directions.