An organization has two Nutanix clusters managed by a single Prism Central (PC) instance. They intend to implement Synchronous Replication between the sites. During a failover test, the administrator notices that automatic failover does not occur when the primary site's storage becomes unavailable.
What is the most likely cause of this behavior based on an analysis of the requirements?

• A. Automatic failover is only supported when the clusters are managed by two different PC instances.
• B. Automatic failover is only supported for network outages and not for storage outages.
• C. Synchronous replication does not automatically failover without a Witness.
• D. The RTT is likely more than 5ms, which disables automatic failover.

An administrator has received the following alert:

The administrator begins gathering troubleshooting information and determines the following: The VM has been replicating to this cluster successfully for at least 6 months The bandwidth has been sufficient to this point and hasn't caused an issue before Network connectivity is good and all necessary ports remain open and reachable There aren't hardware issues, and software is up to date What else could have caused this alert?

• A. Protection Policy schedule was temporarily paused.
• B. A new Availability Zone was paired to Prism Central.
• C. The VM had a significant one-time surge in change rate.
• D. This was a first seed replication without a reference snapshot.

A VM is protected in an Async Protection Policy and added to a Recovery Plan. An administrator is attempting to perform a planned failover of the VM.
How many recovery points are created and replicated during the planned failover process?

• A. One recovery point is created per VM when the VM is powered on.
• B. One recovery point is created while the VM is powered off.
• C. No recovery points are created and the last successfully replicated recovery point is used to restore the VM.
• D. One recovery point is created while the VM is powered on and one while the VM is powered off.

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 fail for both VMs.
• B. 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.
• C. The "Revert" operation will succeed for "REPORTING-DEV", but the option will be unavailable or blocked for "ERP-PROD".
• D. The "Revert" operation will succeed for "ERP-PROD" because synchronous replication natively locks the metadata, but it will fail for "REPORTING-DEV".

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