NCP-BC-7.5 Dumps PDF 2026 Strategy Your Preparation Efficiently [Q43-Q60]

NCP-BC-7.5 Dumps PDF 2026 Strategy Your Preparation Efficiently

Latest Verified & Correct Nutanix NCP-BC-7.5 Questions

NEW QUESTION # 43
A company is recovering a 3-tier application (Database, Middleware, Web). The administrator executes the Recovery Plan. The Web tier VMs start up but applications immediately crash because they cannot connect to the Database tier. Which setting in the Recovery Plan should the administrator have configured to prevent this execution failure?

• A. Automatic Volume Group attachments
• B. Protection Policy mapping
• C. AppType and AppTier category assignments
• D. Optional inter-stage delays

Answer: D

Explanation:
Orchestrating the recovery of multi-tier applications requires more than just powering on virtual machines; it requires managing the dependencies between application layers. In a standard 3-tier architecture, the Middleware and Web tiers typically depend on the Database being fully operational and ready to accept connections before they can successfully initialize. If a Recovery Plan powers on all tiers too quickly or simultaneously, the " upstream " services will fail to find their database backend, leading to the application crashes described in the scenario.
The Nutanix Recovery Plan provides " execution stages " to handle this boot ordering. However, even if tiers are in separate stages, a VM reaching a " Power On " state in the hypervisor does not mean the application services (like SQL or Oracle) are fully booted and ready for traffic. To address this, the administrator should configure " optional inter-stage delays " . This setting allows the administrator to define a specific wait time (in seconds) between the completion of one stage (e.g., Database power-on) and the start of the next (e.g., Middleware power-on). This delay gives the database engine enough time to finish its internal checks, mount its databases, and open its network ports. By incorporating these surgical delays, the administrator ensures a reliable, automated recovery where each tier only attempts to start once its required dependencies are fully operational at the destination site.

NEW QUESTION # 44
An administrator is troubleshooting a hung replication. When checking the replication status, the complete percent and bytes completed do not increase. The administrator checks the Stargate logs on the destination cluster and confirms the writes are failing with " nfs status 28 " . Checking the container info on the destination cluster, free space on the container is 0. The administrator confirms that there is sufficient space available in the storage pool. What could be the reason for free space on the container to be 0?

• A. Compression is turned off.
• B. Advertised capacity is set for the container.
• C. Thick Provisioning is consuming all available space.
• D. Replication factor needs to be set to 1.

Answer: B

Explanation:
In a Nutanix environment, " Advertised Capacity " is a logical limit (a quota) that an administrator can set on a specific storage container. Even if the physical storage pool has terabytes of free space, if a container ' s advertised capacity is reached, the hypervisor and the Nutanix services will perceive the container as being
100% full.
In this troubleshooting scenario, the " nfs status 28 " error code is a standard indicator for " No space left on device " . Since the administrator confirmed the pool is healthy, the logical limit on the container is the only remaining bottleneck. Replication jobs will " hang " because the destination Stargate service cannot write the incoming data blocks to a container that reports zero free space. To resolve this, the administrator must either increase the advertised capacity value in Prism or remove the limit entirely to allow the container to consume the available physical space in the pool. This highlights a common configuration " trap " where logical quotas-intended for multi-tenant management-can inadvertently block critical BCDR processes like replication if not monitored or sized correctly according to the protected VM growth.

NEW QUESTION # 45
An administrator is managing a mission-critical Inventory-VM that is part of a Protection Domain (PD) named PD_Production.
* Monday: A scheduled snapshot of PD_Production is successfully taken.
* Tuesday: Due to a configuration error during a cleanup task, the administrator accidentally removes Inventory-VM from the PD_Production Protection Domain. The VM continues to run, but it is no longer being snapped or replicated.
* Wednesday: A database corruption occurs on Inventory-VM. The administrator finds the local snapshot from Monday and performs an In-place Restore (Revert) to recover the data.
Following the successful completion of the In-place Restore, what is the status of Inventory-VM regarding its data protection?

