Free Nutanix NCP-BC-7.5 Practice Exam with Questions & Answers | Set: 4

This question evaluates the administrator ' s ability to map business RPO (Recovery Point Objective) requirements to the appropriate Nutanix technology. A requirement for " maximum 15 minutes of data loss " means the system must replicate data at least every 15 minutes. Nutanix offers two primary ways to achieve this: traditional Asynchronous replication and Nearsync replication. While Async (Option D) can technically be configured for a 15-minute interval, it relies on standard, full snapshots which can be heavy and resource-intensive, potentially leading to performance lag if the data churn is high. Nearsync Replication (Option B) is specifically designed for these low-RPO scenarios (from 20 seconds up to 15 minutes) by using " Lightweight Snapshots " (LWS). LWS minimize the storage and I/O overhead compared to traditional snapshots, making Nearsync the more reliable and robust choice for Tier-1 applications. Furthermore, Nearsync is built to handle the constant, high-frequency data transfers required to maintain a strict 15-minute window without impacting application performance. Therefore, Nearsync with a 15-minute RPO is the " best " configuration because it is the purpose-built solution for the stated performance and data protection goals.

Nutanix Metro Availability is a continuous availability solution that provides a zero Recovery Point Objective (RPO) and near-zero Recovery Time Objective (RTO) across two sites. For this configuration, there are two distinct latency requirements that administrators must manage. First, the Round Trip Time (RTT) latency between the two storage clusters participating in the synchronous replication must be less than 5ms to ensure application performance is not significantly degraded by the write-synchronization process. Second, the Witness VM, which acts as an external arbitrator to prevent " split-brain " scenarios during a site failure, has a more flexible latency requirement. The maximum RTT between the Witness VM and the managed Protection Domains (PDs) must be less than 200ms. This higher threshold allows the Witness to be placed in a separate geographical region or a third-party cloud availability zone (AZ), ensuring it remains independent of the failure domain affecting the primary and secondary sites. If the latency to the Witness exceeds 200ms, the cluster may be unable to quickly acquire the lock necessary to automate failover, potentially causing the Metro Availability configuration to fail during an actual disaster event.