Nutanix NCP-BC-7.5 Test Engine Practice Test Questions, Exam Dumps [Q13-Q31]

Nutanix NCP-BC-7.5 Test Engine Practice Test Questions, Exam Dumps

100% Free NCP-BC-7.5 Daily Practice Exam With 112 Questions

NEW QUESTION # 13
An administrator is concerned about the operational overhead of manually creating and managing categories across both the primary and recovery sites to ensure Recovery Plans function correctly during failover and failback. What Nutanix Disaster Recovery behavior minimizes this concern?

• A. Categories are automatically synchronized to the recovery site AZ when they are specified in a Recovery Plan.
• B. Recovery Plans replicate categories only during an active failover event to minimize replication traffic.
• C. Categories only need to be configured at the recovery site since that is where failover operations are executed.
• D. Categories must be manually replicated using the Prism Central API between sites to ensure consistency.

Answer: A

Explanation:
Nutanix Disaster Recovery (formerly known as Leap) utilizes Prism Central-based " Categories " to group virtual machines for protection. These categories are used within Protection Policies to determine replication schedules and within Recovery Plans to determine power-on sequences and network mappings. A common operational concern is the need to manually replicate these category definitions across different availability zones (AZs).
To reduce this operational overhead, Nutanix has implemented an automatic synchronization mechanism.
When an administrator creates a Recovery Plan in Prism Central and specifies certain categories for failover, the system automatically synchronizes the definition and metadata of those categories to the paired recovery AZ. This ensures that if the primary Prism Central instance becomes unavailable, the recovery site already possesses the necessary grouping logic to identify and recover the correct virtual machines . This " policy- driven " approach ensures consistency across sites and eliminates the risk of human error associated with manual configuration (Option B). By automating the lifecycle of categories between paired sites, Nutanix ensures that the disaster recovery environment is always aligned with the production environment, allowing for seamless failover and failback operations without the need for repetitive administrative tasks.

NEW QUESTION # 14
After a failover and stabilization of workloads at the recovery AZ, an administrator removes several VMs from the protection policy because they are no longer required. Which action should be performed as part of post-failover cleanup to prevent unnecessary storage consumption?

• A. Recreate the recovery plan.
• B. Delete the associated recovery points.
• C. Reconfigure the replication schedule.
• D. Disable Nearsync replication.

Answer: C

Explanation:
Post-failover cleanup is a vital operational step to ensure that the environment remains optimized and that resources are not being wasted on workloads that are no longer part of the production environment. When virtual machines are removed from a Protection Policy after a failover, the orchestration engine stops creating new recovery points for them; however, the existing schedule metadata and historical snapshots may still consume space on both the primary and recovery clusters. Reconfiguring the replication schedule (Option B) is the specific task that refreshes the policy ' s state and forces the system to re-evaluate the storage requirements for the remaining entities. This action ensures that the background cleanup processes (managed by Cerebro and Curator) can properly identify and purge the snapshots associated with the removed VMs once their retention period has passed. Failing to reconfigure the schedule or the associated protection policy can leave " orphaned " snapshots in the storage tier, leading to a steady increase in storage utilization over time. By reconfiguring the schedule, the administrator confirms the new steady-state of the DR environment, ensuring that storage is only consumed by the active, required workloads.

NEW QUESTION # 15
A remote office deployment consists of a two-node Nutanix hybrid cluster. An administrator attempts to configure a protection domain with a 5-minute RPO (Nearsync) replicating to a central datacenter.
Why is the administrator unable to successfully configure this Nearsync schedule?

• A. The minimum RPO supported for a two-node cluster is 15 minutes.
• B. Nearsync replication requires a minimum of three nodes in the cluster.
• C. Nearsync is only supported on All-Flash clusters, not hybrid models.
• D. Two-node clusters require a Witness VM to enable Nearsync replication

Answer: B

