An organization uses a Recovery Plan to protect a SQL Cluster that relies on Volume Groups (VGs). The VGs are configured with hypervisor attachments. The administrator executes a Planned Failover to migrate the SQL Cluster to the Recovery Site.
The Failover task completes successfully, but the database administrators report that the database is offline.
What is the possible cause of this issue?

• A. An administrator failed to configure mapping for the Storage Network in the Recovery Plan.
• B. VGs cannot be protected by Recovery Plans.
• C. An administrator failed to configure Protection Domains replication.
• D. VGs configured with hypervisor attachments do not reattach automatically after recovery.

An administrator has set up asynchronous replication between the Marseille and Paris clusters for the VMs in the FIN-PROD storage container. After a planned production failover from Paris to Marseille, the administrator noticed that the VMs were scattered across all the storage containers in the Marseille cluster.
Which statement is true regarding this scenario?

• A. The recovery plan did not contain a valid network mapping.
• B. A storage policy is setup on the Paris cluster and missing on the Marseille cluster.
• C. The FIN-PROD storage container does not exist on Marseille cluster.
• D. The recovery plan did not contain a valid storage mapping.

An administrator is managing a Nutanix environment via Prism Central and has two VMs running on AHV:
"ERP-PROD": A mission-critical VM protected by a Synchronous replication schedule (0 RPO) to a secondary site.
"REPORTING-DEV": A non-critical VM protected by an Asynchronous replication schedule (hourly RPO) to the same secondary site.
Following a corrupted application update, the administrator decides to manually recover both VMs locally.
What will be the outcome of this manual recovery attempt?

• A. The "Revert" operation will succeed for both VMs, but for "ERP-PROD", the administrator needs to temporarily break the synchronous replication link before the snapshot can be applied.
• B. The "Revert" operation will succeed for "REPORTING-DEV", but the option will be unavailable or blocked for "ERP-PROD".
• C. The "Revert" operation will succeed for "ERP-PROD" because synchronous replication natively locks the metadata, but it will fail for "REPORTING-DEV".
• D. The "Revert" operation will fail for both VMs.

During the Recovery Plan configuration, the administrator maps the "Test Network" setting to the "Production Network" VLAN on the Recovery Site.
What is the expected outcome when the administrator executes a Test Failover for this plan?

• A. The Test VMs will turn on, but will be isolated from all other network traffic automatically.
• B. The Test VMs will start, causing IP address conflicts with the live production VMs on the Primary Site.
• C. The Test VMs will remain turned off, maintaining isolation from all other network traffic automatically.
• D. The Test Failover will fail the validation check because the production network is already in use.

An administrator has recently completed the initial configuration of Nutanix Disaster Recovery for a production environment. Protection Policies and Recovery Plans have been configured and validated by the senior infrastructure team.
The administrator has confirmed that the expected categories are correctly associated with both the Protection Policies and Recovery Plans. During a scheduled test failover, the administrator notices that several VMs are missing from the recovery.
The administrator reviews the environment and notes the following:
The Protection Summary tab does not show any warnings or errors
No replication tasks are currently ongoing
The missing VMs were all deployed within the last two weeks as part of a new application rollout The missing VMs are running on the same cluster as other VMs that recovered successfully during the test failover The application team followed the standard VM deployment checklist but did not coordinate with the infrastructure team during provisioning Given this information, what is the most likely cause of the missing VMs?

• A. The Recovery Plans were not re-synchronized after the new VMs were deployed, causing them to be excluded from the test failover.
• B. The newly deployed VMs were not assigned the correct categories during provisioning, so they were never included in the Protection Policy.
• C. The Protection Policies experienced replication lag during the two-week period, resulting in incomplete recovery points for the newly deployed VMs.
• D. The new VMs require an initial full replication before they are eligible to appear in a test failover.