• A. The restore fails because the VM is no longer a member of the PD that owns the snapshot.
• B. The VM is restored, but it is placed into a new, system-generated PD named Restored_Entities.
• C. The VM is restored to Monday ' s data state and is automatically added back into the PD.
• D. The VM is restored to Monday ' s data state but remains outside of any PD.

Answer: D

Explanation:
In Nutanix Protection Domains, the relationship between a virtual machine and a snapshot is tied to the metadata at the time the snapshot was created . When an administrator removes a VM from a PD (Option B), the cluster stops taking new snapshots, but the historical snapshots (recovery points) remain in the storage system until their retention period expires .
If a disaster or corruption occurs (Option Wednesday), the administrator can still use those historical snapshots to perform a " Revert " operation. The Nutanix AOS engine can successfully roll back the VM ' s vDisks to the Monday state because the data exists. However, the " Revert " operation only impacts the data on the disks; it does not re-establish the logical configuration of the Protection Domain. Because the VM was explicitly removed from the PD on Tuesday, the system treats it as an " unprotected " VM after the restore is finished. It will not be included in the next scheduled snapshot cycle of PD_Production. To resume ongoing protection, the administrator must manually add the Inventory-VM back into the PD_Production Protection Domain. This scenario illustrates a critical operational point: restoring data does not automatically restore the protection schedule, and administrators must verify the " Protection Status " of VMs following any manual recovery task to ensure they are not left vulnerable to future failures.

NEW QUESTION # 46
An organization uses Nutanix Disaster Recovery with automatic virtual network creation in the Nutanix Cloud AZ. After a successful failback operation from the Nutanix Cloud AZ to the on-premises site, what is the expected behavior regarding the dynamically created virtual networks at the recovery site?

• A. Converted into production networks for use in the future
• B. Automatically cleaned up when no longer required
• C. Must be manually deleted by the administrator
• D. Remain active until the billing cycle ends

Answer: B

Explanation:
Nutanix Disaster Recovery to the Cloud is built on the principle of automation and resource optimization.
When a failover to a Nutanix Cloud Availability Zone (AZ) occurs, the orchestration engine can dynamically provision virtual networks to ensure recovered VMs have immediate connectivity. These networks are temporary infrastructure components required only while the workloads are running in the cloud. Once the primary on-premises site is restored and a failback is successfully executed, the VMs are migrated back to their original home. At this point, the dynamically created virtual networks at the cloud recovery site no longer host any active entities. The Nutanix orchestration engine is designed to automatically clean up these ephemeral resources (Option B) to prevent " infrastructure sprawl " and to ensure the customer is not billed for unused networking components in the cloud. This automated cleanup is a core feature of the Nutanix Cloud AZ workflow, allowing administrators to focus on stabilizing production rather than performing manual housekeeping tasks on the recovery site. This cycle of dynamic provisioning and automated cleanup ensures that the DR environment is always " right-sized " and ready for the next event.

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

Answer: D

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 # 48
What must the maximum Round Trip Latency be less than between a Witness VM and Metro Availability PDs?

• A. 500ms
• B. 5ms
• C. 200ms
• D. 100ms

Answer: C

Explanation:
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.

NEW QUESTION # 49
An administrator configures a VM-VM Anti-Affinity policy for a web application cluster to ensure high availability. The application is protected by a Protection Policy in Prism Central. A failover occurs, moving the VMs to the recovery site.
What determines whether the VM-VM Anti-Affinity rules are active on the recovery site?

• A. The rules are active only if the " Enforce Anti-Affinity " checkbox is selected in the Recovery Plan.
• B. The rules are automatically active because Anti-Affinity policies are intrinsic to the VM metadata replicated by Cerebro.
• C. The rules are active only if the corresponding Anti-Affinity Policy exists on the recovery site.
• D. The rules are inactive because Anti-Affinity policies are not supported in Prism Central-based DR.

