Pass Microsoft AZ-801 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Microsoft AZ-801 Practice Test 12
Question 110
At a Windows Server monitoring and incident engineering team, administrators find that A domain controller database becomes corrupt and normal boot cannot start directory services, requiring controlled authoritative recovery. The case is being investigated during a production overnight fault investigation. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?
Explanation
Correct Answer
Use Directory Services Restore Mode with validated system state backups and choose the documented authoritative or nonauthoritative restore method. AD DS disaster recovery requires selecting restore authority and protecting directory database consistency. At a Windows Server monitoring and incident engineering team, administrators find that A domain controller database becomes corrupt and normal boot cannot start directory services, requiring controlled authoritative recovery.
Incorrect Answers
“Repair effective Windows Update policy or approved Azure Update Manager orchestration after reviewing update source responsibilities” does not explain the observed failure: at a Windows Server monitoring and incident engineering team, administrators find that A domain controller database becomes corrupt and normal boot cannot start directory services, requiring controlled authoritative recovery. AD DS disaster recovery requires selecting restore authority and protecting directory database consistency. Use Directory Services Restore Mode with validated system state backups and choose the documented authoritative or nonauthoritative restore method.
Inspecting sync rules, connector space and export errors, then correct the specific source attribute mapping addresses a separate aspect of the case. At a Windows Server monitoring and incident engineering team, administrators find that A domain controller database becomes corrupt and normal boot cannot start directory services, requiring controlled authoritative recovery. Use Directory Services Restore Mode with validated system state backups and choose the documented authoritative or nonauthoritative restore method.
“Restore AD-integrated DNS replication and correct client DNS resolver assignment for the domain namespace” does not explain the observed failure: at a Windows Server monitoring and incident engineering team, administrators find that A domain controller database becomes corrupt and normal boot cannot start directory services, requiring controlled authoritative recovery. Use Directory Services Restore Mode with validated system state backups and choose the documented authoritative or nonauthoritative restore method.
Question 111
At a Windows Hyper-V replication operations unit, administrators find that Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity. The case is being investigated during an annual site outage simulation. Before implementing the proposed change (configure supported certificate-based Replica authentication, firewall port access and matching server names), which observed evidence most strongly substantiates the technical diagnosis?
Explanation
Correct Answer
Event logs show Replica authentication failed due to certificate identity or trust chain mismatch. Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust. At a Windows Hyper-V replication operations unit, administrators find that Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity.
Incorrect Answers
Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust. At a Windows Hyper-V replication operations unit, administrators find that Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity. The proposed action “Vault backup history shows a valid recovery point while the source VM resource is missing” would not resolve that situation. Event logs show Replica authentication failed due to certificate identity or trust chain mismatch.
The proposed step “Protection group membership shows only volume-level backup while database consistency checks remain absent” would leave the problem unresolved: at a Windows Hyper-V replication operations unit, administrators find that Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity. Event logs show Replica authentication failed due to certificate identity or trust chain mismatch.
“Replication health reports a stale configuration server or repeated agent authentication failure” does not explain the observed failure: at a Windows Hyper-V replication operations unit, administrators find that Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity. Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust. Event logs show Replica authentication failed due to certificate identity or trust chain mismatch.
Question 112
During a signed business continuity acceptance test for an Azure backup and recovery engineering team, administrators confirm that Engineers run Azure Site Recovery test failovers but leave temporary virtual machines consuming reserved IP addresses and cloud quotas. The solution must preserve other approved service dependencies. The administrators propose to apply controlled ASR test failover cleanup and verify resource tracking without deleting production protection. What measurable verification would demonstrate that the original failure has been corrected?
Explanation
Correct Answer
Test recovery resources are removed while protected replication health and genuine production VM state remain intact. The proposed intervention, apply controlled ASR test failover cleanup and verify resource tracking without deleting production protection, is justified on the engineering principle that failover rehearsal must end with safe environment cleanup and preserved disaster recovery capability. Engineers run Azure Site Recovery test failovers but leave temporary virtual machines consuming reserved IP addresses and cloud quotas.
Incorrect Answers
“Sustained healthy replication meets the recovery-point objective and a test failover reaches the authorized region” does not explain the observed failure: engineers run Azure Site Recovery test failovers but leave temporary virtual machines consuming reserved IP addresses and cloud quotas. Test recovery resources are removed while protected replication health and genuine production VM state remain intact.
Consistent recovery points resume and measured replication lag returns within the planned recovery-point objective. Addresses another workflow. Engineers run Azure Site Recovery test failovers but leave temporary virtual machines consuming reserved IP addresses and cloud quotas. Test recovery resources are removed while protected replication health and genuine production VM state remain intact.
Recovered application opens with validated transaction consistency and recorded recovery-point loss within RPO. Engineers run Azure Site Recovery test failovers but leave temporary virtual machines consuming reserved IP addresses and cloud quotas. Test recovery resources are removed while protected replication health and genuine production VM state remain intact.
Question 113
During a monthly compliance verification for a corporate Azure-hosted Windows Server operations unit, administrators confirm that Privileged domain administrators are exposed to credential relay because they routinely sign in to file servers with legacy authentication. The solution must preserve other approved service dependencies. The incident trace shows authentication telemetry shows privileged users successfully using NTLM to legacy hosts during administration. Which proposed action and matching validation would address the same root cause?
Explanation
Correct Answer
Migrate approved management workflows to Kerberos-capable services before placing eligible identities in Protected Users. Verify that validated privileged users can perform approved Kerberos administration and blocked legacy credential flows are recorded. Privileged identity protections must account for the protocols and credential caching restrictions imposed on protected accounts.
Incorrect Answers
Internet probes to the administrative port fail while approved management source addresses retain access. The required validation is different: validated privileged users can perform approved Kerberos administration and blocked legacy credential flows are recorded. Migrate approved management workflows to Kerberos-capable services before placing eligible identities in Protected Users.
The targeted Arc server reports correct coverage and its supported security posture findings appear without duplicate enrollment. It would not verify that validated privileged users can perform approved Kerberos administration and blocked legacy credential flows are recorded. Validated privileged users can perform approved Kerberos administration and blocked legacy credential flows are recorded.
Validated privileged users can perform approved Kerberos administration and blocked legacy credential flows are recorded. To correct the reported problem, migrate approved management workflows to Kerberos-capable services before placing eligible identities in Protected Users. Privileged identity protections must account for the protocols and credential caching restrictions imposed on protected accounts.
Question 114
During a change freeze and rollback planning meeting for a cross-domain infrastructure consolidation project, administrators confirm that A production VM is migrated to Azure and runs, but clients continue connecting to the original on-premises IP because DNS changes were not staged. The solution must preserve other approved service dependencies. The administrators propose to execute the validated Azure Migrate cutover and DNS/route transition plan with rollback checkpoints. What measurable verification would demonstrate that the original failure has been corrected?
Explanation
Correct Answer
Authenticated clients connect to the Azure application endpoint and the old location is safely made read-only. DNS changes were not staged, which was identified by source DNS records and client caches still point to the decommissioned on-premises address. A production VM is migrated to Azure and runs, but clients continue connecting to the original on-premises IP because DNS changes were not staged.
Incorrect Answers
Migration grouping includes the database dependency and a test wave preserves end-to-end application transactions. A production VM is migrated to Azure and runs, but clients continue connecting to the original on-premises IP because DNS changes were not staged. Authenticated clients connect to the Azure application endpoint and the old location is safely made read-only.
“The container starts, passes HTTP and dependency tests, and an image provenance scan succeeds” does not explain the observed failure: a production VM is migrated to Azure and runs, but clients continue connecting to the original on-premises IP because DNS changes were not staged. DNS changes were not staged, which was identified by source DNS records and client caches still point to the decommissioned on-premises address. Authenticated clients connect to the Azure application endpoint and the old location is safely made read-only.
Destination shares present expected files and effective SMB/NTFS permissions match the validated source inventory. A production VM is migrated to Azure and runs, but clients continue connecting to the original on-premises IP because DNS changes were not staged. Authenticated clients connect to the Azure application endpoint and the old location is safely made read-only.
Question 115
During a replication and authentication health review for an Active Directory hybrid troubleshooting group, administrators confirm that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity is appropriate?
Explanation
Correct Answer
Recovering an identity preserves authorization continuity that a same-name replacement object cannot reproduce. Applying restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity should then yield restored group retains its original SID and membership and access checks regain expected rights. Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information.
Incorrect Answers
VM extension health is an agent and handler execution question independent of RDP connectivity. Addresses another workflow. Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. Recovering an identity preserves authorization continuity that a same-name replacement object cannot reproduce.
Hybrid identity troubleshooting must preserve immutable identity mapping and diagnose attribute flow before re-creating accounts. Applying restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity should then yield restored group retains its original SID and membership and access checks regain expected rights. Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. Recovering an identity preserves authorization continuity that a same-name replacement object cannot reproduce.
Hybrid agent connection does not guarantee authorization and connectivity for each Arc extension operation. Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. Recovering an identity preserves authorization continuity that a same-name replacement object cannot reproduce.
Question 116
At a regulated Windows Server hybrid identity environment, administrators find that An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller. The case is being investigated during a privileged-access audit. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?
Explanation
Correct Answer
Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement. Untested protocol removal can interrupt dependent applications; the intended key must still be technically verified against supported product behavior. At a regulated Windows Server hybrid identity environment, administrators find that An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller.
Incorrect Answers
Replacing the broad inbound exception with service-scoped source-restricted rules and validate GPO precedence addresses a separate aspect of the case. At a regulated Windows Server hybrid identity environment, administrators find that An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller. Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement.
“Tighten RODC Password Replication Policy and revoke inappropriate cached privileged identities” concerns a different part of the problem. At a regulated Windows Server hybrid identity environment, administrators find that An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller. Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement.
Untested protocol removal can interrupt dependent applications; the intended key must still be technically verified against supported product behavior. At a regulated Windows Server hybrid identity environment, administrators find that An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller. The proposed action “Associate the Arc resource to the correct subscription, resource group and policy assignment scopes, then verify evaluation” would not resolve that situation. Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement.
Question 117
During an annual site outage simulation for a Windows Hyper-V replication operations unit, administrators confirm that A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to use the Hyper-V Replica Broker clustered client access point instead of a node-specific replication endpoint is appropriate?
Explanation
Correct Answer
A clustered replication endpoint must use a role identity that follows protected workloads across nodes. The target points to one host name, produces the distinctive clue replication metadata references one former cluster node and errors occur after a legitimate role move. A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name.
Incorrect Answers
“ASR readiness requires healthy source-side replication agents and target-service connectivity” does not explain the observed failure: a replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. The target points to one host name, produces the distinctive clue replication metadata references one former cluster node and errors occur after a legitimate role move. A clustered replication endpoint must use a role identity that follows protected workloads across nodes.
Replication policies must be measured against recovery requirements rather than relying on a generic protected badge. A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. A clustered replication endpoint must use a role identity that follows protected workloads across nodes.
“Recovery orchestration must represent service dependencies rather than merely powering on VM replicas” does not explain the observed failure: a replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. A clustered replication endpoint must use a role identity that follows protected workloads across nodes.
Question 118
At an Azure Arc and Windows Server fleet operations team, administrators find that Performance Monitor counters are configured interactively but no long-term Data Collector Set exists to capture overnight application stalls. The case is being investigated during a critical-service alert and telemetry test. Which system engineering principle most directly explains why the remedy to create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions is appropriate?
Explanation
Correct Answer
Repeatable performance diagnosis depends on persistent sampling and bounded collection storage. Applying create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions should then yield the scheduled collection captures a deliberately induced slowdown with timestamps and disk limits enforced. Occurred after operators closed PerfMon.
Incorrect Answers
Applying create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions should then yield the scheduled collection captures a deliberately induced slowdown with timestamps and disk limits enforced. Occurred after operators closed PerfMon. The proposed action “Agent installation and rule-to-resource association are distinct requirements for Azure Monitor ingestion” would not resolve that situation. Repeatable performance diagnosis depends on persistent sampling and bounded collection storage.
The proposed step “Management portal registration is separate from actual actionable monitoring and alert configuration” would leave the problem unresolved: occurred after operators closed PerfMon. Repeatable performance diagnosis depends on persistent sampling and bounded collection storage.
SYSVOL file replication is a separate health dependency from Active Directory database replication. Occurred after operators closed PerfMon. Repeatable performance diagnosis depends on persistent sampling and bounded collection storage.
Question 119
At a corporate Azure-hosted Windows Server operations unit, administrators find that Domain controllers stop providing meaningful identity attack telemetry even though the cloud Defender for Identity portal still lists the environment. The case is being investigated during a monthly compliance verification. The incident trace shows identity sensor health records show a disconnected sensor and no recent identity events for an active controller. Which proposed action and matching validation would address the same root cause?
Explanation
Correct Answer
Check sensor version, service health, network connectivity and identity permissions on affected domain controllers. Verify that a safe lab identity-threat fixture is detected after sensor health and event ingestion return to normal. A mismatched action or mismatched verification does not establish this result. Identity sensor health records show a disconnected sensor and no recent identity events for an active controller.
Incorrect Answers
A tested protected recovery workflow uses the new escrowed protector and old material is invalidated afterwards. It would not verify that a safe lab identity-threat fixture is detected after sensor health and event ingestion return to normal. Identity sensor health records show a disconnected sensor and no recent identity events for an active controller.
Validated privileged users can perform approved Kerberos administration and blocked legacy credential flows are recorded. The required validation is different: a safe lab identity-threat fixture is detected after sensor health and event ingestion return to normal. Check sensor version, service health, network connectivity and identity permissions on affected domain controllers.
A safe lab identity-threat fixture is detected after sensor health and event ingestion return to normal. To correct the reported problem, check sensor version, service health, network connectivity and identity permissions on affected domain controllers. A mismatched action or mismatched verification does not establish this result.
Question 120
During a change freeze and rollback planning meeting for a cross-domain infrastructure consolidation project, administrators confirm that An IIS application migrated into Azure App Service starts but fails outbound database access because connection strings and managed identity are not configured. The solution must preserve other approved service dependencies. The administrators propose to map application settings and database access to approved App Service configuration with secret custody and identity permissions. What measurable verification would demonstrate that the original failure has been corrected?
Explanation
Correct Answer
Authenticated application requests reach the database without publishing connection secrets into deployment files. Connection strings and managed identity are not configured; the pre-change evidence is App Service diagnostics show missing environment settings and rejected managed database authentication.
Incorrect Answers
“The destination VM starts with consistent checkpoints and all expected virtual disks available” does not demonstrate what is needed when app Service diagnostics show missing environment settings and rejected managed database authentication. Authenticated application requests reach the database without publishing connection secrets into deployment files.
“Migration grouping includes the database dependency and a test wave preserves end-to-end application transactions” does not explain the observed failure: app Service diagnostics show missing environment settings and rejected managed database authentication. Authenticated application requests reach the database without publishing connection secrets into deployment files.
“Clients renew from only the approved replacement server and receive the exact expected network options” concerns a different part of the problem. App Service diagnostics show missing environment settings and rejected managed database authentication. Authenticated application requests reach the database without publishing connection secrets into deployment files.
Configuring Windows Server Hybrid Advanced Services (AZ-801) Practice Tests
- Microsoft AZ-801 Practice Test 10 - 10 Questions (Last Reviewed 09-Nov-2026)
- Microsoft AZ-801 Practice Test 11 - 10 Questions (Last Reviewed 08-Nov-2026)
- Microsoft AZ-801 Practice Test 12 - 10 Questions (Last Reviewed 07-Nov-2026)
- Microsoft AZ-801 Practice Test 13 - 10 Questions (Last Reviewed 06-Nov-2026)
- Microsoft AZ-801 Practice Test 14 - 10 Questions (Last Reviewed 05-Nov-2026)
