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 highly privileged AD account is being used on general-purpose member servers outside the administration tier.
Which acceptance result most directly demonstrates a working configuration?
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: A highly privileged AD account is being used on general-purpose member servers outside the administration tier. 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: A highly privileged AD account is being used on general-purpose member servers outside the administration tier. 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: A highly privileged AD account is being used on general-purpose member servers outside the administration tier. 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: A highly privileged AD account is being used on general-purpose member servers outside the administration tier. 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.
A Windows Server can ping its default gateway but cannot reach a remote TCP service across the WAN.
Which configuration change best addresses this specific requirement?
Use layered Windows TCP/IP diagnostics for routes, DNS, firewall rules and target TCP connectivity before changing the application. This addresses the stated situation: A Windows Server can ping its default gateway but cannot reach a remote TCP service across the WAN. IP reachability to one hop does not demonstrate end-to-end name resolution, routing or application port access. Confirm the outcome by checking that tests isolate the failed network hop or port and the intended remote service accepts authorized connections after correction. If the control is skipped, restarting application services without diagnosing packet path failures can prolong downtime and obscure the root cause.
Inspect Windows Update logs, servicing stack health, policy source and component-store integrity before rerunning patches. This is more relevant to Windows Update servicing failures, such as when security patches fail repeatedly on Windows Server even though clients can reach their configured update endpoint. Windows servicing requires healthy component metadata and a functional update source; retries alone do not fix corruption. The appropriate action here is to use layered Windows TCP/IP diagnostics for routes, DNS, firewall rules and target TCP connectivity before changing the application.
Inspect DNS client settings, authoritative records, cache and conditional forwarding before altering file-share permissions. This is more relevant to DNS client and server resolution, such as when a Windows file server is reachable by IP address but fails when clients use the configured host name. Name resolution maps service names to addresses and depends on correct DNS zone data and cache behavior. The appropriate action here is to use layered Windows TCP/IP diagnostics for routes, DNS, firewall rules and target TCP connectivity before changing the application.
Inspect Windows Time Service hierarchy, source peers and synchronization status, then correct the responsible time configuration. This is more relevant to Windows Time synchronization failures, such as when kerberos logons fail intermittently because a domain member's clock differs significantly from its domain controller. Kerberos authentication and distributed logs depend on reasonably synchronized clocks; inconsistent time can cause ticket validation failures. The appropriate action here is to use layered Windows TCP/IP diagnostics for routes, DNS, firewall rules and target TCP connectivity before changing the application.
A domain modernization team must locate legacy NTLM consumers before disabling weaker authentication.
Which explanation most directly supports the appropriate decision?
NTLM audit events reveal remaining consumers; staged restrictions avoid assuming all applications already support Kerberos. This mechanism is relevant because a domain modernization team must locate legacy NTLM consumers before disabling weaker authentication. The administrator should enable relevant NTLM auditing, identify dependencies, remediate application configuration, and enforce restrictions in phases. Validate the decision by confirming that events show expected legacy usage has been remediated before restrictions, and target logons continue using supported mechanisms.
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 NTLM audit events reveal remaining consumers; staged restrictions avoid assuming all applications already support Kerberos.
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 NTLM audit events reveal remaining consumers; staged restrictions avoid assuming all applications already support Kerberos.
Defender for Identity analyzes identity-related network and directory signals to identify suspicious activities in on-premises AD environments. This explains Defender for Identity directory sensors, for example: Security analysts need to detect suspicious AD reconnaissance and lateral-movement activity around domain controllers. The decisive mechanism is that NTLM audit events reveal remaining consumers; staged restrictions avoid assuming all applications already support Kerberos.
A domain modernization team must locate legacy NTLM consumers before disabling weaker authentication.
What is the most direct consequence of leaving this problem unresolved?
Disabling NTLM everywhere without inventorying dependencies can interrupt legacy services and create an unplanned outage. This is the direct risk of the described condition: 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 corrective approach is to enable relevant NTLM auditing, identify dependencies, remediate application configuration, and enforce restrictions in phases.
Using group membership alone without restricting privileged logon destinations leaves the account exposed on untrusted hosts. This is a risk associated with Authentication policy silos, such as when tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. For this case, the main exposure is that disabling NTLM everywhere without inventorying dependencies can interrupt legacy services and create an unplanned outage.
Treating domain controllers as generic member servers exposes the central identity infrastructure to avoidable attack paths. This is a risk associated with Domain controller hardening, such as when a new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions. For this case, the main exposure is that disabling NTLM everywhere without inventorying dependencies can interrupt legacy services and create an unplanned outage.
Installing generic host monitoring without identity-specific telemetry can leave credential and directory attack behaviors undetected. This is a risk associated with Defender for Identity directory sensors, such as when security analysts need to detect suspicious AD reconnaissance and lateral-movement activity around domain controllers. For this case, the main exposure is that disabling NTLM everywhere without inventorying dependencies can interrupt legacy services and create an unplanned outage.
Help-desk technicians must reset passwords in one organizational unit without changing privileged domain groups.
Which adverse outcome best describes the untreated issue?
Using Domain Admins membership for routine help-desk work increases privilege exposure and audit complexity. This is the direct risk of the described condition: Help-desk technicians must reset passwords in one organizational unit without changing privileged domain groups. Delegated directory ACLs grant specific object actions within a scope; domain-wide administrative groups grant unnecessarily broad control. The corrective approach is to delegate narrowly scoped AD DS permissions on the intended OU and review membership in privileged built-in groups.
Treating domain controllers as generic member servers exposes the central identity infrastructure to avoidable attack paths. This is a risk associated with Domain controller hardening, such as when a new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions. For this case, the main exposure is that using Domain Admins membership for routine help-desk work increases privilege exposure and audit complexity.
Installing generic host monitoring without identity-specific telemetry can leave credential and directory attack behaviors undetected. This is a risk associated with Defender for Identity directory sensors, such as when security analysts need to detect suspicious AD reconnaissance and lateral-movement activity around domain controllers. For this case, the main exposure is that using Domain Admins membership for routine help-desk work increases privilege exposure and audit complexity.
Disabling NTLM everywhere without inventorying dependencies can interrupt legacy services and create an unplanned outage. This is a risk associated with NTLM auditing and phased restriction, such as when a domain modernization team must locate legacy NTLM consumers before disabling weaker authentication. For this case, the main exposure is that using Domain Admins membership for routine help-desk work increases privilege exposure and audit complexity.
A verified on-premises Windows Server VM must be migrated to Azure with a controlled application cutover.
What is the most directly justified remediation?
Use a supported Azure Migrate server migration workflow to replicate, test migrate and execute the cutover. This addresses the stated situation: A verified on-premises Windows Server VM must be migrated to Azure with a controlled application cutover. Azure Migrate migration coordinates replication and target VM creation; test migration helps validate network and service behavior before committing. Confirm the outcome by checking that a test-migrated VM functions on the intended Azure network and the final cutover meets the agreed data freshness and service objectives. If the control is skipped, skipping the test migration can reveal incompatible networking or application prerequisites only during the production cutover.
Deploy a supported Azure Migrate discovery appliance and collect sufficient performance and dependency data for assessment. This is more relevant to Azure Migrate discovery appliance, such as when an organization plans to migrate VMware VMs but lacks inventory data about dependencies and utilization. Azure Migrate discovery and assessment uses inventory and utilization evidence to inform sizing, readiness and cost recommendations. The appropriate action here is to use a supported Azure Migrate server migration workflow to replicate, test migrate and execute the cutover.
Use a supported Azure Migrate physical-server migration or agent-based approach with the correct source prerequisites. This is more relevant to Azure Migrate physical servers, such as when 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 appropriate action here is to use a supported Azure Migrate server migration workflow to replicate, test migrate and execute the cutover.
Review Azure Migrate readiness, observed performance, software compatibility and cost recommendations before selecting VM sizes. This is more relevant to Azure VM readiness and right-sizing, such as when a legacy application runs on an oversized source VM but the migration team has no throughput or memory baseline. Azure workload sizing depends on actual demand and supported target capabilities rather than simply preserving source hardware dimensions. The appropriate action here is to use a supported Azure Migrate server migration workflow to replicate, test migrate and execute the cutover.
Operations want to copy departmental data to a modern Windows Server without losing share configuration.
Which acceptance result most directly demonstrates a working configuration?
Destination files and share ACL tests match the expected source access for authorized and unauthorized users. This specifically verifies the case: Operations want to copy departmental data to a modern Windows Server without losing share configuration. SMS coordinates transfer of file data and supported configuration; migration success requires checking effective permissions, not only byte counts. The matching action is to configure a Storage Migration Service transfer job that preserves required data, shares and security settings, then validate results.
A controlled cutover shows clients reaching migrated shares through the planned name while the legacy server is safely removed. This would validate Storage Migration Service server cutover, as in this different situation: Clients still resolve the old file server name after successful data transfer to a replacement host. It is not the most direct evidence for the case: Operations want to copy departmental data to a modern Windows Server without losing share configuration. Here, successful verification means that destination files and share ACL tests match the expected source access for authorized and unauthorized users.
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: Operations want to copy departmental data to a modern Windows Server without losing share configuration. Here, successful verification means that destination files and share ACL tests match the expected source access for authorized and unauthorized users.
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: Operations want to copy departmental data to a modern Windows Server without losing share configuration. Here, successful verification means that destination files and share ACL tests match the expected source access for authorized and unauthorized users.
A remote workforce uses older RDS session hosts and needs a staged migration without invalidating licensing assumptions.
What is the most direct consequence of leaving this problem unresolved?
Replacing session hosts without checking brokers and licensing can deny users remote application access. This is the direct risk of the described condition: A remote workforce uses older RDS session hosts and needs a staged migration without invalidating licensing assumptions. RDS session access depends on the coordinated deployment roles and user session configuration, not merely one host's OS image. The corrective approach is to plan supported RDS role and session-host migration with licensing, connection broker and application compatibility checks.
Assuming live migration works across all CPU and Windows version combinations can cause service interruption. This is a risk associated with Hyper-V host replacement, such as when a company wants to move running VMs from legacy Hyper-V hosts to new Windows Server virtualization hardware. For this case, the main exposure is that replacing session hosts without checking brokers and licensing can deny users remote application access.
Moving only the printer name without driver and port configuration can leave end-user printing unavailable. This is a risk associated with Print server migration, such as when an office has hundreds of printer queues tied to a Windows Server scheduled for decommissioning. For this case, the main exposure is that replacing session hosts without checking brokers and licensing can deny users remote application access.
Turning on a new server with overlapping scopes before disabling the old one can issue conflicting leases. This is a risk associated with DHCP migration with leases and options, such as when a new Windows Server will replace a legacy DHCP server serving multiple network scopes. For this case, the main exposure is that replacing session hosts without checking brokers and licensing can deny users remote application access.
A virtualization cluster is being refreshed and planners need to preserve guest availability during host migration.
What technical distinction explains the intended control?
Hyper-V migration methods have distinct availability, storage and compatibility requirements; an unsupported live move may fail. This mechanism is relevant because a virtualization cluster is being refreshed and planners need to preserve guest availability during host migration. The administrator should choose supported Hyper-V live migration, storage migration or export/import according to CPU, version and storage compatibility. Validate the decision by confirming that a test guest starts and retains its data, identity and network configuration on the approved destination host.
DHCP continuity relies on valid scopes, reservations, options and directory authorization where required. This explains DHCP migration with leases and options, for example: A new Windows Server will replace a legacy DHCP server serving multiple network scopes. The decisive mechanism is that Hyper-V migration methods have distinct availability, storage and compatibility requirements; an unsupported live move may fail.
Print workloads depend on queue definitions, printer drivers, ports and sharing configuration beyond spool data. This explains Print server migration, for example: An office has hundreds of printer queues tied to a Windows Server scheduled for decommissioning. The decisive mechanism is that Hyper-V migration methods have distinct availability, storage and compatibility requirements; an unsupported live move may fail.
RDS session access depends on the coordinated deployment roles and user session configuration, not merely one host's OS image. This explains Remote Desktop Services session host migration, for example: A legacy RDS deployment must replace its session hosts while retaining user access and application behavior. The decisive mechanism is that Hyper-V migration methods have distinct availability, storage and compatibility requirements; an unsupported live move may fail.
Tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers.
What could most specifically go wrong without the correct mitigation?
Using group membership alone without restricting privileged logon destinations leaves the account exposed on untrusted hosts. This is the direct risk of the described condition: 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 corrective approach is to design and enforce supported AD authentication policies and authentication policy silos for the privileged identities and eligible hosts.
Overbroad password caching on an RODC can expose privileged credentials when the branch server is compromised. This is a risk associated with 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. For this case, the main exposure is that using group membership alone without restricting privileged logon destinations leaves the account exposed on untrusted hosts.
Adding incompatible service identities blindly can disrupt logons while omitting eligible privileged accounts leaves weaker credential handling. This is a risk associated with Protected Users account group, such as when tier-zero administrator credentials must not be exposed through legacy NTLM authentication on member machines. For this case, the main exposure is that using group membership alone without restricting privileged logon destinations leaves the account exposed on untrusted hosts.
Treating domain controllers as generic member servers exposes the central identity infrastructure to avoidable attack paths. This is a risk associated with Domain controller hardening, such as when a new domain controller was deployed with unnecessary services and no clearly documented inbound management restrictions. For this case, the main exposure is that using group membership alone without restricting privileged logon destinations leaves the account exposed on untrusted hosts.
A regional datacenter needs the same banned-password policy for on-premises password changes as cloud accounts.
What risk should be highlighted in the change assessment?
Installing only the cloud policy without functional DC agents leaves local AD password changes outside the intended protection. This is the direct risk of the described condition: A regional datacenter needs the same banned-password policy for on-premises password changes as cloud accounts. Password Protection DC agents evaluate password changes in AD DS against the synchronized banned-password policy; proxy services support policy distribution. The corrective approach is to deploy Microsoft Entra Password Protection proxy and DC agents, configure global and custom banned passwords, and test enforcement.
Using group membership alone without restricting privileged logon destinations leaves the account exposed on untrusted hosts. This is a risk associated with Authentication policy silos, such as when tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. For this case, the main exposure is that installing only the cloud policy without functional DC agents leaves local AD password changes outside the intended protection.
Overbroad password caching on an RODC can expose privileged credentials when the branch server is compromised. This is a risk associated with 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. For this case, the main exposure is that installing only the cloud policy without functional DC agents leaves local AD password changes outside the intended protection.
Adding incompatible service identities blindly can disrupt logons while omitting eligible privileged accounts leaves weaker credential handling. This is a risk associated with Protected Users account group, such as when tier-zero administrator credentials must not be exposed through legacy NTLM authentication on member machines. For this case, the main exposure is that installing only the cloud policy without functional DC agents leaves local AD password changes outside the intended protection.
Please check your mailbox for a message from support@examlabs.com and follow the directions.