Nutanix NCP-MCI-7.5 - Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) 7.5

Nutanix DR documentation for volume groups distinguishes replication types by RPO range. Nutanix documents Asynchronous Replication as the model for 1 hour or more RPO, while NearSync covers 1 minute to 15 minutes, and synchronous/Metro designs target near-zero or zero-RPO behavior with tighter latency expectations. Since the requirement here is 1 hour and the clusters are in different geographic regions, Asynchronous is the correct fit. That makes D the right answer.

The geography in the question is also a clue. Synchronous and Metro Availability are usually associated with low-latency links and more demanding network requirements, which are not implied by “different geographic regions.” NearSync is too aggressive for a 1-hour target and is documented for much shorter RPO windows. Nutanix’s own replication taxonomy places 1 hour or more squarely in the Asynchronous category, so D is the authentic answer.

When Prism Central is scaled out for resiliency, the design goal is not only to have multiple Prism Central VMs, but also to ensure they are not placed together in a way that creates a common point of failure. Nutanix documentation around anti-affinity policies explains that VM-VM anti-affinity is used to keep selected VMs from running on the same host. In a scaled-out Prism Central deployment, this placement separation is the logical next step to strengthen resiliency, because it prevents the Prism Central instances from collapsing onto the same physical host and failing together during a node outage. ( Nutanix )

The other options are either unrelated or not the primary required follow-up. Witness Service is associated with Metro Availability and DR designs, not with the baseline requirement of distributing Prism Central VMs after scale-out. Protection Domain protection may be useful in some cases, but it does not solve co-location risk. HA reservations on the hosting Prism Element cluster address restart capacity, not placement diversity. The most direct resiliency improvement after scaling out Prism Central is to enforce separation between the Prism Central VMs. That is why D is the best answer. ( Nutanix )

Nutanix documents Logbay as the preferred and supported mechanism for efficient platform log collection. The AHV administration guide states that you can use Logbay only after the CVM is installed on the node or the AHV compute node has been added to the cluster, which directly matches the wording in option A. Nutanix’s web-console guidance also points administrators toward Logbay as the preferred collection method rather than relying only on manual UI collection.

The other options describe tools or behaviors that do not match Nutanix’s documented collection path for this scenario. Panacea is not the standard answer for supported cluster log-bundle collection in the way described. Storage policy reports are not substitutes for host/CVM diagnostic logs, and ADS does not function as an automatic diagnostic bundle exporter for arbitrary contention events. Because the question asks for both the supported approach and a key prerequisite, Logbay with the documented availability condition is the most precise Nutanix answer. Therefore A is correct.

A required RPO of 5 minutes immediately points to NearSync replication, because Nutanix documents NearSync protection policies as supporting recovery points in 1–15 minute intervals. The second requirement—automatically protect new mission-critical VMs—points to a Protection Policy approach in Prism Central, because protection policies can use categories and policy-based assignment to scale protection dynamically as new matching VMs are added. Combining those two requirements makes Protection Policy with NearSync replication the correct answer. ( Nutanix )

Protection Domains can support NearSync in older or alternate workflows, but the phrase “new mission critical VMs should be automatically protected” is the clue that pushes this question toward policy-based protection rather than manually maintained membership. Asynchronous replication also fails the first requirement because its RPO target is not the 5-minute class represented by NearSync. Nutanix’s modern DR design encourages policy-driven protection for scalable, category-based administration. Therefore B is the best fit for both the RPO and automatic-inclusion requirements. ( Nutanix )

Nutanix guidance for compression settings and current container behavior aligns with inline compression as the standard default, with an immediate (0-minute) delay model. Nutanix compression FAQ guidance also states that when deploying compression on a container, the recommended default delay for inline compression is 0, reinforcing the expected default posture for new storage containers. That makes A the correct answer. ( Nutanix )

This is one of those questions where older platform knowledge can cause confusion because historical versions and terminology evolved. The safest exam-oriented approach is to follow the current documented behavior and Nutanix’s own recommended default delay. Post-process compression with 60 minutes used to be a common mental model in older storage discussions, but the modern expected answer for a newly created container in Prism Central is inline compression with a 0-minute delay. Therefore A is the right choice. ( Nutanix )

For CHAP-protected volume groups, Nutanix documentation is explicit that when the target password is changed, the administrator must also update the associated recovery plan. Nutanix states that if the new target password is not updated in the recovery plan, it is not retained after failover. That makes the recovery plan the place where the failover-side credential continuity is preserved. In other words, protection policies create and replicate recovery points, but the recovery plan contains the information needed for the recovered application workflow, including CHAP details needed after recovery. ( Nutanix Portal )

This is an important exam distinction: protection policy controls snapshot and replication behavior, while recovery plan controls recovery orchestration and the settings needed when workloads are actually brought online at the target site. Recovery points themselves are snapshots of protected entities; they are not the administrative mechanism Nutanix documents for persisting an updated CHAP target password through failover. So even though the uploaded file says option D, the official Nutanix guidance supports A. For failover success with CHAP-enabled VGs, always synchronize password changes with the recovery plan. ( Nutanix Portal )

Nutanix security hardening guidance explains that SSH Whitelisted Addresses control which client IPs are allowed to reach the CVM over SSH. If IP restriction is enabled and the new jump box is not on the allowlist, the SSH connection is expected to be refused. In that locked-down state, the correct recovery path is to access the CVM through a local or serial console and update the whitelist to include the new jump box IP. That makes C the correct answer. ( portal.nutanix.com , portal.nutanix.com )

Cluster Lockdown disabling password-based SSH is not the same setting as the SSH allowlist. Prism Central security views can help with visibility, but the key documented mechanism is the whitelist itself. Restarting the CVM does not reset the hardened configuration. Nutanix’s intent is that trusted-source access must be explicitly permitted, and once it is blocked, you need console-level access to make the change safely.

Nutanix documentation for Windows VM creation on AHV clearly states that when deploying the Nutanix VirtIO ISO for a VM using Secure Boot and UEFI, the SATA bus type must be used. Nutanix also documents that IDE is not supported when Secure Boot is enabled for UEFI mode, which reinforces the correct bus choice. This makes C. SATA the correct answer directly from the official procedure. ( Nutanix )

This is a compatibility question, not a performance question. It can be tempting to choose SCSI because it is common in virtual machine storage design, but Nutanix’s secure-boot provisioning guidance is explicit about the VirtIO ISO attachment method. The exam often checks whether the administrator remembers that the driver ISO itself has a required bus type in secure-boot scenarios. Since the supported method in the Nutanix documentation is to mount the VirtIO ISO on SATA, C is the correct answer. ( Nutanix )

Nutanix documentation and KB guidance for transferring virtual disks to AHV clearly state that when a source hypervisor such as ESXi needs temporary access to a Nutanix storage container, administrators should add the host IP address to the filesystem whitelist. That is the approved mechanism for allowing the source host to mount or access the container for migration purposes. This makes D the correct answer. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

The wording “setup as an NFS share” is too generic and is not the exact Nutanix administrative step. Nutanix storage containers are not meant to be treated as open general-purpose file shares. Importing the ESXi host into AHV is not the workflow here, and per-user NFS authentication is not the key control being tested. The precise and supported action is to allow the ESXi host through the Filesystem Whitelist.