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 security team needs controlled rotation and access auditing for keys protecting managed Azure VM disks.
What is the most directly justified remediation?
Configure supported disk-encryption key management with least-privilege identities, protected vaults and a recovery validation process. This addresses the stated situation: A security team needs controlled rotation and access auditing for keys protecting managed Azure VM disks. Encrypted Azure disks depend on their configured key model and access path; changing key grants without dependency analysis can break availability. Confirm the outcome by checking that the correct identity can access the expected key during a restoration test and unauthorized principals cannot use it. If the control is skipped, over-restricting or deleting encryption keys can render recoverable infrastructure disks unusable.
For supported existing deployments, verify Azure Disk Encryption extension status and required key-vault access and recovery procedures. This is more relevant to Azure Disk Encryption implementation, such as when a team maintaining an existing Azure VM deployment uses the Azure Disk Encryption extension and needs to validate key access. Azure Disk Encryption relies on supported in-guest encryption and associated secrets/keys; extension health alone does not guarantee recoverability. The appropriate action here is to configure supported disk-encryption key management with least-privilege identities, protected vaults and a recovery validation process.
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 supported disk-encryption key management with least-privilege identities, protected vaults and a recovery validation process.
Enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement. This is more relevant to BitLocker recovery-key readiness, such as when a physical Windows Server must protect its system volume while supporting disaster recovery after motherboard replacement. BitLocker encrypts volumes at rest, while recovery requires access to stored key material if normal TPM unlocking fails. The appropriate action here is to configure supported disk-encryption key management with least-privilege identities, protected vaults and a recovery validation process.
A cluster build team wants to convert eligible local drives into clustered Storage Spaces Direct capacity.
What technical distinction explains the intended control?
S2D pools supported local disks across clustered hosts and exposes resilient virtual disks; disk and network prerequisites are essential. This mechanism is relevant because a cluster build team wants to convert eligible local drives into clustered Storage Spaces Direct capacity. The administrator should validate supported S2D hardware and enable Storage Spaces Direct on eligible cluster nodes before creating resilient volumes. Validate the decision by confirming that the storage pool shows healthy eligible disks and resilient volumes remain available under a planned disk or node failure.
S2D commonly benefits from SMB Direct and appropriate lossless network behavior to keep storage traffic efficient and reliable. This explains RDMA traffic health for Storage Spaces Direct, for example: An S2D cluster suffers intermittent storage pauses while CPU utilization rises during large east-west transfers. The decisive mechanism is that S2D pools supported local disks across clustered hosts and exposes resilient virtual disks; disk and network prerequisites are essential.
Removing S2D fault domains changes data-placement redundancy; healthy repair state is a prerequisite for safe staged maintenance. This explains Upgrade an S2D storage node safely, for example: An S2D cluster must replace an aging node without sacrificing data integrity during the transition. The decisive mechanism is that S2D pools supported local disks across clustered hosts and exposes resilient virtual disks; disk and network prerequisites are essential.
S2D resiliency depends on free capacity and healthy fault domains for data repair after host or disk failure. This explains Storage Spaces Direct repair and capacity reserve, for example: A node in a Storage Spaces Direct cluster fails and the remaining hosts must rebuild missing data copies. The decisive mechanism is that S2D pools supported local disks across clustered hosts and exposes resilient virtual disks; disk and network prerequisites are essential.
A remote domain controller has stale user group membership despite reliable local authentication.
Which acceptance result most directly demonstrates a working configuration?
Replication diagnostics show no persistent failures and the changed object converges on the affected remote domain controller. This specifically verifies the case: A remote domain controller has stale user group membership despite reliable local authentication. AD DS replicates directory objects across domain controllers using site topology and scheduled or notification-based replication. The matching action is to inspect AD DS replication status, site links, connectivity and directory service errors, then fix the specific replication fault.
SYSVOL shares and replicated policy files agree on all required controllers and client policy processing becomes consistent. This would validate SYSVOL replication troubleshooting, as in this different situation: A newly created Group Policy Object reaches one domain controller but not another because SYSVOL contents are missing. It is not the most direct evidence for the case: A remote domain controller has stale user group membership despite reliable local authentication. Here, successful verification means that replication diagnostics show no persistent failures and the changed object converges on the affected remote domain controller.
The restored controller starts correctly and replication/directory integrity checks pass under a documented recovery procedure. This would validate DSRM directory database recovery, as in this different situation: A domain controller's AD DS database is damaged and an ordinary service restart cannot bring directory services online. It is not the most direct evidence for the case: A remote domain controller has stale user group membership despite reliable local authentication. Here, successful verification means that replication diagnostics show no persistent failures and the changed object converges on the affected remote domain controller.
A controlled attribute change appears on the cloud identity within the expected sync interval and errors clear. This would validate Hybrid identity synchronization, as in this different situation: Cloud users see stale account information after an on-premises AD attribute change despite healthy local replication. It is not the most direct evidence for the case: A remote domain controller has stale user group membership despite reliable local authentication. Here, successful verification means that replication diagnostics show no persistent failures and the changed object converges on the affected remote domain controller.
A Windows Server can ping its default gateway but cannot reach a remote TCP service across the WAN.
What technical distinction explains the intended control?
IP reachability to one hop does not demonstrate end-to-end name resolution, routing or application port access. This mechanism is relevant because a Windows Server can ping its default gateway but cannot reach a remote TCP service across the WAN. The administrator should use layered Windows TCP/IP diagnostics for routes, DNS, firewall rules and target TCP connectivity before changing the application. Validate the decision by confirming that tests isolate the failed network hop or port and the intended remote service accepts authorized connections after correction.
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 iP reachability to one hop does not demonstrate end-to-end name resolution, routing or application port access.
Name resolution maps service names to addresses and depends on correct DNS zone data and cache behavior. This explains DNS client and server resolution, for example: A Windows file server is reachable by IP address but fails when clients use the configured host name. The decisive mechanism is that iP reachability to one hop does not demonstrate end-to-end name resolution, routing or application port access.
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 iP reachability to one hop does not demonstrate end-to-end name resolution, routing or application port access.
An operator is about to fill every remaining S2D disk and assumes rebuild capacity is unnecessary.
Which implementation step should the Windows Server administrator prioritize?
Monitor virtual disk health and repair jobs, preserve sufficient free pool capacity and restore the failed storage fault domain. This addresses the stated situation: An operator is about to fill every remaining S2D disk and assumes rebuild capacity is unnecessary. S2D resiliency depends on free capacity and healthy fault domains for data repair after host or disk failure. Confirm the outcome by checking that repair jobs complete and virtual disks return to healthy redundancy without storage exhaustion. If the control is skipped, operating an S2D pool with no repair headroom can leave protection degraded after ordinary failures.
Validate supported S2D hardware and enable Storage Spaces Direct on eligible cluster nodes before creating resilient volumes. This is more relevant to Storage Spaces Direct pool enablement, such as when four qualified Windows Servers have local data disks and need resilient shared storage without a traditional SAN. S2D pools supported local disks across clustered hosts and exposes resilient virtual disks; disk and network prerequisites are essential. The appropriate action here is to monitor virtual disk health and repair jobs, preserve sufficient free pool capacity and restore the failed storage fault domain.
Verify supported RDMA adapters, SMB Direct configuration, switch policies and cluster storage-network counters. This is more relevant to RDMA traffic health for Storage Spaces Direct, such as when an S2D cluster suffers intermittent storage pauses while CPU utilization rises during large east-west transfers. S2D commonly benefits from SMB Direct and appropriate lossless network behavior to keep storage traffic efficient and reliable. The appropriate action here is to monitor virtual disk health and repair jobs, preserve sufficient free pool capacity and restore the failed storage fault domain.
Complete repair, confirm healthy redundancy, drain the target node and follow supported replacement procedures. This is more relevant to Upgrade an S2D storage node safely, such as when an S2D cluster must replace an aging node without sacrificing data integrity during the transition. Removing S2D fault domains changes data-placement redundancy; healthy repair state is a prerequisite for safe staged maintenance. The appropriate action here is to monitor virtual disk health and repair jobs, preserve sufficient free pool capacity and restore the failed storage fault domain.
A security audit finds domain controllers share the same network and administrative access rules as ordinary servers.
Which underlying service behavior is most relevant?
Domain controllers hold directory authentication and replication responsibilities, so tier-zero hardening reduces the blast radius of compromise. This mechanism is relevant because a security audit finds domain controllers share the same network and administrative access rules as ordinary servers. 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.
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.
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.
Administrators need repeatable network configuration across cluster hosts with RDMA-capable interfaces.
Which technical principle best explains why the correct solution works?
Network ATC expresses host networking intent and applies consistent configuration across eligible cluster nodes. This mechanism is relevant because administrators need repeatable network configuration across cluster hosts with RDMA-capable interfaces. The administrator should use supported Network ATC intent policies to deploy consistent management, compute and storage network settings. Validate the decision by confirming that effective host adapters, RDMA, VLAN and virtual switches match the intended policy on all selected nodes.
Storage Spaces Direct uses fault-domain and resiliency settings to decide data placement and survivability across failures. This explains Storage Spaces Direct campus cluster fault domains, for example: A campus cluster must tolerate a whole-building outage without losing data consistency. The decisive mechanism is that network ATC expresses host networking intent and applies consistent configuration across eligible cluster nodes.
Scale-Out File Server supports active-access clustered file services for suitable application-data workloads such as Hyper-V and SQL Server. This explains Scale-Out File Server workloads, for example: A Hyper-V virtualization farm requires continuously available SMB storage backed by a Windows failover cluster. The decisive mechanism is that network ATC expresses host networking intent and applies consistent configuration across eligible cluster nodes.
A stretched failover cluster spans fault domains, but application continuity depends on storage consistency, quorum and supported connectivity. This explains Stretch cluster across facilities, for example: An application must fail over between two physically separate datacenters while minimizing data loss. The decisive mechanism is that network ATC expresses host networking intent and applies consistent configuration across eligible cluster nodes.
An on-premises application server requires centrally scheduled backups with off-site Azure retention.
Which finding should be recorded as evidence of success?
A supported workload backup completes and an authorized restore test verifies application-consistent data under the retention policy. This specifically verifies the case: 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 matching action is to deploy a supported Microsoft Azure Backup Server configuration and register it for appropriate off-site protection.
The specified folder is recovered with correct content and permissions while unrelated current application files stay intact. This would validate Azure Backup file and folder restore, as in this different situation: A finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM. It is not the most direct evidence for the case: An on-premises application server requires centrally scheduled backups with off-site Azure retention. Here, successful verification means that a supported workload backup completes and an authorized restore test verifies application-consistent data under the retention policy.
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: An on-premises application server requires centrally scheduled backups with off-site Azure retention. Here, successful verification means that a supported workload backup completes and an authorized restore test verifies application-consistent data under the retention policy.
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: An on-premises application server requires centrally scheduled backups with off-site Azure retention. Here, successful verification means that a supported workload backup completes and an authorized restore test verifies application-consistent data under the retention policy.
An enterprise needs reliable centralized operational and security events from domain-joined Windows Servers.
What observable evidence is most important for successful validation?
A selected Windows event is queryable centrally with accurate source identity and timestamp within retention requirements. This specifically verifies the case: An enterprise needs reliable centralized operational and security events from domain-joined Windows Servers. Windows event logs preserve structured operational evidence; centralized retention reduces loss when individual servers fail. The matching action is to configure supported event collection or forwarding, time synchronization, scoped access and sufficient log retention.
Forecasted disk consumption aligns with observed trends and triggers an actionable capacity response before thresholds are exceeded. This would validate System Insights capacity forecasts, as in this different situation: A Windows Server file host repeatedly approaches free-space alerts without reliable forecasting. It is not the most direct evidence for the case: An enterprise needs reliable centralized operational and security events from domain-joined Windows Servers. Here, successful verification means that a selected Windows event is queryable centrally with accurate source identity and timestamp within retention requirements.
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: An enterprise needs reliable centralized operational and security events from domain-joined Windows Servers. Here, successful verification means that a selected Windows event is queryable centrally with accurate source identity and timestamp within retention requirements.
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: An enterprise needs reliable centralized operational and security events from domain-joined Windows Servers. Here, successful verification means that a selected Windows event is queryable centrally with accurate source identity and timestamp within retention requirements.
A domain modernization team must locate legacy NTLM consumers before disabling weaker authentication.
What observable evidence is most important for successful validation?
Events show expected legacy usage has been remediated before restrictions, and target logons continue using supported mechanisms. This specifically verifies the case: 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 matching action is to enable relevant NTLM auditing, identify dependencies, remediate application configuration, and enforce restrictions in phases.
Sensors report healthy status and a supported test signal produces identity-related investigation context in the security portal. This would validate Defender for Identity directory sensors, as in this different situation: Security analysts need to detect suspicious AD reconnaissance and lateral-movement activity around domain controllers. It is not the most direct evidence for the case: A domain modernization team must locate legacy NTLM consumers before disabling weaker authentication. Here, successful verification means that events show expected legacy usage has been remediated before restrictions, and target logons continue using supported mechanisms.
Test logons succeed on the allowed host set and are rejected on out-of-scope computers with meaningful authentication events. This would validate Authentication policy silos, as in this different situation: Tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. It is not the most direct evidence for the case: A domain modernization team must locate legacy NTLM consumers before disabling weaker authentication. Here, successful verification means that events show expected legacy usage has been remediated before restrictions, and target logons continue using supported mechanisms.
Baseline review and connectivity tests show only required directory services and approved administrative endpoints remain accessible. This would validate Domain controller hardening, as in this different situation: A new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions. It is not the most direct evidence for the case: A domain modernization team must locate legacy NTLM consumers before disabling weaker authentication. Here, successful verification means that events show expected legacy usage has been remediated before restrictions, and target logons continue using supported mechanisms.
A security team wants extra credential-theft resistance for a small set of privileged AD DS user accounts.
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: A security team wants extra credential-theft resistance for a small set of privileged AD DS user accounts. 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.
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.
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.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.