Explanation:
Nutanix NearSync replication provides a middle ground between traditional asynchronous replication and synchronous mirroring, offering RPOs as low as 1 minute using Lightweight Snapshots (LWS). However, the LWS mechanism and the high-frequency metadata operations required to maintain a 1-to-15 minute RPO have specific hardware and cluster-level requirements.
One of the strict prerequisites for enabling NearSync is the cluster size. Nutanix requires a minimum of a three-node cluster for NearSync replication. This is because the system must have enough resources to distribute the LWS metadata and handle the increased I/O overhead without compromising the cluster ' s availability or performance. In a two-node cluster (which is common for small ROBO deployments), the system does not meet the minimum redundancy and resource thresholds required for the NearSync engine to operate reliably. While two-node clusters support standard Asynchronous replication (with a 60-minute RPO or higher), they are restricted from using the NearSync lightweight snapshot engine. An administrator attempting to set a 5-minute RPO on a two-node cluster will find the option either grayed out or the task will fail validation. To achieve a 5-minute RPO, the organization would need to expand the remote office cluster to at least three nodes or settle for a higher RPO supported by standard asynchronous replication on the existing hardware.

NEW QUESTION # 16
After a storage failover in a synchronous replication environment, users report higher I/O latency and degraded performance compared to pre-failover levels. Cluster health is normal, and replication is functioning correctly. Which post-failover cleanup action could the administrator perform to correct the performance issue?

• A. Manually realign the compute and storage locations of the affected VMs.
• B. Wait for Acropolis Dynamic Scheduler to rebalance the workloads of the affected VMs.
• C. Reconfigure the replication schedule of the affected VMs.
• D. Increase the snapshot retention period of the affected VMs.

Answer: A

Explanation:
Synchronous replication environments (like Metro Availability) allow for zero-RPO failover, but the performance of the workload is highly dependent on " Data Locality " . Nutanix architecture is built on the principle that a VM ' s compute (vCPU/RAM) should ideally reside on the same host or cluster that serves its primary storage I/O.
During a storage failover, the " Active " container role may move to the recovery site, but the virtual machines might still be running on the primary site ' s compute nodes. This causes " Remote I/O, " where every read and write must traverse the network link to reach the active storage container at the other site, resulting in the reported higher latency and degraded performance. To resolve this, the administrator must " realign " the compute and storage by performing a vMotion (or live migration) of the VMs to the cluster that is now hosting the active storage role. While the Acropolis Dynamic Scheduler (ADS) (Option D) eventually attempts to rebalance, a manual realignment ensures that performance is restored immediately after the failover stabilization. Reconfiguring schedules (Option C) or retention (Option A) has no impact on real-time I
/O latency, highlighting the critical role of data locality in high-performance BCDR designs.

NEW QUESTION # 17
An administrator notices that storage utilization continues to increase at both the primary and recovery sites after implementing a third-party backup solution that uses protection policies. Which configuration should be reviewed first?

• A. Replication traffic encryption
• B. Network segmentation
• C. Retention settings in the backup solution
• D. Recovery validation schedule in the backup solution

Answer: C

Explanation:
Storage consumption in a BCDR environment is directly governed by two factors: the frequency of recovery points (RPO) and the length of time those points are kept (Retention). When a third-party backup solution integrates with Nutanix Protection Policies, it often takes over the management of the snapshot lifecycle.
If storage utilization is increasing unexpectedly at both sites, the most likely cause is that recovery points are not being expired or purged at the expected rate. The administrator should first review the retention settings within the backup solution. If the retention period is set too long, or if the backup software is failing to send the " delete " command to Prism after its local catalog is updated, snapshots will accumulate on both the primary and recovery Nutanix clusters, leading to a steady growth in storage consumption. Other factors like network segmentation (Option C) or encryption (Option B) affect traffic paths and security but do not directly influence the quantity of data stored on the disks. Recovery validation (Option A) might use temporary storage but should not cause a continuous, long-term increase. Therefore, aligning the retention policy of the backup software with the available cluster capacity is the primary troubleshooting step.

