An administrator is supporting a business critical environment and deploys metro availability to achieve a zero data loss configuration. The two…

Metro Availability provides a zero Recovery Point Objective (RPO=0) by using synchronous replication. This means every write I/O must be successfully written to both the primary and secondary sites before being acknowledged. The inter-cluster network link must therefore support the peak write I/O of the protected workloads. The new workload requires 150 MB/s (MegaBytes per second). A 1 GbE link has a theoretical maximum throughput of 125 MB/s (1 Gigabit/sec ÷ 8 bits/Byte = 125 MegaBytes/sec). Since the required write throughput (150 MB/s) exceeds the available network bandwidth (125 MB/s), the bandwidth must be increased.

The workload must be configured to read at greater than 12.5MB/S.: Read I/O is served locally and is not replicated over the Metro link, so read throughput is irrelevant to the bandwidth requirement for replication. The replication frequency must be less than 60 minutes.: Replication frequency is a setting for asynchronous (non-zero RPO) protection domains, not for the continuous synchronous replication used by Metro Availability. Zero data loss nearsync must be used to support this workload.: Nearsync provides a low RPO (minutes), but it is not an RPO of zero. The requirement is to maintain the existing zero data loss configuration.

1. Nutanix. (2023). Data Protection and Recovery with Prism Element Guide v6.7. Chapter: "Metro Availability (ESXi and AHV)". Section: "Metro Availability Requirements and Limitations". This section specifies network requirements, including bandwidth sufficient for peak writes and latency constraints.

2. Nutanix University. (2023). Nutanix Data Protection and Disaster Recovery (NDPDR). Module: "Business Continuity with Metro Availability". The courseware details that synchronous replication performance is directly gated by the inter-site network bandwidth and latency.