Answer: D

Explanation:
VM-VM Anti-Affinity rules are used in Nutanix to ensure that specific virtual machines (such as the nodes of a database cluster or redundant web servers) never run on the same physical host, thereby protecting the application from a single host failure. These rules are typically managed through Prism Central (PC) in a modern deployment.
However, in the context of Disaster Recovery (DR) between two different clusters or availability zones, there is a technical limitation regarding the replication of these affinity policies. While the virtual machine ' s data and primary metadata (CPU, RAM, Disks) are replicated by the Cerebro service, the affinity rules are often considered local cluster constraints. In many versions of Nutanix Disaster Recovery (specifically the initial iterations of Leap/Prism Central-based DR), these affinity policies are not natively " synchronized " or enforced at the recovery site during a failover. This means that when the VMs are recovered at the destination cluster, the hypervisor ' s dynamic scheduler (ADS) may place them on the same host if that host has the most available resources. To maintain anti-affinity at the recovery site, an administrator would typically need to manually recreate the affinity policies at the destination AZ or use specialized orchestration scripts.
Understanding this limitation is vital for ensuring that high-availability requirements are still met after a disaster recovery event has occurred.

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

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

Answer: C

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 # 51
An administrator enables network segmentation for Disaster Recovery on a primary cluster to isolate replication traffic. The primary and recovery clusters are in a " brownfield " configuration, meaning the recovery cluster does not yet have network segmentation enabled.
How is the configuration of the recovery cluster handled in this scenario?

• A. The recovery cluster rejects the connection until the firewall rules on the recovery site are manually updated to allow traffic on port 3260.
• B. The system automatically reconfigures the recovery cluster using the new virtual IP address communicated by the primary cluster.
• C. The administrator must manually enable network segmentation on the recovery cluster.
• D. The system creates a temporary VPN tunnel between the interface eth0 of the recovery cluster and ntnx0 of the primary cluster.

Answer: C

Explanation:
Network segmentation in a Nutanix cluster allows for the physical or logical isolation of different types of traffic (management, storage, and backplane). When applied to Disaster Recovery, it allows an administrator to dedicate a specific network interface (typically ntnx0) and a dedicated subnet for replication traffic, ensuring it does not contend with VM or management traffic for bandwidth.
However, Disaster Recovery is a site-to-site operation that requires a symmetric network configuration. If an administrator enables segmentation on the primary cluster, the Cerebro service at that site will now attempt to originate and receive all replication traffic on the newly defined segmented IP addresses. If the recovery cluster is still in its original " brownfield " state without segmentation, it will be looking for traffic on its management IP addresses (on eth0). This creates a mismatch where the two sites are effectively " speaking different languages " or looking for each other on the wrong networks. Nutanix does not automatically propagate segmentation settings between clusters because each site may have different physical network topologies or VLAN requirements. Therefore, the administrator must manually enable and configure network segmentation on the recovery cluster to match the primary. Only when both sites have consistent segmented interfaces and the routing/firewall rules are updated to allow communication between these new subnets will the replication link be restored and functional.

NEW QUESTION # 52
An administrator executes an Unplanned Failover. The VMs recover at the Recovery Site and are powered on.
However, the application owners report that the VMs are completely isolated and cannot communicate with any other services on the network. The administrator checks the Recovery Plan and notices the Network Mapping section was left blank.
What is the expected configuration for VMs recovered without a valid Network Mapping?

• A. The VMs attach to the same VLAN ID they used at the source site.
• B. The VMs are recovered with their network adapters disconnected.
• C. The VMs are recovered without the network adapters attached.
• D. The VMs attach to the management network of the cluster.

Answer: B

