Metro Availability in Nutanix requires that the primary and secondary storage containers be configured identicallyto ensuredata replication consistency.
Option C (The destination storage container is not empty) is correct:
Theremote storage container must be emptybefore Metro Availability can be enabled.
Existing data can cause conflictsand prevent it from appearing in the "Compatible Remote Sites" list.
Option D (Both storage containers must have the same name) is correct:
Metro Availability requires thatstorage containers have identical names across clusters.
If namesdo not match, thestorage container will not be listed as compatible.
Option A is incorrect: Metro Availability works regardless of hardware vendor differences.
Option B is incorrect:Compression does not affect compatibilitybut may impact performance.
References:
Nutanix Metro Availability Deployment Guide
Nutanix Best Practices forConfiguring Remote Sites for Metro Availability Nutanix KB #Troubleshooting Storage Container Issues in Metro Availability

Nutanix Data Protection enforces strict snapshot lifecycle controls to ensure recovery integrity. The system prevents deletion of any snapshot that is actively referenced by a running operation. The documentation states:
"Snapshots that are part of an active recovery or restore workflow cannot be deleted until the operation completes, as they are required to maintain data consistency and restore points." This includes DR failover tests, restorations, or live recovery workflows. Corrupted snapshots do not cause deletion failure; the system can still delete a corrupted snapshot unless it's attached to an active workflow.
Ransomware affects guest data, not the snapshot metadata in Prism. Approval policies do not block snapshot deletion unless tied to automation policies, which is rare and would produce a different error.
Therefore, active recovery operations are the most common and most accurate cause when deletion is blocked.

Nutanix platform timing guidelines state that Prism Central requires accurate clock synchronization to ensure proper authentication, event logging, certificate validation, and cluster orchestration. The documentation details that "NTP must be configured to a reachable, reliable time source, and best practice is to configure Prism Central to use an external, independent, standards-based NTP server." Using a Domain Controller is acceptable only if the DC itself is properly synchronized with an authoritative external NTP source, but Nutanix strongly recommends specifying the external source directly in Prism Central for consistency across hypervisors and multi-cluster environments. Adding a DNS server IP is not time-related. Adding a hostname is valid only if it resolves to a functioning NTP server, but the question requires the correct method, not the acceptable syntax.
Therefore, selecting an external NTP server is the correct and recommended configuration.

TheBully VMs List (Option C)in Prism Central'sIntelligent OperationsidentifiesVMs consuming excessive CPU, memory, or storage, which negatively affects other VMs.
* Option A (Inactive VMs List)is used foridentifying unused VMsbut does not detect performance issues.
* Option B (Overprovisioned VMs List)helps identifyVMs with excessive allocated resources, but it does not focus on live performance impact.
* Option D (Constrained VMs List)highlightsVMs suffering from resource contention, not those causing it.
References:
* Nutanix Prism Central #Intelligent Operations and Performance Tuning
* Nutanix KB #Identifying and Managing Resource-Hogging VMs