NEW QUESTION # 18
A security team has detected a ransomware attack that began encrypting files on the primary site at 2:00 AM.
By 2:45 AM, the primary site is still accessible but workloads are compromised. The administrator needs to recover to a known-good state from before the attack.
Which statement shows the action and reasoning that the administrator should consider?

• A. Planned Failover, as it guarantees zero data loss by capturing the most current state of all VMs.
• B. Test Failover, to validate the recovery point in isolation before committing to a full failover.
• C. Unplanned Failover, as it allows the administrator to select a specific recovery point in time.
• D. Planned Failover, as the primary site is still accessible and a clean final snapshot can be created before failing over.

Answer: C

Explanation:
In a Nutanix Disaster Recovery context, choosing the right failover type is critical during a ransomware event.
A " Planned Failover " is designed for maintenance scenarios. Its first step is to synchronize the current data state to the recovery site to ensure zero data loss. In a ransomware attack, the " current state " is encrypted or corrupted data. If an administrator performs a Planned Failover at 2:45 AM, the system will capture and replicate the encrypted files, effectively " backing up " the ransomware to the recovery site.
To successfully recover from ransomware, the administrator must perform an " Unplanned Failover. " Despite the name, this failover type is the correct choice for this scenario because it allows the administrator to manually select a historical recovery point from the destination cluster ' s storage. By choosing a recovery point from 1:00 AM (before the attack began), the administrator can restore the virtual machines to a known- good, unencrypted state. This is a primary use case for maintaining a multi-day or multi-week snapshot retention policy. While a " Test Failover " (Option A) could be used to verify the 1:00 AM snapshot in an isolated network first, the ultimate production recovery is achieved via an Unplanned Failover that specifically targets a point-in-time snapshot that predates the infection.

NEW QUESTION # 19
An administrator wants to protect the snapshots created on the cluster. Only authorized users should be allowed to modify or delete the snapshots on the cluster. How can the administrator harden the security of the snapshots?

• A. Configure CVM and AHV hardening.
• B. Configure Approval policy for snapshots.
• C. Configure a backup user with admin privileges.
• D. Configure cluster lockdown and use SSH keys.

Answer: B

Explanation:
Hardening a Nutanix cluster for Business Continuity involves implementing security controls that protect recovery data from unauthorized destruction. In many modern cyberattacks, specifically ransomware, the goal is not just to encrypt production data but also to delete the snapshots and backups that would allow for recovery. To satisfy the requirement that only authorized modifications occur, the administrator must move beyond simple Role-Based Access Control (RBAC) and implement an " Approval Policy " .
The Approval Policy feature in Prism Central forces a secondary layer of validation for sensitive operations like snapshot deletion. When a user tries to delete a recovery point, the Nutanix orchestration engine captures the request and holds it in a " Pending " state. The request must be reviewed and approved by a designated person with approval authority. This ensures that even if an administrator ' s account is compromised, the attacker cannot immediately wipe out the snapshots needed to restore the environment. This " multi-person control " is a recognized security best practice for protecting mission-critical data. While cluster lockdown (Option C) prevents unauthorized SSH access, it does not manage the logical management of data through the Prism UI. An Approval Policy provides the specific " modification and deletion " control requested, ensuring that the cluster ' s recovery points remain a reliable " source of truth " following a security incident or administrative error.

NEW QUESTION # 20
A sudden and unrecoverable hardware failure occurs at the primary site, making the Prism Element console for that cluster inaccessible. The secondary site is healthy and contains the latest replicated snapshots. Which action must the administrator take on the secondary cluster to restore the VMs?

• A. Select the Protection Domain and click Activate.
• B. Restart the local Cerebro service and wait for the VMs to power on.
• C. Select the Protection Domain and click Migrate.
• D. Create a new Protection Domain and import the snapshots.

Answer: B

