Nutanix Certified Professional - Business Continuity (NCP-BC) 7.5 Version: Demo [ Total Questions: 10] Web: www.dumpsleader.com Email: support@dumpsleader.com Nutanix NCP-BC-7.5 IMPORTANT NOTICE Feedback We have developed quality product and state-of-art service to ensure our customers interest. If you have any suggestions, please feel free to contact us at feedback@dumpsleader.com Support If you have any questions about our product, please provide the following items: exam code screenshot of the question login id/email please contact us at and our technical experts will provide support within 24 hours. support@dumpsleader.com Copyright The product of each order has its own encryption code, so you should use it independently. Any unauthorized changes will inflict legal punishment. We reserve the right of final explanation for this statement. Nutanix - NCP-BC-7.5 Valid Questions and Answers 1 of 7 100% Valid Questions - Guaranteed Success A. B. C. D. A. Category Breakdown Category Number of Questions Test Business Continuity and Disaster Recovery (BCDR) Solutions 2 Interpret and Configure Business Continuity and Disaster Recovery (BCDR) Requirements 2 Troubleshoot Business Continuity and Disaster Recovery (BCDR) Failures 5 Perform Business Continuity and Disaster Recovery (BCDR) Tasks 1 TOTAL 10 Question #:1 - [Test Business Continuity and Disaster Recovery (BCDR) Solutions] An administrator wants to run a test failover and maps the primary production virtual network to the recovery site production virtual network for the test. What are the two most likely outcomes? (Choose two.) Test failover can overlap with production networking and can lead to IP conflicts. Using production networks on recovery AZ for test failover provides the most accurate validation. It defeats the intended isolation between production and test workflows. Test failover does not require network mapping, so the selection of production or test networks will have no impact. Answer: A C Explanation The fundamental purpose of a " Test Failover " in Nutanix Disaster Recovery is to provide a non-disruptive way to validate the recovery process. During this test, virtual machines are cloned from their most recent snapshots and powered on at the recovery site. If an administrator incorrectly maps the " Test Network " to the actual " Production Network " (VLAN/Subnet) at the recovery site, they create two significant risks. First, this configuration can lead to immediate IP address conflicts. Because the test VMs have the exact same IP addresses as the live production VMs, having them active on the same logical production network will disrupt routing and potentially cause service outages for real users. Second, it defeats the " isolation " between production and test workflows. A valid DR test should occur in a " sandbox " where test applications can crash or exhibit errors without any possibility of affecting the live environment. By using the production network, the administrator is effectively running a " live " test on the production infrastructure, which is a dangerous violation of standard BCDR best practices. To avoid these outcomes, the administrator must map the test network to a dedicated, isolated VLAN or overlay network at the recovery AZ that has no physical or logical path back to the production segment. Question #:2 - [Interpret and Configure Business Continuity and Disaster Recovery (BCDR) Requirements] What is the bandwidth limit of a single Nutanix Cloud Gateway for IPSec traffic? 250 Mbps Nutanix - NCP-BC-7.5 Valid Questions and Answers 2 of 7 100% Valid Questions - Guaranteed Success B. C. D. A. B. C. D. 500 Mbps 1 Gbps 10 Gbps Answer: C 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. Question #:3 - [Troubleshoot Business Continuity and Disaster Recovery (BCDR) Failures] A Protection Domain exists with a VM, but no new snapshots are being created and replication never starts. Which is the most likely DR setup issue? The Protection Domain has no entities that are protected The Protection Domain has no schedule configured The remote site has no vStore mapping Bandwidth throttling is set too low Answer: B Explanation In a Nutanix legacy Protection Domain (PD) configuration, three primary elements must be in place for data protection to occur: the entities (VMs), the remote site (destination), and the schedule. Even if a VM has been added to a Protection Domain (negating Option A), the cluster will not take any action unless it is explicitly told " when " and " how often " to do so. Nutanix - NCP-BC-7.5 Valid Questions and Answers 3 of 7 100% Valid Questions - Guaranteed Success A. B. C. D. A. B. If no new snapshots are being created locally and replication is not starting, the most likely issue is that no " Schedule " has been configured for that Protection Domain. The schedule defines the RPO (e.g., hourly, daily) and the retention period for the snapshots. Without an active schedule, the Cerebro service simply has no instruction to initiate the snapshot process. While a missing vStore mapping (Option C) would cause the " replication " to fail, the " local snapshots " would still be created in the PD. Similarly, low bandwidth throttling (Option D) would cause the replication to move slowly or time out, but it would not prevent the initial creation of the local recovery points. Therefore, verifying the presence of a valid, active replication schedule is the mandatory first step for an administrator when a Protection Domain appears to be " idle " despite having VMs assigned to it. Question #:4 - [Test Business Continuity and Disaster Recovery (BCDR) Solutions] During a Test Failover, how can an administrator ensure that test VMs do not disrupt production? By using an isolated network By reconfiguring VMs IP addresses By powering off production VMs By changing MAC addresses Answer: A Explanation The primary purpose of a Test Failover is to validate the recovery process in a non-disruptive manner. When a VM is recovered from a snapshot during a test, it retains its original configuration, including its IP address and hostname. If this test VM were to be powered on on the same network as the live production VM, it would immediately cause a duplicate IP address conflict and potentially disrupt production services or trigger security alerts. To prevent this disruption, Nutanix Recovery Plans allow administrators to map the production network to a " Test Network " at the recovery site. This test network is typically an " Isolated " VLAN or overlay network that has no physical or logical route back to the production environment. By using an isolated network (Option A), the test VMs can boot up, run their internal services, and even communicate with other test VMs (if placed on the same isolated segment) without any risk of interfering with real users or databases. This allows the infrastructure team to verify that the " Recovered " state is functional while the " Primary " state continues to serve the business, fulfilling the core requirement of non-disruptive testing. Question #:5 - [Troubleshoot Business Continuity and Disaster Recovery (BCDR) Failures] A deployment uses native encryption for replication traffic between two clusters. An administrator subsequently enables network segmentation to isolate this traffic. Which specific maintenance step must be performed to ensure the encrypted replication functions correctly on the new segmented network? Manually add the new segmented IP addresses to the external firewall whitelist. Nutanix - NCP-BC-7.5 Valid Questions and Answers 4 of 7 100% Valid Questions - Guaranteed Success B. C. D. A. B. C. D. Update the IPSec VPN gateway configuration to include the new subnet range. Regenerate the Key Management Server (KMS) tokens for all self-encrypting drives (SEDs). Delete the existing certificates for Cerebro and Stargate services and restart the services. Answer: B Explanation Nutanix allows for the encryption of replication traffic " on the wire " using IPSec tunnels between clusters. When an administrator enables network segmentation for Disaster Recovery, the replication traffic is moved from the default management network to a new, dedicated subnet and set of virtual interfaces. Because the native replication encryption relies on IPSec gateways to secure the communication, the underlying VPN configuration must be aware of the network paths it is protecting. If the traffic is now originating from a new segmented subnet, the IPSec VPN gateway configuration at both the primary and recovery sites must be updated to include these new subnet ranges. If this step is missed, the encrypted tunnel will not recognize the segmented traffic as valid for the VPN, causing replication to fail even if the physical network is reachable. Regenerating KMS tokens (Option C) relates to data-at-rest encryption on physical drives, not traffic-in-transit. Restarting services (Option D) might be part of the general segmentation workflow, but the specific requirement for " encrypted replication " stability in this context is the alignment of the IPSec VPN policy with the new segmented network topology. Question #:6 - [Troubleshoot Business Continuity and Disaster Recovery (BCDR) Failures] 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? RTT is greater than 5 ms. Only one recovery plan exists. Reverse synchronization is disabled. Bandwidth is insufficient. Answer: D 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 Nutanix - NCP-BC-7.5 Valid Questions and Answers 5 of 7 100% Valid Questions - Guaranteed Success A. B. C. D. A. B. C. D. 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. Question #:7 - [Interpret and Configure Business Continuity and Disaster Recovery (BCDR) Requirements] What must the maximum Round Trip Latency be less than between a Witness VM and Metro Availability PDs? 5ms 100ms 200ms 500ms 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. Question #:8 - [Troubleshoot Business Continuity and Disaster Recovery (BCDR) Failures] An administrator recently expanded a Nutanix cluster by adding several new nodes. Shortly after, multiple backup jobs began failing. The following error is consistently reported: " Failed to perform backup: Cannot complete process ' iscsiadm --mode discovery --type sendtargets --portal X.X.X.X ' within timeout " . What is the most likely cause of the failure? Firewall ports 3502 and 3620 are missing to the new nodes. Firewall ports 3202 and 3206 are missing to the new nodes. Firewall ports 3302 and 3360 are missing to the new nodes. Nutanix - NCP-BC-7.5 Valid Questions and Answers 6 of 7 100% Valid Questions - Guaranteed Success D. A. B. C. D. Firewall ports 3205 and 3260 are missing to the new nodes. Answer: D Explanation Nutanix storage is often accessed by external backup solutions (like Veeam, Commvault, or HYCU) using the iSCSI protocol. This allows the backup server to mount snapshots and read data directly from the storage tier. The error message " iscsiadm... discovery... timeout " specifically indicates that the backup server ' s iSCSI initiator is unable to communicate with the Nutanix Data Services IP or the Controller VMs (CVMs) over the network. When a Nutanix cluster is expanded, it is essential that all networking and firewall configurations applied to the existing nodes are also applied to the new nodes. The iSCSI protocol relies on specific TCP ports: port 3260 is the standard port for iSCSI traffic, and port 3205 is often used for iSCSI discovery and metadata operations within Nutanix. If these ports are not open in the physical firewall or the host-based security rules for the newly added nodes, the backup server will be unable to discover the targets on those specific nodes, leading to the timeout errors . This highlights a common " Day 2 " operational trap: cluster expansion requires careful auditing of network security groups and firewall whitelists to ensure that external integrations— especially BCDR and backup services—continue to have uninterrupted access to the expanded storage fabric. Verifying and opening ports 3205 and 3260 for the new node IPs is the first step to resolving this timeout issue. Question #:9 - [Perform Business Continuity and Disaster Recovery (BCDR) Tasks] A mission-critical VM utilizing an NVIDIA vGPU profile for high-end graphical processing is replicated from a primary Nutanix cluster to a secondary disaster recovery site. After failover of a VM using an NVIDIA vGPU profile, the VM boots but hardware acceleration does not function. What action is required? Disable Nutanix Guest Tools (NGT) to prevent driver conflicts. Reinstall the guest operating system to recognize the new hardware ID. Increase the VM memory allocation to compensate for the lost GPU buffer. Manually update the vGPU configuration on the VM at the recovery site Answer: D Explanation Virtual GPUs (vGPUs) are hardware-dependent resources that are tied to specific physical GPU cards installed in the Nutanix nodes. While Nutanix Disaster Recovery can replicate the VM ' s virtual disks and general configuration, the specific mapping to a physical vGPU profile is often not automatically preserved across clusters due to potential differences in hardware availability or GPU generations at the recovery site. When the VM fails over and boots up at the secondary site, the guest OS may see the NVIDIA driver but will find that the " backed " hardware resource is missing or incorrectly mapped, leading to a failure in hardware acceleration. To resolve this, the administrator must manually edit the VM ' s hardware settings at the recovery site and re-assign a compatible vGPU profile from the local cluster ' s available GPU resources. This Nutanix - NCP-BC-7.5 Valid Questions and Answers 7 of 7 100% Valid Questions - Guaranteed Success A. B. C. D. post-failover cleanup task is essential for workloads like VDI (Virtual Desktop Infrastructure) or CAD applications that depend on GPU processing. Relying on NGT (Option A) or reinstalling the OS (Option B) will not fix the underlying missing hardware assignment in the hypervisor, highlighting the need for specialized knowledge when protecting VMs with specialized hardware pass-through or vGPU requirements. Question #:10 - [Troubleshoot Business Continuity and Disaster Recovery (BCDR) Failures] During routine monitoring, an administrator notices that replication from the primary Nutanix cluster to the recovery cluster has stopped. New recovery points are not being created, and the DR dashboard shows replication errors. Investigation reveals: The primary and recovery clusters are both online and healthy. Network segmentation was recently enabled to isolate replication traffic from other workloads. No recent changes were made to firewall rules, protection policies or RPO settings. Which action should the administrator take first to investigate the replication failure? Delete and recreate the protection policy to reset replication. Increase the RPO interval setting in order to reduce the replication load. Verify required ports are open and reachable between clusters. Perform a test failover at the recovery site. Answer: B Explanation In a Nutanix environment, replication health is heavily dependent on the available bandwidth and the consistency of the network path between the source and target sites. When replication fails following an infrastructure change like network segmentation, it often indicates that the system is unable to sustain the current data change rate over the new path. While verifying ports (Option C) is a logical infrastructure step, the provided answer emphasizes managing the replication load by increasing the Recovery Point Objective (RPO) interval. Increasing the RPO (e.g., from 1 hour to 4 hours) reduces the frequency of snapshot transfers, which can help determine if the replication engine (Cerebro) can successfully complete a transfer when given a longer window or reduced pressure. If increasing the RPO resolves the failure, the administrator can conclude that the network change introduced a bottleneck or limited throughput that is insufficient for the original " heavy " schedule. This diagnostic step helps differentiate between a total connectivity blackout and a performance-related failure caused by the newly implemented network segmentation. Once the baseline replication is restored at a higher RPO, the administrator can then proceed to optimize the network or firewall settings to support the more aggressive RPO requirements originally set by the business. About dumpsleader.com dumpsleader.com was founded in 2007. We provide latest & high quality IT / Business Certification Training Exam Questions, Study Guides, Practice Tests. We help you pass any IT / Business Certification Exams with 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. View list of all certification exams: All vendors We prepare state-of-the art practice tests for certification exams. You can reach us at any of the email addresses listed below. Sales: sales@dumpsleader.com Feedback: feedback@dumpsleader.com Support: support@dumpsleader.com Any problems about IT certification or our products, You can write us back and we will get back to you within 24 hours.