Pass the Nutanix NCP-MCI NCP-MCI-7.5 Questions and answers with CertsForce

Nutanix documentation describes guest customization profiles as reusable configuration settings that can be applied during VM deployment from a template and also during certain clone operations. For Linux-based cloud-init workflows, Nutanix explicitly shows that when deploying a VM from a template with Cloud-Init guest customization, administrators can apply or override the customization settings at deployment time. That makes option A the cleanest and most documentation-aligned answer. ( portal.nutanix.com , portal.nutanix.com )

Why not the others? Nutanix does support guided setup and clone scenarios, but the wording “create a VM template for reusability” points most strongly to the template deployment workflow rather than one-off cloning. Cloud-init is also the Nutanix-native customization method for Linux initialization at first boot, which makes it especially suitable for standardized reusable templates. So if the goal is simple repeatable management with a template-driven lifecycle, the correct point to apply the guest customization profile is when deploying a VM with Cloud-Init guest customization, which is A. ( portal.nutanix.com )

For database workloads, Nutanix documentation distinguishes between crash-consistent and application-consistent recovery points. If the Take App-Consistent Recovery Points option is not selected, the recovery point may capture storage in a crash-consistent state only. For transactional databases, that can lead to corruption, incomplete writes, or recovery issues after restore. Nutanix specifically documents that selecting the app-consistent option creates application-consistent recovery points; if you do not select it, the recovery points are crash-consistent. That makes D the most likely root cause. ( portal.nutanix.com , portal.nutanix.com )

The mention that NGT was checked is important because NGT participation is commonly part of quiesced and app-consistent protection workflows. A high RPO can increase data loss, but it does not by itself explain logical corruption inside the restored database. Category choice and roll-up schedule are also not the primary issue. Nutanix best practice for databases is to ensure application-consistent protection is enabled wherever supported. Therefore D is the correct answer.

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.