Explanation:
When a primary Nutanix site suffers a catastrophic failure, the disaster recovery plan must be executed from the recovery (secondary) site . In a legacy Protection Domain-based environment, the secondary site is in a " passive " or " standby " mode, receiving snapshots but not actively running the workloads. The traditional method to failover is using the " Activate " command (Option A), which promotes the PD and registers the VMs. However, in certain specific failure scenarios or older software versions, the secondary cluster may require a service-level reset to recognize its new role as the active master for those specific workloads.
The Cerebro service is the core component responsible for managing Protection Domains and replication metadata. If the primary site is completely inaccessible and the secondary site ' s metadata state needs refreshing to initiate recovery, restarting the Cerebro service on the secondary cluster CVMs can force a re- evaluation of all local snapshots and protection domain states. This action triggers the recovery logic, allowing the administrator to then see and activate the recovery points. While " Activate " is the goal, the first technical step in a situation where the cluster management plane is unstable or the primary is gone is ensuring the data protection services are aware of the current state. This allows the VMs to be restored from the latest snapshots, fulfilling the Recovery Time Objective (RTO) despite the complete loss of the source infrastructure.

NEW QUESTION # 21
An organization is finalizing its Disaster Recovery (DR) plan. The primary objective is to balance cost- efficiency with a target RTO of under 15 minutes. Data currently resides in Object Storage, but the team is debating between a Zero Compute approach and a Pilot Light approach. Why would a Pilot Light infrastructure be selected over a Zero Compute model despite the higher " Moderate " cost?

• A. Lowest cost option available for long-term idle infrastructure.
• B. Only model that allows for a " Power-On " recovery trigger.
• C. Eliminates the need for any Object Storage (S3/Blob) costs.
• D. Faster recovery due to metadata and cluster already existing.

Answer: D

Explanation:
When designing disaster recovery to a cloud environment (such as NC2 on AWS or Azure), organizations must choose a compute model that aligns with their Recovery Time Objective (RTO). The " Zero Compute " model is the most cost-efficient because it stores only the data (snapshots) in low-cost Object Storage (S3 or Blob) and does not maintain a running cluster. However, the RTO for Zero Compute is high because, in a disaster, the organization must first deploy a new Nutanix cluster, configure it, and then begin the process of hydrating data from the Object Storage.
In contrast, the " Pilot Light " model involves keeping a minimal, active Nutanix cluster (e.g., 3 nodes) running at the recovery site. While this carries a moderate ongoing cost, it significantly reduces the RTO.
Because the cluster already exists, the management plane (Prism Central), the storage containers, and all metadata are already active. When a failover is triggered, the system only needs to power on the VMs or perform a small amount of data hydration. This allows the organization to meet aggressive RTO targets of under 15 minutes, which is generally impossible with the Zero Compute model. Pilot Light provides the " ready-to-go " infrastructure needed for mission-critical applications that cannot afford the multiple hours required to provision a fresh cluster from scratch during an emergency.

NEW QUESTION # 22
An administrator logs into Prism Central (PC) and notices that a replication of a recovery point is still ongoing from Cluster A to Cluster B on a new setup.
* The bytes being replicated aren ' t changing.
* Both site ' s virtual IP addresses are reachable.
* Connectivity between PC/PE is good.
* There is a dedicated LAN between the clusters.
What could be causing this replication to be stuck?

• A. Port 2030 is blocked between CVMs.
• B. Acropolis is down at the Remote Site.
• C. Port 2020 is blocked between CVMs.
• D. Protection Policy is incorrectly configured.

Answer: D

Explanation:
When a replication job is marked as " ongoing " but the progress (bytes completed) is stagnant, it typically indicates a mismatch in the configuration or a failure in the orchestration logic rather than a total network blackout, especially when virtual IPs are confirmed reachable. In a " new setup, " a very common root cause is an incorrectly configured Protection Policy.
This can include issues such as mismatched category assignments, incorrect target site selection, or an invalid replication schedule that the system is unable to initialize properly. If the policy itself is misconfigured-for instance, if it is attempting to replicate to a storage container that hasn ' t been mapped or lacks permissions- the Cerebro service may initiate the task but then fail to progress the data transfer. While blocked ports (Options C and D) are common culprits in replication failures, they usually result in immediate " unreachable
" alerts or job failures rather than a " stuck " status where connectivity is otherwise reported as healthy. If the Acropolis service were down at the remote site (Option A), the cluster would likely report the site as disconnected or show a critical service alert in Prism. Therefore, the most logical first area to investigate in a new, non-progressing setup is the logic and settings defined within the Protection Policy itself.

