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 )

The error message is tied to resilience requirements. Nutanix documentation states that Replication Factor 3 requires at least five nodes so data remains online even if two nodes fail concurrently. If removing a node would drop the cluster below the minimum usable-node requirement, Nutanix blocks the operation. The safest and supported way to proceed during a hardware refresh is to add the replacement node first, restore compliant cluster capacity, and then remove the original node. ( Nutanix Portal ) The wrong answers all involve bypassing or weakening resilience inappropriately. Changing cluster or container RF to RF2 just to remove a node would reduce fault tolerance and is not the right answer for a SQL environment where resilience matters. Force-removal is also not the supported operational answer in a healthy refresh workflow. This question tests whether the administrator understands that node lifecycle actions are constrained by Nutanix fault-tolerance rules. When the cluster says it needs at least five usable nodes, the correct action is not to override the rule but to satisfy it by adding capacity first. Therefore A is the correct answer. ( Nutanix Portal )

Nutanix documentation for Prism Central point-in-time backup states that Prism Central supports up to 30 days of restore points for recovery. This is documented consistently across Nutanix guidance for backup to Nutanix Objects, AWS S3, and generic S3-compliant storage. Because the platform wording is explicit and repeated, the correct answer is 30 days. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com ) This is a retention-boundary question, so it is best answered directly from the official limit rather than from memory. The values 7, 14, and 90 days are exam-style distractors, but Nutanix's supported restore-point duration for Prism Central recovery is 30 days. In practical terms, that means administrators should plan their backup retention and operational expectations around that documented maximum rather than assuming indefinite or quarterly restore history.

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 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.