100% Latest & Updated Microsoft AZ-801 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 360
The recovery team validates a restored VM only by checking that the Azure resource is in Running state. Which implementation step directly corrects the underlying problem?
- Correct network interface, routes, security rules and application bindings on the restored instance.
- Run guest OS, application, data-integrity and network service validation before marking recovery successful.
- Run a complete restore drill and measure storage recovery, boot, networking and application health.
- Select and validate a recovery point before the deletion event.
Explanation
Correct Answer
B:Azure platform VM power state does not prove functional workload recovery. A suitable corrective action is to run guest OS, application, data-integrity and network service validation before marking recovery successful.
Incorrect Answers
A:A recovered disk does not automatically recreate appropriate target-network connectivity. However, Azure platform VM power state does not prove functional workload recovery.
C:Snapshot availability is not equivalent to an end-to-end service recovery-time guarantee. In this situation, Azure platform VM power state does not prove functional workload recovery.
D:Recovery point timestamps determine available historical data and must precede the undesired change. However, Azure platform VM power state does not prove functional workload recovery.
Question 361
An Azure VM must be recoverable in a second region but the team enabled only Azure Backup in its local vault. What change should be prioritized to restore the intended behavior?
- Verify supported target region, compute SKU, disk and encryption compatibility before enabling ASR.
- Deploy the supported on-premises ASR replication components and register them with the recovery vault.
- Configure Azure Site Recovery replication to the designated secondary region.
- Wait for initial synchronization and a healthy recovery point before treating the VM as protected.
Explanation
Correct Answer
C:Point-in-time backup and continuously maintained disaster-recovery replicas serve different recovery objectives. The targeted remedy is to configure Azure Site Recovery replication to the designated secondary region.
Incorrect Answers
A:Disaster recovery can fail even with healthy replication if target resources cannot be provisioned. Here, point-in-time backup and continuously maintained disaster-recovery replicas serve different recovery objectives.
B:Protecting a physical source requires supported replication infrastructure, not merely an Azure target VM. In this situation, point-in-time backup and continuously maintained disaster-recovery replicas serve different recovery objectives.
D:Replication enrollment is not equivalent to a usable synchronized recovery point. Here, point-in-time backup and continuously maintained disaster-recovery replicas serve different recovery objectives.
Question 362
An ASR-protected VM's recovery point objective rises above the approved limit after outbound replication traffic is throttled. Which configuration or recovery action best matches this evidence?
- Measure source data change rate and network/replication throughput, then address the actual bottleneck.
- Retain point-in-time backup and application consistency controls in addition to ASR replication.
- Adjust supported ASR recovery-point retention and validate resulting stored recovery points.
- Restore appropriate replication throughput and inspect backlog rather than tuning a backup schedule.
Explanation
Correct Answer
D:Restore appropriate replication throughput and inspect backlog rather than tuning a backup schedule. This addresses the condition because replication lag responds to transport capacity and change rate, not unrelated scheduled backups.
Incorrect Answers
A:Recovery point objectives can be missed when writes outpace achievable replication bandwidth. In this situation, replication lag responds to transport capacity and change rate, not unrelated scheduled backups.
B:Replication can faithfully copy corrupted data and does not replace historical backup. However, replication lag responds to transport capacity and change rate, not unrelated scheduled backups.
C:Recovery point history is constrained by replication policy and available retained data. Here, replication lag responds to transport capacity and change rate, not unrelated scheduled backups.
Question 363
A physical Windows Server in a local datacenter is expected to replicate to Azure, but no Site Recovery mobility service/components are installed. Which administrative change most directly resolves the documented failure?
- Deploy the supported on-premises ASR replication components and register them with the recovery vault.
- Specify and validate target network mappings as part of ASR replication configuration.
- Retain point-in-time backup and application consistency controls in addition to ASR replication.
- Adjust supported ASR recovery-point retention and validate resulting stored recovery points.
Explanation
Correct Answer
A:Protecting a physical source requires supported replication infrastructure, not merely an Azure target VM. For that reason, deploy the supported on-premises ASR replication components and register them with the recovery vault.
Incorrect Answers
B:Replicated disk state and target virtual network placement are independent configurations. Here, protecting a physical source requires supported replication infrastructure, not merely an Azure target VM.
C:Replication can faithfully copy corrupted data and does not replace historical backup. In this situation, protecting a physical source requires supported replication infrastructure, not merely an Azure target VM.
D:Recovery point history is constrained by replication policy and available retained data. However, protecting a physical source requires supported replication infrastructure, not merely an Azure target VM.
Question 364
The ASR vault exists in one subscription but operators attempt to register a source VM using credentials scoped to a different vault. Which supported action should be taken for this reported condition?
- Wait for initial synchronization and a healthy recovery point before treating the VM as protected.
- Correct vault registration/identity scope and verify protected source association.
- Specify and validate target network mappings as part of ASR replication configuration.
- Measure source data change rate and network/replication throughput, then address the actual bottleneck.
Explanation
Correct Answer
B:Correct vault registration/identity scope and verify protected source association. The underlying technical reason is that source appliance and replication provider registrations are tied to an intended Recovery Services vault.
Incorrect Answers
A:Replication enrollment is not equivalent to a usable synchronized recovery point. Here, source appliance and replication provider registrations are tied to an intended Recovery Services vault.
C:Replicated disk state and target virtual network placement are independent configurations. However, source appliance and replication provider registrations are tied to an intended Recovery Services vault.
D:Recovery point objectives can be missed when writes outpace achievable replication bandwidth. Here, source appliance and replication provider registrations are tied to an intended Recovery Services vault.
Question 365
A replication policy uses recovery point retention shorter than the business's documented rollback window. Which supported action should be taken for this reported condition?
- Wait for initial synchronization and a healthy recovery point before treating the VM as protected.
- Retain point-in-time backup and application consistency controls in addition to ASR replication.
- Adjust supported ASR recovery-point retention and validate resulting stored recovery points.
- Deploy the supported on-premises ASR replication components and register them with the recovery vault.
Explanation
Correct Answer
C:Recovery point history is constrained by replication policy and available retained data. A suitable corrective action is to adjust supported ASR recovery-point retention and validate resulting stored recovery points.
Incorrect Answers
A:Replication enrollment is not equivalent to a usable synchronized recovery point. In this situation, recovery point history is constrained by replication policy and available retained data.
B:Replication can faithfully copy corrupted data and does not replace historical backup. However, recovery point history is constrained by replication policy and available retained data.
D:Protecting a physical source requires supported replication infrastructure, not merely an Azure target VM. In this situation, recovery point history is constrained by replication policy and available retained data.
Question 366
A VM has recently enabled ASR but initial replication has not completed, yet the team plans immediate production failover. What would be the most defensible next action based on the observed symptoms?
- Adjust supported ASR recovery-point retention and validate resulting stored recovery points.
- Retain point-in-time backup and application consistency controls in addition to ASR replication.
- Correct vault registration/identity scope and verify protected source association.
- Wait for initial synchronization and a healthy recovery point before treating the VM as protected.
Explanation
Correct Answer
D:Replication enrollment is not equivalent to a usable synchronized recovery point. The targeted remedy is to wait for initial synchronization and a healthy recovery point before treating the VM as protected.
Incorrect Answers
A:Recovery point history is constrained by replication policy and available retained data. However, replication enrollment is not equivalent to a usable synchronized recovery point.
B:Replication can faithfully copy corrupted data and does not replace historical backup. Here, replication enrollment is not equivalent to a usable synchronized recovery point.
C:Source appliance and replication provider registrations are tied to an intended Recovery Services vault. In this situation, replication enrollment is not equivalent to a usable synchronized recovery point.
Question 367
A workload's nightly write spike makes ASR protection repeatedly fall behind while the target region is healthy. Which supported action should be taken for this reported condition?
- Measure source data change rate and network/replication throughput, then address the actual bottleneck.
- Restore appropriate replication throughput and inspect backlog rather than tuning a backup schedule.
- Specify and validate target network mappings as part of ASR replication configuration.
- Configure Azure Site Recovery replication to the designated secondary region.
Explanation
Correct Answer
A:Measure source data change rate and network/replication throughput, then address the actual bottleneck. This addresses the condition because recovery point objectives can be missed when writes outpace achievable replication bandwidth.
Incorrect Answers
B:Replication lag responds to transport capacity and change rate, not unrelated scheduled backups. In this situation, recovery point objectives can be missed when writes outpace achievable replication bandwidth.
C:Replicated disk state and target virtual network placement are independent configurations. However, recovery point objectives can be missed when writes outpace achievable replication bandwidth.
D:Point-in-time backup and continuously maintained disaster-recovery replicas serve different recovery objectives. Here, recovery point objectives can be missed when writes outpace achievable replication bandwidth.
Question 368
A planned DR design chooses a region unavailable for the workload's VM size and encrypted disk configuration. Which Windows Server or Azure operation best addresses the reported fault?
- Specify and validate target network mappings as part of ASR replication configuration.
- Verify supported target region, compute SKU, disk and encryption compatibility before enabling ASR.
- Configure Azure Site Recovery replication to the designated secondary region.
- Deploy the supported on-premises ASR replication components and register them with the recovery vault.
Explanation
Correct Answer
B:Disaster recovery can fail even with healthy replication if target resources cannot be provisioned. For that reason, verify supported target region, compute SKU, disk and encryption compatibility before enabling ASR.
Incorrect Answers
A:Replicated disk state and target virtual network placement are independent configurations. In this situation, disaster recovery can fail even with healthy replication if target resources cannot be provisioned.
C:Point-in-time backup and continuously maintained disaster-recovery replicas serve different recovery objectives. Here, disaster recovery can fail even with healthy replication if target resources cannot be provisioned.
D:Protecting a physical source requires supported replication infrastructure, not merely an Azure target VM. In this situation, disaster recovery can fail even with healthy replication if target resources cannot be provisioned.
Question 369
A source VM's NIC mapping is not configured, and a test failover creates a replica in an unintended network. Which supported action should be taken for this reported condition?
- Deploy the supported on-premises ASR replication components and register them with the recovery vault.
- Retain point-in-time backup and application consistency controls in addition to ASR replication.
- Specify and validate target network mappings as part of ASR replication configuration.
- Verify supported target region, compute SKU, disk and encryption compatibility before enabling ASR.
Explanation
Correct Answer
C:Specify and validate target network mappings as part of ASR replication configuration. The underlying technical reason is that replicated disk state and target virtual network placement are independent configurations.
Incorrect Answers
A:Protecting a physical source requires supported replication infrastructure, not merely an Azure target VM. However, replicated disk state and target virtual network placement are independent configurations.
B:Replication can faithfully copy corrupted data and does not replace historical backup. Here, replicated disk state and target virtual network placement are independent configurations.
D:Disaster recovery can fail even with healthy replication if target resources cannot be provisioned. However, replicated disk state and target virtual network placement are independent configurations.
Question 370
An operator assumes ASR replication automatically protects a database application against logical corruption occurring before replication. What should the administrator change first to correct this specific issue?
- Specify and validate target network mappings as part of ASR replication configuration.
- Deploy the supported on-premises ASR replication components and register them with the recovery vault.
- Adjust supported ASR recovery-point retention and validate resulting stored recovery points.
- Retain point-in-time backup and application consistency controls in addition to ASR replication.
Explanation
Correct Answer
D:Replication can faithfully copy corrupted data and does not replace historical backup. A suitable corrective action is to retain point-in-time backup and application consistency controls in addition to ASR replication.
Incorrect Answers
A:Replicated disk state and target virtual network placement are independent configurations. Here, replication can faithfully copy corrupted data and does not replace historical backup.
B:Protecting a physical source requires supported replication infrastructure, not merely an Azure target VM. In this situation, replication can faithfully copy corrupted data and does not replace historical backup.
C:Recovery point history is constrained by replication policy and available retained data. However, replication can faithfully copy corrupted data and does not replace historical backup.
Configuring Windows Server Hybrid Advanced Services (AZ-801) Practice Tests