NEW QUESTION # 23
An administrator has been tasked with configuring a Nutanix replication solution that provides an RPO of zero. Which solution should the administrator choose?

• A. Cloud Connect
• B. Async Replication
• C. Nearsync Replication
• D. Synchronous Replication

Answer: D

Explanation:
The Recovery Point Objective (RPO) is a measure of how much data an organization can afford to lose during an outage. An RPO of zero means that absolutely no data loss is tolerated; every write performed at the primary site must be safely committed to the recovery site before the application receives a confirmation. In the Nutanix portfolio, Synchronous Replication (Option A) is the only technology that guarantees this level of data protection. It mirrors every write in real-time between two clusters, ensuring they are always in perfect synchronization. In contrast, Nearsync Replication (Option B) allows for very low RPOs (as low as 20 seconds to 1 minute), but it is still fundamentally an asynchronous process using lightweight snapshots, meaning some " data-in-flight " could be lost. Async Replication (Option C) typically involves RPOs of one hour or more and is used for less critical workloads. Cloud Connect (Option D) is a legacy feature for off-site backup and does not support zero-RPO requirements. Synchronous Replication is the " gold standard " for Tier-1, mission-critical applications where data integrity and zero loss are the primary business requirements, provided the network latency between sites is 5ms or less.

NEW QUESTION # 24
What is the bandwidth limit of a single Nutanix Cloud Gateway for IPSec traffic?

• A. 10 Gbps
• B. 500 Mbps
• C. 250 Mbps
• D. 1 Gbps

Answer: D

Explanation:
The Nutanix Cloud Gateway serves as a critical bridge between on-premises Nutanix clusters and the Nutanix Cloud Availability Zone (AZ). Its primary role is to provide a secure, encrypted tunnel for replicating recovery points and managing disaster recovery orchestration metadata. When utilizing standard IPSec for this traffic, the system architecture imposes certain throughput limitations based on the processing capabilities of the gateway instance. For a single Nutanix Cloud Gateway, the maximum supported bandwidth for IPSec- encrypted traffic is 1 Gbps.
This 1 Gbps limit is an important consideration for BCDR planning, as it defines the maximum " Snapshot-on- wire " throughput available for a given protection policy. If an organization has a high data change rate (churn) that exceeds 1 Gbps of sustained replication traffic, the Recovery Point Objective (RPO) may be at risk of lag. While the physical network link might be 10 Gbps or higher, the encryption overhead of the IPSec protocol within the gateway VM is the limiting factor. To achieve higher aggregate throughput, administrators would need to deploy multiple gateways or consider high-performance direct connectivity options if available.
Understanding this 1 Gbps threshold ensures that administrators can accurately size their replication windows and manage expectations for initial seed transfers and ongoing delta synchronization to the cloud AZ.

NEW QUESTION # 25
An administrator is tasked with ensuring the VMs do not experience downtime during an upcoming network maintenance on the primary cluster. The VMs are protected by a Protection Policy and are configured under a Recovery Plan. What failover mechanism should the administrator use to ensure the VMs are available on the target cluster before the maintenance window?

• A. Unplanned Failover
• B. Validate the Recovery Plan
• C. Planned Failover
• D. Test Failover

Answer: C

