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 server accidentally exposes RDP on a public network profile while administrators require limited management access.
Which adverse outcome best describes the untreated issue?
Broadly disabling the host firewall can expose management services even when upstream filtering changes. This is the direct risk of the described condition: A server accidentally exposes RDP on a public network profile while administrators require limited management access. Host firewall profile rules filter traffic at the individual machine independently of perimeter firewalls or NSGs. The corrective approach is to configure Windows Defender Firewall rules scoped by profile, protocol, port, remote address and administration requirement.
Relying solely on Windows Firewall while leaving broad NSG exposure increases unintended reachable attack surface. This is a risk associated with Azure NSG filtering for Windows VM, such as when an Azure Windows VM accepts inbound RDP from the public Internet even though access should be limited to a bastion subnet. For this case, the main exposure is that broadly disabling the host firewall can expose management services even when upstream filtering changes.
Confusing a firewall allow rule with IPsec authentication can permit spoofed or unauthenticated connections. This is a risk associated with Windows IPsec connection security rules, such as when sensitive server-to-server traffic on the same corporate subnet must be authenticated independently of application logins. For this case, the main exposure is that broadly disabling the host firewall can expose management services even when upstream filtering changes.
Over-restricting or deleting encryption keys can render recoverable infrastructure disks unusable. This is a risk associated with IaaS VM encryption key governance, such as when a security team needs controlled rotation and access auditing for keys protecting managed Azure VM disks. For this case, the main exposure is that broadly disabling the host firewall can expose management services even when upstream filtering changes.
A team maintaining an existing Azure VM deployment uses the Azure Disk Encryption extension and needs to validate key access.
What would provide the strongest verification of the intended solution?
An authorized restoration successfully accesses encryption material and boots or mounts the recovered encrypted disk. This specifically verifies the case: 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 matching action is to for supported existing deployments, verify Azure Disk Encryption extension status and required key-vault access and recovery procedures.
Encryption reports protection active and a controlled recovery drill retrieves the correct authorized recovery key. This would validate BitLocker recovery-key readiness, as in this different situation: A physical Windows Server must protect its system volume while supporting disaster recovery after motherboard replacement. It is not the most direct evidence for the case: A team maintaining an existing Azure VM deployment uses the Azure Disk Encryption extension and needs to validate key access. Here, successful verification means that an authorized restoration successfully accesses encryption material and boots or mounts the recovered encrypted disk.
The target machines appear in inventory with expected recommendations and the remediated control changes its finding state. This would validate Microsoft Defender for Cloud posture findings, as in this different situation: Hybrid Windows Servers have inconsistent hardening and central security needs risk-ranked recommendations. It is not the most direct evidence for the case: A team maintaining an existing Azure VM deployment uses the Azure Disk Encryption extension and needs to validate key access. Here, successful verification means that an authorized restoration successfully accesses encryption material and boots or mounts the recovered encrypted disk.
The correct identity can access the expected key during a restoration test and unauthorized principals cannot use it. This would validate IaaS VM encryption key governance, as in this different situation: A security team needs controlled rotation and access auditing for keys protecting managed Azure VM disks. It is not the most direct evidence for the case: A team maintaining an existing Azure VM deployment uses the Azure Disk Encryption extension and needs to validate key access. Here, successful verification means that an authorized restoration successfully accesses encryption material and boots or mounts the recovered encrypted disk.
An infrastructure team wants centrally governed server threat protection across Azure and supported hybrid machines.
What is the most appropriate next administrative action?
Enable the appropriate Microsoft Defender for Servers plan and verify deployment of its supported protective components. This addresses the stated situation: An infrastructure team wants centrally governed server threat protection across Azure and supported hybrid machines. Defender for Servers provides server workload protection features that differ from posture-only inventory and depend on plan and agent configuration. Confirm the outcome by checking that the targeted VM shows healthy coverage and a representative alert or assessment becomes available in the security workflow. If the control is skipped, enabling a subscription label without confirming actual server onboarding can leave coverage gaps undetected.
Configure the appropriate Microsoft Sentinel data connector and collection path for Windows Server security events. This is more relevant to Microsoft Sentinel security telemetry, such as when security operations must correlate Windows Server security events from multiple sites with cloud identity alerts. Sentinel analytics relies on ingested telemetry, usually routed through Azure Monitor components and supported connectors. The appropriate action here is to enable the appropriate Microsoft Defender for Servers plan and verify deployment of its supported protective components.
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 enable the appropriate Microsoft Defender for Servers plan and verify deployment of its supported protective components.
Onboard supported servers to Microsoft Defender for Cloud and remediate assessed security recommendations by priority. This is more relevant to Microsoft Defender for Cloud posture findings, such as when hybrid Windows Servers have inconsistent hardening and central security needs risk-ranked recommendations. Defender for Cloud combines posture assessment and workload protection insights, including supported hybrid servers through Azure Arc. The appropriate action here is to enable the appropriate Microsoft Defender for Servers plan and verify deployment of its supported protective components.
A campus cluster must tolerate a whole-building outage without losing data consistency.
Which failure mode is most relevant if the required control is omitted?
Ignoring physical failure domains can place redundant copies together and undermine site resilience. This is the direct risk of the described condition: 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. The corrective approach is to assign supported S2D site or fault-domain awareness and choose storage resiliency suited to the campus topology.
Unreachable or misconfigured cloud-witness storage can eliminate the expected extra quorum vote when needed. This is a risk associated with Azure cloud witness placement, such as when a two-site cluster has no dependable independent third datacenter for a file-share witness. For this case, the main exposure is that ignoring physical failure domains can place redundant copies together and undermine site resilience.
Treating two datacenters as one LAN without storage or quorum planning risks split-brain and extended downtime. This is a risk associated with Stretch cluster across facilities, such as when an application must fail over between two physically separate datacenters while minimizing data loss. For this case, the main exposure is that ignoring physical failure domains can place redundant copies together and undermine site resilience.
Hand-configured inconsistent adapters can interrupt east-west storage traffic and impair cluster resiliency. This is a risk associated with 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. For this case, the main exposure is that ignoring physical failure domains can place redundant copies together and undermine site resilience.
Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised.
What would provide the strongest verification of the intended solution?
The server rotates its local password, authorized recovery succeeds and an unrelated operator cannot retrieve the secret. This specifically verifies the case: Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised. Windows LAPS manages distinct rotating local administrator credentials and protects their recovery through supported directory permissions. The matching action is to configure Windows LAPS backup, rotation and authorized password retrieval for each managed Windows Server computer.
A post-deployment compliance assessment shows target settings in their expected state and records any deliberate exception. This would validate OSConfig baseline drift, as in this different situation: Security policy requires a consistent Windows Server 2025 configuration despite manual changes by server operators. It is not the most direct evidence for the case: Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised. Here, successful verification means that the server rotates its local password, authorized recovery succeeds and an unrelated operator cannot retrieve the secret.
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: Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised. Here, successful verification means that the server rotates its local password, authorized recovery succeeds and an unrelated operator cannot retrieve the secret.
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: Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised. Here, successful verification means that the server rotates its local password, authorized recovery succeeds and an unrelated operator cannot retrieve the secret.
Tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers.
Which test result would best confirm the requirement has been met?
Test logons succeed on the allowed host set and are rejected on out-of-scope computers with meaningful authentication events. This specifically verifies the case: 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 matching action is to design and enforce supported AD authentication policies and authentication policy silos for the privileged identities and eligible hosts.
Approved branch accounts can log on under the intended network conditions, while denied privileged credentials are not cached. This would validate RODC password replication policy, as in this different situation: A branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch. It is not the most direct evidence for the case: Tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. Here, successful verification means that test logons succeed on the allowed host set and are rejected on out-of-scope computers with meaningful authentication events.
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: Tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. Here, successful verification means that test logons succeed on the allowed host set and are rejected on out-of-scope computers with meaningful authentication events.
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: Tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. Here, successful verification means that test logons succeed on the allowed host set and are rejected on out-of-scope computers with meaningful authentication events.
An operations team needs predictive signals about disk and resource trends before an application fills its volume.
Which underlying service behavior is most relevant?
System Insights uses local machine data to generate forecasts for resource trends that inform proactive capacity planning. This mechanism is relevant because an operations team needs predictive signals about disk and resource trends before an application fills its volume. The administrator should use supported Windows Server System Insights forecasting capabilities and validate its predictive data quality. Validate the decision by confirming that forecasted disk consumption aligns with observed trends and triggers an actionable capacity response before thresholds are exceeded.
Windows event logs preserve structured operational evidence; centralized retention reduces loss when individual servers fail. This explains Event log forwarding and retention, for example: Investigators cannot reconstruct a server failure because system logs were overwritten before analysis. The decisive mechanism is that system Insights uses local machine data to generate forecasts for resource trends that inform proactive capacity planning.
VM Insights aggregates supported virtual-machine guest metrics and dependency information when required monitoring components are installed. This explains VM Insights performance monitoring, for example: Azure IaaS Windows VMs need consistent memory, disk and process-performance dashboards across a subscription. The decisive mechanism is that system Insights uses local machine data to generate forecasts for resource trends that inform proactive capacity planning.
Azure Monitor DCRs determine what telemetry an associated agent collects and routes to selected destinations. This explains Azure Monitor data collection rules, for example: Azure Arc-enabled Windows Servers are connected to Azure but their security and performance events are not arriving in Log Analytics. The decisive mechanism is that system Insights uses local machine data to generate forecasts for resource trends that inform proactive capacity planning.
A team maintaining an existing Azure VM deployment uses the Azure Disk Encryption extension and needs to validate key access.
Which supported approach best meets the stated operational need?
For supported existing deployments, verify Azure Disk Encryption extension status and required key-vault access and recovery procedures. This addresses the stated situation: 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. Confirm the outcome by checking that an authorized restoration successfully accesses encryption material and boots or mounts the recovered encrypted disk. If the control is skipped, removing required key-vault access or secrets can prevent recovery even when an encrypted disk snapshot is intact.
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 for supported existing deployments, verify Azure Disk Encryption extension status and required key-vault access and recovery procedures.
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 for supported existing deployments, verify Azure Disk Encryption extension status and required key-vault access and recovery procedures.
Pilot Windows Exploit Protection mitigations for the executable, verify compatibility, and deploy the tested policy by management tools. This is more relevant to Exploit Protection mitigation policy, such as when 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 appropriate action here is to for supported existing deployments, verify Azure Disk Encryption extension status and required key-vault access and recovery procedures.
Clients still resolve the old file server name after successful data transfer to a replacement host.
What would provide the strongest verification of the intended solution?
A controlled cutover shows clients reaching migrated shares through the planned name while the legacy server is safely removed. This specifically verifies the case: Clients still resolve the old file server name after successful data transfer to a replacement host. SMS cutover can preserve an expected client-facing server identity within supported conditions, separating data copy from service transition. The matching action is to use supported Storage Migration Service cutover procedures to transfer the approved identity or connection endpoint to the target.
Destination files and share ACL tests match the expected source access for authorized and unauthorized users. This would validate Storage Migration Service transfer and ACLs, as in this different situation: A legacy file server hosts millions of files with complex NTFS permissions that must survive migration. It is not the most direct evidence for the case: Clients still resolve the old file server name after successful data transfer to a replacement host. Here, successful verification means that a controlled cutover shows clients reaching migrated shares through the planned name while the legacy server is safely removed.
Approved clients mount the Azure file share with expected access while out-of-scope users are denied. This would validate Azure Files destination migration, as in this different situation: An on-premises Windows file share must move to Azure Files with SMB access and retained permissions. It is not the most direct evidence for the case: Clients still resolve the old file server name after successful data transfer to a replacement host. Here, successful verification means that a controlled cutover shows clients reaching migrated shares through the planned name while the legacy server is safely removed.
Inventory reports the source shares and permissions, identifies incompatible items and maps them to the intended destination. This would validate Storage Migration Service inventory, as in this different situation: An organization must move legacy file servers while preserving share names and security descriptors. It is not the most direct evidence for the case: Clients still resolve the old file server name after successful data transfer to a replacement host. Here, successful verification means that a controlled cutover shows clients reaching migrated shares through the planned name while the legacy server is safely removed.
A three-tier service must recover database, application and web tiers in a dependency-aware order.
Which test result would best confirm the requirement has been met?
A controlled drill starts tiers in the intended order and records successful steps and required operator approvals. This specifically verifies the case: A three-tier service must recover database, application and web tiers in a dependency-aware order. ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions. The matching action is to build and test an Azure Site Recovery recovery plan with dependency-appropriate groups and supported automation or manual steps.
A test failover VM receives the expected network placement and communicates with approved application dependencies. This would validate Azure Site Recovery network mapping, as in this different situation: A replicated application VM starts during a recovery drill but its virtual network cannot reach dependent services. It is not the most direct evidence for the case: A three-tier service must recover database, application and web tiers in a dependency-aware order. Here, successful verification means that a controlled drill starts tiers in the intended order and records successful steps and required operator approvals.
Replication health is green, a recovery point exists and a non-disruptive test failover starts the workload in the selected recovery environment. This would validate Azure Site Recovery region replication, as in this different situation: A business requires a protected Azure Windows VM to survive loss of its primary Azure region. It is not the most direct evidence for the case: A three-tier service must recover database, application and web tiers in a dependency-aware order. Here, successful verification means that a controlled drill starts tiers in the intended order and records successful steps and required operator approvals.
Replication monitoring and a test failover confirm a recovery point meets the documented freshness and application consistency objective. This would validate ASR replication policy and recovery points, as in this different situation: A recovery auditor requires a measurable RPO and enough recovery history for a Windows application VM. It is not the most direct evidence for the case: A three-tier service must recover database, application and web tiers in a dependency-aware order. Here, successful verification means that a controlled drill starts tiers in the intended order and records successful steps and required operator approvals.
An organization must move legacy file servers while preserving share names and security descriptors.
What technical distinction explains the intended control?
Storage Migration Service inventories source server data and configurations to support staged file-server migration planning. This mechanism is relevant because an organization must move legacy file servers while preserving share names and security descriptors. The administrator should run Storage Migration Service inventory and assess share, file, account and destination requirements before transferring data. Validate the decision by confirming that inventory reports the source shares and permissions, identifies incompatible items and maps them to the intended destination.
SMS coordinates transfer of file data and supported configuration; migration success requires checking effective permissions, not only byte counts. This explains Storage Migration Service transfer and ACLs, for example: A legacy file server hosts millions of files with complex NTFS permissions that must survive migration. The decisive mechanism is that storage Migration Service inventories source server data and configurations to support staged file-server migration planning.
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 storage Migration Service inventories source server data and configurations to support staged file-server migration planning.
SMS cutover can preserve an expected client-facing server identity within supported conditions, separating data copy from service transition. This explains Storage Migration Service server cutover, for example: Clients still resolve the old file server name after successful data transfer to a replacement host. The decisive mechanism is that storage Migration Service inventories source server data and configurations to support staged file-server migration planning.
Please check your mailbox for a message from support@examlabs.com and follow the directions.