Online Access Free NCP-BC-7.5 Practice Test
| Exam Code: | NCP-BC-7.5 |
| Exam Name: | Nutanix Certified Professional - Business Continuity (NCP-BC) 7.5 |
| Certification Provider: | Nutanix |
| Free Question Number: | 112 |
| Posted: | Oct 21, 2026 |
An administrator is validating a newly created Recovery Plan and receives the following warning:
IP addresses xxx.xxx.xxx.xxx cannot be preserved/mapped for VM REPORTVM01.
IP addresses cannot be preserved/mapped for entities
IP might be already in use or will be used by some other VM for recovery. IP cannot be mapped.
Only one IP address can be preserved for a vNIC in an IP address management enabled network.
What can the administrator do to resolve this warning without changing the existing IP address assigned to the VM?
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?
An administrator has recently completed the initial configuration of Nutanix Disaster Recovery for a production environment. Protection Policies and Recovery Plans have been configured and validated by the senior infrastructure team.
The administrator has confirmed that the expected categories are correctly associated with both the Protection Policies and Recovery Plans. During a scheduled test failover, the administrator notices that several VMs are missing from the recovery.
The administrator reviews the environment and notes the following:
* The Protection Summary tab does not show any warnings or errors
* No replication tasks are currently ongoing
* The missing VMs were all deployed within the last two weeks as part of a new application rollout
* The missing VMs are running on the same cluster as other VMs that recovered successfully during the test failover
* The application team followed the standard VM deployment checklist but did not coordinate with the infrastructure team during provisioning Given this information, what is the most likely cause of the missing VMs?
How does the system behave if the network cannot sustain the data change rate required to maintain a 1- minute RPO between the primary and recovery AZs?