Explanation:
In a Business Continuity strategy, " downtime " can be categorized as either unexpected (disaster) or controlled (maintenance). When an administrator knows that a disruption is coming, such as scheduled network maintenance on a primary cluster, they should utilize the " Planned Failover " mechanism within the Nutanix Recovery Plan.
A Planned Failover is a graceful, orchestrated migration. It first shuts down the virtual machines at the primary site to ensure all data is flushed and no new writes occur. It then performs a final synchronization to the recovery site to ensure zero data loss (Zero RPO), and finally powers the VMs on at the destination site according to the plan ' s sequence. This differs significantly from an " Unplanned Failover " (Option A), which assumes the primary site is already offline and may result in minor data loss depending on the last successful replication. A " Test Failover " (Option D) merely validates the process in an isolated environment and does not move the actual production workload. By executing a Planned Failover before the maintenance begins, the administrator ensures that the services are safely running on the target cluster, maintaining application availability and meeting the objective of zero downtime during the maintenance window.

NEW QUESTION # 26
Which native Nutanix tool is used to determine connectivity between two sites during disaster recovery testing?

• A. ncc
• B. ecli
• C. acli
  /B. ccli

Answer: B

Explanation:
Disaster recovery success depends on the stability of the network link and the health of the services responsible for data replication. Nutanix Cluster Check (NCC) is the primary native health-monitoring tool for the Nutanix environment. NCC includes a comprehensive suite of checks specifically designed for Data Protection and BCDR.
During disaster recovery setup or testing, an administrator can run NCC to verify that the clusters are correctly paired, that remote site connectivity is functional, and that the required ports (such as 2009 and
2020) are open and reachable. Specific NCC checks like remote_site_connectivity_check or replication_health_check provide granular insights into whether the " handshake " between the primary and recovery sites is succeeding. While acli (Acropolis CLI) or ecli (Erasure Coding CLI) are used for managing VMs or storage disks, they do not provide the high-level diagnostic capabilities of NCC. By regularly running NCC, an administrator can proactively identify connectivity issues-such as firewall changes or routing failures-that could otherwise lead to replication failures and compromise the organization ' s recovery objectives.

NEW QUESTION # 27
Which log file should an administrator review to ensure consistent connectivity stability between primary and remote disaster recovery sites?

• A. genesis.out
• B. cerebro.INFO
• C. mantle.out
• D. prism_monitor.INFO

Answer: B

Explanation:
The Nutanix architecture relies on specialized services running on each Controller VM (CVM) to handle specific cluster operations. The " Cerebro " service is the primary engine responsible for data protection and replication tasks across the Nutanix cluster. It manages recovery points, snapshot schedules, and the actual transfer of data between the local cluster and remote sites. Consequently, the cerebro.INFO log file is the most vital resource for an administrator troubleshooting replication health or site-to-site connectivity. This log records critical events such as the start and completion of replication jobs, handshake failures between clusters, and timeout errors during snapshot transfers. If an administrator notices that replication is " hung " or failing consistently, cerebro.INFO provides the granular detail needed to see if the issue is a network timeout, a remote service unavailability, or a metadata synchronization error. Reviewing this log helps ensure that the connection stability is maintained and that any deviations in replication performance are identified before they impact the Recovery Point Objective (RPO). Other logs like genesis.out (Option B) are more focused on service startup and configuration rather than the ongoing health of the BCDR replication stream.

NEW QUESTION # 28
A solution architect designs a protection policy in Prism Central to protect a specific set of VMs. The design calls for synchronous replication to two separate availability zones (AZs) simultaneously to ensure zero data loss at multiple physical locations. Which configuration limitation prevents the implementation of this specific design?

• A. Synchronous replication requires a minimum RPO of 1 hour when targeting multiple sites.
• B. Synchronous replication is restricted to Protection Domains and cannot be used in Protection Policies.
• C. A protection policy supports only one synchronous replication schedule.
• D. Prism Central prevents pairing with more than one AZ at a time.

Answer: C