Explanation:
In the Nutanix Disaster Recovery orchestration workflow, Network Mapping is a critical step that tells the system which production VLAN at the primary site corresponds to which VLAN at the recovery site. This ensures that when a VM is recovered, its virtual NIC (vNIC) is " plugged in " to a functional and valid network at the new location.
If an administrator leaves the Network Mapping section blank, the Nutanix orchestrator has no information about where to connect the VM ' s network interface. In this scenario, the priority of the system is to ensure the VM can boot and start its services without causing a " network storm " or security risk. If the system were to simply attach the VM to a random or default network, it could cause IP address conflicts or expose the VM to the wrong security zone. Therefore, the built-in behavior for a failover without a valid mapping is to recover the VM with all its network adapters in a " disconnected " state. The vNIC still exists on the VM, but the " connected " checkbox in the hypervisor is unchecked. This explains why the application owners report that the VMs are " isolated. " To fix this, the administrator must either update the Recovery Plan with the correct mappings and re-run the task or manually connect each VM ' s vNIC to the correct local VLAN in the recovery site ' s Prism interface.

NEW QUESTION # 53
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. Eliminates the need for any Object Storage (S3/Blob) costs.
• B. Only model that allows for a " Power-On " recovery trigger.
• C. Faster recovery due to metadata and cluster already existing.
• D. Lowest cost option available for long-term idle infrastructure.

Answer: C

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 # 54
What must be installed on a guest VM prior to enabling Self-Service Restore?

• A. VirtIO
• B. NGT
• C. Post_Thaw Scripts
• D. Pre_Freeze Scripts

Answer: B

Explanation:
Nutanix Guest Tools (NGT) is a software bundle that must be installed on the guest virtual machine (VM) to enable advanced management and data protection features within the Nutanix ecosystem. For the specific functionality of Self-Service Restore (SSR), NGT provides the necessary communication drivers and the Nutanix SSR agent. This agent allows end-users or administrators to mount recovery point snapshots as local drives directly within the guest operating system. Without NGT, the cluster lacks the specialized hooks into the guest OS required to perform granular file-level recovery without restoring the entire VM. Furthermore, NGT facilitates the creation of application-consistent snapshots by interacting with the Windows Volume Shadow Copy Service (VSS), which is often a prerequisite for high-integrity backups of Tier-1 applications like SQL Server or Exchange. By installing NGT, the VM is granted the intelligence to browse and attach historical vDisks, effectively enabling the SSR workflow and reducing the operational burden on the infrastructure team for simple file recovery requests.

NEW QUESTION # 55
Which two Data Protection technologies are compatible with Self-Service Restore? (Choose two.)

• A. Volume Group manual snapshot
• B. Async replication schedules
• C. Synchronous data replication
• D. Nearsync hourly recovery points

Answer: B

Explanation:
Self-Service Restore (SSR) is a Nutanix guest-level feature that empowers users to mount snapshots as local drives to recover individual files without administrative intervention. For SSR to function, the underlying data protection mechanism must support the specific metadata and disk-attachment hooks required by Nutanix Guest Tools (NGT). Asynchronous (Async) replication schedules are a primary supported technology for SSR because they create standard, persistent recovery points that are easily indexed by the SSR agent within the guest OS. While the question asks to " Choose two, " it is important to note that Nutanix also generally supports SSR for Synchronous replication (Option C), as both methods produce the point-in-time vDisk snapshots necessary for the mounting process.
Conversely, certain high-frequency technologies like NearSync (at very low RPOs) or complex storage entities like Volume Groups (VGs) have historically faced limitations with the SSR mounting workflow due to the way metadata is handled or how disks are presented to the hypervisor. In a production environment, an administrator must ensure that NGT is fully functional on the VM and that the VM is part of a compatible Protection Policy to enable the SSR " snapshot-to-drive " mapping. This capability is essential for balancing operational efficiency with user-led data recovery, as it offloads simple " deleted file " requests from the infrastructure team while leveraging the existing BCDR snapshot architecture.

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

