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
Security plans to enable BitLocker on branch disks but has not documented authorized recovery-key custody.
Which supported approach best meets the stated operational need?
Enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement. This addresses the stated situation: Security plans to enable BitLocker on branch disks but has not documented authorized recovery-key custody. BitLocker encrypts volumes at rest, while recovery requires access to stored key material if normal TPM unlocking fails. Confirm the outcome by checking that encryption reports protection active and a controlled recovery drill retrieves the correct authorized recovery key. If the control is skipped, encrypting without a retrievable recovery key can make data inaccessible after a TPM or hardware change.
Configure supported disk-encryption key management with least-privilege identities, protected vaults and a recovery validation process. This is more relevant to IaaS VM encryption key governance, such as when 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. The appropriate action here is to enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement.
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 enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement.
Deploy a staged Windows Defender Application Control policy that permits approved code and blocks untrusted executables. This is more relevant to Application control allowlist, such as when 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 appropriate action here is to enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement.
A branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch.
Which test result would best confirm the requirement has been met?
Approved branch accounts can log on under the intended network conditions, while denied privileged credentials are not cached. This specifically verifies the case: 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 matching action is to configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts.
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 branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch. Here, successful verification means that approved branch accounts can log on under the intended network conditions, while denied privileged credentials are not cached.
A weak branded password change is rejected on an on-premises domain controller while approved passwords are accepted. This would validate Entra Password Protection for AD DS, as in this different situation: A hybrid AD organization finds that users can choose predictable passwords containing the company name. It is not the most direct evidence for the case: A branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch. Here, successful verification means that approved branch accounts can log on under the intended network conditions, while denied privileged credentials are not cached.
Protected administrators authenticate with supported Kerberos paths and the required older authentication flows are appropriately blocked. This would validate Protected Users account group, as in this different situation: Tier-zero administrator credentials must not be exposed through legacy NTLM authentication on member machines. It is not the most direct evidence for the case: A branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch. Here, successful verification means that approved branch accounts can log on under the intended network conditions, while denied privileged credentials are not cached.
An S2D cluster suffers intermittent storage pauses while CPU utilization rises during large east-west transfers.
What technical distinction explains the intended control?
S2D commonly benefits from SMB Direct and appropriate lossless network behavior to keep storage traffic efficient and reliable. This mechanism is relevant because an S2D cluster suffers intermittent storage pauses while CPU utilization rises during large east-west transfers. The administrator should verify supported RDMA adapters, SMB Direct configuration, switch policies and cluster storage-network counters. Validate the decision by confirming that adapter and SMB performance counters show expected RDMA use while storage latency and dropped traffic return to baseline.
S2D pools supported local disks across clustered hosts and exposes resilient virtual disks; disk and network prerequisites are essential. This explains Storage Spaces Direct pool enablement, for example: Four qualified Windows Servers have local data disks and need resilient shared storage without a traditional SAN. The decisive mechanism is that S2D commonly benefits from SMB Direct and appropriate lossless network behavior to keep storage traffic efficient and reliable.
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 commonly benefits from SMB Direct and appropriate lossless network behavior to keep storage traffic efficient and reliable.
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 commonly benefits from SMB Direct and appropriate lossless network behavior to keep storage traffic efficient and reliable.
A two-site cluster has no dependable independent third datacenter for a file-share witness.
Which finding should be recorded as evidence of success?
Cluster witness health is normal and a simulated site failure preserves the intended quorum behavior. This specifically verifies the case: 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 matching action is to configure an Azure Cloud Witness using supported storage-account access, connectivity and cluster settings.
Cluster membership and supported client connections function using the configured non-domain identity and name-resolution paths. This would validate Workgroup cluster identity design, as in this different situation: A small isolated application cluster must be built without an Active Directory domain membership dependency. It is not the most direct evidence for the case: A two-site cluster has no dependable independent third datacenter for a file-share witness. Here, successful verification means that cluster witness health is normal and a simulated site failure preserves the intended quorum behavior.
A controlled site-failure exercise confirms consistent data, intended ownership and client reconnection within objectives. This would validate Stretch cluster across facilities, as in this different situation: An application must fail over between two physically separate datacenters while minimizing data loss. It is not the most direct evidence for the case: A two-site cluster has no dependable independent third datacenter for a file-share witness. Here, successful verification means that cluster witness health is normal and a simulated site failure preserves the intended quorum behavior.
A controlled node-loss test preserves quorum and supported cluster services under the planned failure scenario. This would validate Cluster quorum and witness planning, as in this different situation: A two-node Windows failover cluster needs to survive the loss of one node without unnecessary loss of quorum. It is not the most direct evidence for the case: A two-site cluster has no dependable independent third datacenter for a file-share witness. Here, successful verification means that cluster witness health is normal and a simulated site failure preserves the intended quorum behavior.
A legacy application runs on an oversized source VM but the migration team has no throughput or memory baseline.
Which explanation most directly supports the appropriate decision?
Azure workload sizing depends on actual demand and supported target capabilities rather than simply preserving source hardware dimensions. This mechanism is relevant because a legacy application runs on an oversized source VM but the migration team has no throughput or memory baseline. The administrator should review Azure Migrate readiness, observed performance, software compatibility and cost recommendations before selecting VM sizes. Validate the decision by confirming that the selected Azure VM size meets workload peak demand in a test with an explainable cost and rightsizing rationale.
Physical server replication to Azure uses compatible migration components and differs from a VM discovery-only inventory. This explains Azure Migrate physical servers, for example: A standalone Windows Server physical machine hosts an application that must run as an Azure virtual machine. The decisive mechanism is that Azure workload sizing depends on actual demand and supported target capabilities rather than simply preserving source hardware dimensions.
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 Azure workload sizing depends on actual demand and supported target capabilities rather than simply preserving source hardware dimensions.
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 Azure workload sizing depends on actual demand and supported target capabilities rather than simply preserving source hardware dimensions.
An older IIS application needs repeatable isolated runtime packaging because its dependencies do not fit the chosen PaaS configuration.
What could most specifically go wrong without the correct mitigation?
Containerizing without checking Windows image compatibility or persistent state can cause failures and data loss. This is the direct risk of the described condition: An older IIS application needs repeatable isolated runtime packaging because its dependencies do not fit the chosen PaaS configuration. Windows containers bundle compatible application dependencies while still depending on supported host/image versions and persistent-data design. The corrective approach is to evaluate supported Windows container images and package the IIS application with its required runtime and configuration.
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 containerizing without checking Windows image compatibility or persistent state can cause failures and data loss.
Copying only IIS files without configuring secrets and platform settings can fail at startup or deployment cutover. This is a risk associated with Migrate IIS application to Azure App Service, such as when a stateless ASP.NET application on IIS needs staging deployment slots and managed web hosting. For this case, the main exposure is that containerizing without checking Windows image compatibility or persistent state can cause failures and data loss.
Lifting an application into App Service without analyzing its OS dependencies can break functionality. This is a risk associated with IIS workload assessment for App Service, such as when an IIS web app is a possible candidate for Azure App Service but uses unsupported local Windows components. For this case, the main exposure is that containerizing without checking Windows image compatibility or persistent state can cause failures and data loss.
An older IIS server runs several applications with custom bindings, certificates and authentication settings.
What would provide the strongest verification of the intended solution?
A post-migration application test verifies certificates, host headers, app pools, authentication and backend connectivity. This specifically verifies the case: An older IIS server runs several applications with custom bindings, certificates and authentication settings. IIS application function depends on web-server configuration and runtime identity in addition to static website files. The matching action is to inventory and migrate IIS configuration, app pools, bindings, certificates and application dependencies as well as content.
Test clients receive addresses and expected gateway/DNS options from the intended new server without conflicting leases. This would validate DHCP migration with leases and options, as in this different situation: A new Windows Server will replace a legacy DHCP server serving multiple network scopes. It is not the most direct evidence for the case: An older IIS server runs several applications with custom bindings, certificates and authentication settings. Here, successful verification means that a post-migration application test verifies certificates, host headers, app pools, authentication and backend connectivity.
The chosen upgrade or migration passes application testing and the rollback procedure remains feasible before commitment. This would validate Choose in-place upgrade versus side-by-side migration, as in this different situation: A very old Windows Server installation hosts an application that cannot tolerate an unsupported direct OS upgrade. It is not the most direct evidence for the case: An older IIS server runs several applications with custom bindings, certificates and authentication settings. Here, successful verification means that a post-migration application test verifies certificates, host headers, app pools, authentication and backend connectivity.
A test workstation connects to a migrated printer and prints through the new queue with correct permissions. This would validate Print server migration, as in this different situation: An office has hundreds of printer queues tied to a Windows Server scheduled for decommissioning. It is not the most direct evidence for the case: An older IIS server runs several applications with custom bindings, certificates and authentication settings. Here, successful verification means that a post-migration application test verifies certificates, host headers, app pools, authentication and backend connectivity.
A very old Windows Server installation hosts an application that cannot tolerate an unsupported direct OS upgrade.
What would provide the strongest verification of the intended solution?
The chosen upgrade or migration passes application testing and the rollback procedure remains feasible before commitment. This specifically verifies the case: A very old Windows Server installation hosts an application that cannot tolerate an unsupported direct OS upgrade. Windows Server upgrade paths and application dependencies constrain which versions can be upgraded directly; side-by-side replacement isolates risk. The matching action is to check version/application compatibility and choose a supported staged in-place upgrade or side-by-side migration with a rollback plan.
A post-migration application test verifies certificates, host headers, app pools, authentication and backend connectivity. This would validate Migrate IIS site configuration, as in this different situation: An older IIS server runs several applications with custom bindings, certificates and authentication settings. It is not the most direct evidence for the case: A very old Windows Server installation hosts an application that cannot tolerate an unsupported direct OS upgrade. Here, successful verification means that the chosen upgrade or migration passes application testing and the rollback procedure remains feasible before commitment.
Test clients receive addresses and expected gateway/DNS options from the intended new server without conflicting leases. This would validate DHCP migration with leases and options, as in this different situation: A new Windows Server will replace a legacy DHCP server serving multiple network scopes. It is not the most direct evidence for the case: A very old Windows Server installation hosts an application that cannot tolerate an unsupported direct OS upgrade. Here, successful verification means that the chosen upgrade or migration passes application testing and the rollback procedure remains feasible before commitment.
A test workstation connects to a migrated printer and prints through the new queue with correct permissions. This would validate Print server migration, as in this different situation: An office has hundreds of printer queues tied to a Windows Server scheduled for decommissioning. It is not the most direct evidence for the case: A very old Windows Server installation hosts an application that cannot tolerate an unsupported direct OS upgrade. Here, successful verification means that the chosen upgrade or migration passes application testing and the rollback procedure remains feasible before commitment.
A cloud governance review needs to compare security configuration of Azure VMs and Arc-enabled servers.
What technical distinction explains the intended control?
Defender for Cloud combines posture assessment and workload protection insights, including supported hybrid servers through Azure Arc. This mechanism is relevant because a cloud governance review needs to compare security configuration of Azure VMs and Arc-enabled servers. The administrator should onboard supported servers to Microsoft Defender for Cloud and remediate assessed security recommendations by priority. Validate the decision by confirming that the target machines appear in inventory with expected recommendations and the remediated control changes its finding state.
Sentinel analytics relies on ingested telemetry, usually routed through Azure Monitor components and supported connectors. This explains Microsoft Sentinel security telemetry, for example: Security operations must correlate Windows Server security events from multiple sites with cloud identity alerts. The decisive mechanism is that defender for Cloud combines posture assessment and workload protection insights, including supported hybrid servers through Azure Arc.
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 defender for Cloud combines posture assessment and workload protection insights, including supported hybrid servers through Azure Arc.
Defender for Servers provides server workload protection features that differ from posture-only inventory and depend on plan and agent configuration. This explains Defender for Servers threat protection, for example: Azure-hosted Windows Server workloads need endpoint threat alerts and vulnerability assessment beyond configuration-only review. The decisive mechanism is that defender for Cloud combines posture assessment and workload protection insights, including supported hybrid servers through Azure Arc.
Cloud users see stale account information after an on-premises AD attribute change despite healthy local replication.
What is the most appropriate next administrative action?
Check synchronization scope, connector health, error queues and identity mapping in the supported Microsoft Entra synchronization path. This addresses the stated situation: Cloud users see stale account information after an on-premises AD attribute change despite healthy local replication. Hybrid directory synchronization propagates eligible on-premises identity changes only when the connector, scope and attribute mapping are healthy. Confirm the outcome by checking that a controlled attribute change appears on the cloud identity within the expected sync interval and errors clear. If the control is skipped, ignoring synchronization failures can leave inactive accounts or stale permissions in cloud services.
Inspect AD DS replication status, site links, connectivity and directory service errors, then fix the specific replication fault. This is more relevant to Active Directory replication topology, such as when 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 appropriate action here is to check synchronization scope, connector health, error queues and identity mapping in the supported Microsoft Entra synchronization path.
Inspect DFS Replication health and SYSVOL state on affected domain controllers before republishing policy objects. This is more relevant to SYSVOL replication troubleshooting, such as when a newly created Group Policy Object reaches one domain controller but not another because SYSVOL contents are missing. SYSVOL contains file-based Group Policy and scripts, and DFSR failures can create inconsistent policy delivery even when AD object replication works. The appropriate action here is to check synchronization scope, connector health, error queues and identity mapping in the supported Microsoft Entra synchronization path.
Use the appropriate Directory Services Restore Mode and validated system-state recovery procedure for the specific AD DS failure. This is more relevant to DSRM directory database recovery, such as when a domain controller's AD DS database is damaged and an ordinary service restart cannot bring directory services online. DSRM provides an offline maintenance environment for directory database recovery when normal AD DS operation is unavailable. The appropriate action here is to check synchronization scope, connector health, error queues and identity mapping in the supported Microsoft Entra synchronization path.
A standalone Windows Server physical machine hosts an application that must run as an Azure virtual machine.
Which finding should be recorded as evidence of success?
The physical machine replicates successfully and a test Azure VM boots with correct drivers, network and application data. This specifically verifies the case: A standalone Windows Server physical machine hosts an application that must run as an Azure virtual machine. Physical server replication to Azure uses compatible migration components and differs from a VM discovery-only inventory. The matching action is to use a supported Azure Migrate physical-server migration or agent-based approach with the correct source prerequisites.
A test-migrated VM functions on the intended Azure network and the final cutover meets the agreed data freshness and service objectives. This would validate Azure Migrate VM replication and cutover, as in this different situation: A verified on-premises Windows Server VM must be migrated to Azure with a controlled application cutover. It is not the most direct evidence for the case: A standalone Windows Server physical machine hosts an application that must run as an Azure virtual machine. Here, successful verification means that the physical machine replicates successfully and a test Azure VM boots with correct drivers, network and application data.
Discovered machines appear in the project and produce assessment results based on a representative observation period. This would validate Azure Migrate discovery appliance, as in this different situation: An organization plans to migrate VMware VMs but lacks inventory data about dependencies and utilization. It is not the most direct evidence for the case: A standalone Windows Server physical machine hosts an application that must run as an Azure virtual machine. Here, successful verification means that the physical machine replicates successfully and a test Azure VM boots with correct drivers, network and application data.
The selected Azure VM size meets workload peak demand in a test with an explainable cost and rightsizing rationale. This would validate Azure VM readiness and right-sizing, as in this different situation: A legacy application runs on an oversized source VM but the migration team has no throughput or memory baseline. It is not the most direct evidence for the case: A standalone Windows Server physical machine hosts an application that must run as an Azure virtual machine. Here, successful verification means that the physical machine replicates successfully and a test Azure VM boots with correct drivers, network and application data.
Please check your mailbox for a message from support@examlabs.com and follow the directions.