Explanation:
Nutanix Disaster Recovery provides multisite replication capabilities, allowing a single cluster to protect workloads across multiple locations. However, there are specific architectural constraints regarding the type of replication schedules that can coexist within a single Protection Policy.
The primary limitation in this architect ' s design is that a single Nutanix Protection Policy supports only one synchronous replication schedule. While you can configure a policy to replicate to multiple sites using Asynchronous or NearSync schedules, you cannot natively instruct the system to perform a synchronous " 3- way " write where a single VM mirrors every I/O to two different physical destination clusters simultaneously. This is due to the extreme latency and metadata synchronization overhead that would be required to maintain zero-RPO consistency across three sites for every single write operation. Prism Central does allow pairing with more than one AZ (negating Option B), and synchronous replication is fully supported in Protection Policies (negating Option D). Therefore, to achieve the desired level of protection, the architect would need to use a combination of one synchronous schedule and additional asynchronous schedules to the second AZ, rather than attempting two simultaneous synchronous links within one policy.

NEW QUESTION # 29
An administrator is planning to deploy some 2-node clusters and is reviewing data protection strategies for some of the critical VMs.
What can be the minimum RPO for these VMs?

• A. 1 hour RPO
• B. 1 minute RPO
• C. 0 minute RPO
• D. 6 hour RPO

Answer: A

Explanation:
Nutanix 2-node clusters are often used in small remote office (ROBO) environments to provide high availability with a smaller hardware footprint. However, the reduced node count introduces specific limitations on advanced data protection features compared to standard 3-node or larger clusters.
One of the key limitations of a 2-node cluster is the support for high-frequency replication. Technologies like NearSync (which provides RPOs from 1 to 15 minutes) and Synchronous replication (0 RPO) require a minimum of three nodes to manage the necessary metadata overhead, storage consistency, and lightweight snapshot (LWS) engine requirements. In a 2-node cluster, the system is restricted to using standard Asynchronous replication. The minimum RPO supported for standard Asynchronous replication in these small cluster configurations is typically 1 hour (60 minutes). An administrator attempting to set a more aggressive RPO will find that the system does not support the necessary lightweight snapshot infrastructure.
Therefore, while a 2-node cluster provides excellent local availability, its off-site disaster recovery capability is limited to a 1-hour RPO, which should be considered during the initial architectural design and risk assessment phase for critical workloads.

NEW QUESTION # 30
A VM is configured with a 5-minute Nearsync RPO. After several hours, replication transitions back to hourly RPO. Alerts indicate the minute schedule cannot be maintained. What is the most likely root cause?

• A. RTT is greater than 5 ms.
• B. Only one recovery plan exists.
• C. Bandwidth is insufficient.
• D. Reverse synchronization is disabled.

Answer: C

Explanation:
Nutanix NearSync replication uses Lightweight Snapshots (LWS) to achieve RPOs as low as 1 minute. To maintain this aggressive schedule, the system must be able to replicate all the " delta " changes (the data that has changed since the last snapshot) within the RPO window. If the data change rate (churn) of the VM increases, or if the available network bandwidth decreases, the system may find that it cannot complete the replication of one LWS before the next one is due.
When the Nutanix Cerebro service detects that it is consistently missing its NearSync target, it will automatically " downshift " the replication to a standard Asynchronous schedule (typically hourly) to ensure that the VM remains protected at a manageable frequency. This is a self-healing mechanism designed to prevent replication jobs from stacking up and causing cluster instability. Insufficient bandwidth (Option D) is the most common cause for this downshift, as the " Snapshot-on-wire " cannot be moved fast enough to satisfy the 5-minute requirement. While high RTT (Option A) is a requirement for Synchronous replication, NearSync is designed to handle higher latencies (up to 80ms or more), making bandwidth the primary bottleneck in these troubleshooting scenarios.

NEW QUESTION # 31
......

Use Valid New NCP-BC-7.5 Test Notes & NCP-BC-7.5 Valid Exam Guide: https://www.dumpsking.com/NCP-BC-7.5-testking-dumps.html

NCP-BC-7.5 exam torrent Nutanix study guide: https://drive.google.com/open?id=112K2THEpG05cAjCVRG9ZX5llN_zjZz3K