Answer: D

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 # 57
An administrator managing critical VMs has been tasked with designing a Disaster Recovery solution where the VMs are brought up on the target cluster if the source cluster experience any issues. The failover needs to be triggered without any user intervention and with minimal downtime. What automatic failure execution solution is best suited?

• A. Synchronous Protection policy and no witness VM
• B. Synchronous Protection policy with witness VM
• C. Asynchronous Protection policy with witness VM
• D. Nearsync Protection policy and no witness VM

Answer: B

Explanation:
To achieve the goal of " minimal downtime " and " no user intervention, " a zero-RPO solution with automated failover capabilities is required. In the Nutanix ecosystem, this is accomplished through Synchronous Replication. Unlike Asynchronous or NearSync replication, which rely on snapshot intervals and manual failover triggers, Synchronous replication ensures that data is written to both the local and remote clusters simultaneously. This architecture provides the foundation for zero data loss during a site failure.
However, the " automatic " part of the requirement is fulfilled by the addition of a Witness VM. Without a Witness, a secondary cluster cannot independently determine if the primary cluster has actually failed or if there is merely a network partition. In a " no witness " scenario (Option C), the secondary cluster stays in a passive state to prevent " split-brain " data corruption, requiring an administrator to manually promote the storage. By deploying a Witness VM at a third, independent site, the secondary cluster can communicate with the Witness to " acquire the lock " on the protection domain. Once the Witness confirms the primary site is unreachable, the orchestrator automatically promotes the secondary container and powers on the VMs. This combined solution of a Synchronous Protection Policy and a Witness VM provides the highest level of availability and the fastest possible recovery without requiring human action during the disaster event.

NEW QUESTION # 58
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. Create a new Protection Domain and import the snapshots.
• B. Select the Protection Domain and click Migrate.
• C. Restart the local Cerebro service and wait for the VMs to power on.
• D. Select the Protection Domain and click Activate.

Answer: C

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 # 59
Recently, several new VMs were deployed as part of an application expansion. Within 24 hours, the administrator notices no recovery points are being created for the new VMs.
During investigation, the administrator observes:
* Existing VMs in the Protection Policy continue to replicate successfully.
* No replication task failures are reported.
* Network connectivity between clusters is healthy.
* Storage capacity at the remote site is sufficient.
* The Protection Policy uses category-based entity selection.
* The newly deployed VMs were provisioned by a separate team.
What is the most likely root cause of the issue?

• A. The replication schedule must be changed to Nearsync.
• B. Snapshot retention settings are too low.
• C. The new VMs were not added to the required category.
• D. The recovery plan must be recreated.

Answer: C

Explanation:
Nutanix Disaster Recovery (formerly Leap) utilizes a " policy-driven " approach where virtual machines are protected based on assigned " Categories " rather than individual VM names. This allows for automated protection: any VM tagged with a specific category (e.g., App:Web) is automatically picked up by the associated Protection Policy. When existing VMs are replicating fine but new ones are not, and there are no network or storage errors, the root cause is almost always an administrative oversight during provisioning.
If the separate team that deployed the VMs followed a checklist that didn ' t include category assignment, those VMs exist as " unprotected entities " in the eyes of Prism Central. The Protection Policy will ignore them because they do not match the entity selection criteria defined in the policy ' s configuration. To resolve this, the administrator must simply apply the correct category to the new VMs. Once tagged, the Cerebro service will identify the new members during its next scan and initiate the initial full seed replication to the recovery site. This scenario highlights the critical need for cross-team coordination and the use of automated deployment tools (like Nutanix Self-Service or Calm) to ensure that security and BCDR requirements are applied consistently during the VM lifecycle.

NEW QUESTION # 60
......

NCP-BC-7.5 PDF Dumps Are Helpful To produce Your Dreams Correct QA's: https://examtorrent.actualcollection.com/NCP-BC-7.5-exam-questions.html