Selected NCP-MCI-7.5 NCP-MCI Questions Answers

Here the uploaded answer key says C, but current Nutanix documentation says the opposite. Nutanix’s Live vDisk Migration Across Storage Containers documentation explicitly states that during an ongoing vDisk migration you cannot perform operations such as clone the VM, resize the VM, or take a snapshot. Nutanix also states, under DR considerations, that you should remove the VM from the protection domain or protection policy, migrate the vDisks, and then add the VM back afterward. That means the actions listed in option C are specifically blocked during vDisk live migration. ( Nutanix Portal )

Because all four answer choices are problematic against the current documentation, this is one of the questions I would flag as flawed in the source bank. The most accurate real-world Nutanix answer is: you should not perform snapshot, clone, resize, or DR policy/protection-domain operations during the migration. So although the uploaded key marks C, the official docs indicate that C is not actually allowed. For your final study document, this question should ideally be corrected or rewritten because the documented AHV behavior does not cleanly support any listed option as a valid “can perform during migration” task. ( Nutanix Portal )

Nutanix documentation confirms that Prism Element supports both NCC execution and log collection from the web console, so options A and B are incorrect. However, Nutanix also distinguishes running checks from collecting logs as separate actions. Operationally, if the administrator is actively running NCC at that moment, log collection is not available until that task is no longer in progress. That is why the most likely explanation is that logs cannot be collected while NCC is running. ( Nutanix )

This is a classic UI workflow question. Nutanix does allow log bundle collection from the web console, and newer NCC/Logbay capabilities even extend collection options further. But that does not mean every action is available concurrently. The supported mental model is: run checks, review output, then collect logs as needed. Since the question specifically says the administrator is running NCC and is not able to collect logs, the best explanation is the conflict between those two operations at the same time. Therefore, D is the correct answer. ( Nutanix )

Nutanix documentation for Performing Failover in PD-based DR includes the exact error message quoted in the question: “Protection domain is already active on source site ... Please trigger migrate from source site to activate the protection domain.” Nutanix shows this message when the protection domain is still active on the source cluster and the proper action is a planned migrate from the source, not an activate at the target. In other words, the source cluster is still reachable and authoritative, so trying to activate the protection domain on the other side is the wrong operation. That makes D the correct answer. ( Nutanix Portal )

This is a classic Nutanix DR distinction between planned migration and unplanned failover/activation. If the primary cluster is still available, Nutanix expects the administrator to use migrate from the source site. Activation at the destination is reserved for failover conditions when the source cannot safely coordinate the move. The error itself tells you the reason if you read it carefully: the protection domain is still active on the source site. Therefore the root cause is that the administrator is trying to activate the PD while the primary cluster is still reachable and still owns the active copy, which is exactly option D. ( Nutanix Portal )

Nutanix documentation for log collection in Prism Central and related Logbay guidance supports collecting logs for a specific time range, which is exactly what this question requires to minimize noise and capture only the relevant 30-minute incident window. Nutanix also documents that when sending logs to Nutanix Support FTP, the administrator can enter a support case number, allowing the bundle to be attached to the case without manual repackaging. That makes D the strongest answer: use the alert details to identify the impacted entities and timestamps, collect the logs for that time window, and upload them using the support-case workflow. ( Nutanix Portal )

The other options do not produce the right diagnostic artifact. Auto-resolve only affects alert state, not log quality. Tightening thresholds may generate more alerts, but it does not replace collecting platform logs. Exporting a CSV of alerts can help summarize incidents, but it is not the primary evidence Nutanix Support needs for performance troubleshooting. Nutanix’s supported model is very clear: identify the incident timing, collect the appropriate logs for that window, and upload the bundle in a support-compatible way. Therefore D is the authentic answer from a Nutanix troubleshooting workflow perspective. ( Nutanix Portal )