Nutanix describes a special process for updating golden images or templates without modifying the original source object directly. The documentation states:

“Complete Guest OS Update creates a temporary, cloned instance of the template, boots it, and allows administrators to patch or update the operating system. Once updates are applied, the system recomposes the template with the modifications.”

This process ensures that templates remain clean and version-controlled while still allowing regular OS patching operations. Other options such as Create VM from Template merely instantiate running VMs and do not update the template source. Update Guest OS and Update Configuration refer to VM-level settings but do not create a temporary working copy for template lifecycle management.

Thus, Complete Guest OS Update is the correct feature.

Nutanix storage architecture uses distributed data paths, where each vDisk represents a distributed logical object. The performance best practices for databases state:

“Multiple vDisks provide parallelism across the Nutanix storage stack, increasing I/O queue depth and distributing operations across multiple CVMs.”

Also, the guidance for Linux-based database workloads specifies:

“Using LVM striping across multiple vDisks increases throughput by merging multiple I/O channels and enhancing parallel read/write operations.”

Thin vs thick provisioning is irrelevant for performance in a Nutanix environment, as both types deliver identical I/O performance due to the metadata-driven storage engine.

Thus, database performance benefits from additional vDisks and striping across them.

Metro Availability requires that VMs always read data from their primary site to maintain optimal performance and prevent remote data access latency.

Option C (Migrate the VM to its primary site and set appropriate rules) is correct:

If a VMfails over to the secondary sitebut is still running in the primary site, it will read data remotely, causinghigh latency and performance issues.

The solution is tomigrate the VM back to the primary siteand configureDRS rulesorhost affinity settingsto prevent unwanted movement.

Option A is incorrect:

The command listsactive Metro Availability protection domainsbut doesnot resolvethe issue.

Option B is incorrect:

Must-affinity rules can help, but they should be configuredafter migrating the VM back to the primary site.

Option D is incorrect:

RunningNCC health checkswill onlydiagnose the issue, not resolve it.

Nutanix Protection Policies replicate VM data between clusters using Nutanix’s built-in data protection engine. For inter-site or cloud-based replication, Nutanix documentation specifies that replication traffic can be encrypted using the Data-in-Transit Encryption feature. The internal description states:

“Data-in-Transit Encryption secures replication traffic moving between clusters by encrypting data packets before transmission across external or untrusted networks.”

This is distinct from Data-at-Rest Encryption, which protects stored data on disks but does not secure network traffic. Self-encrypting drives and secure boot only protect the VM locally, not the replication path. Because replication to NC2 travels over the Internet, encryption of the transport channel is mandatory to meet security compliance.

Therefore, the required capability is Data-in-Transit Encryption.

In Nutanix Prism Central,categoriesallow administrators togroup and organize entitiesfor management, automation, and policy enforcement.

Alerts (Option B) can be categorizedto group similar system events and create filtering rules.

Virtual Machines (Option C) can be categorizedto apply security policies, automation tasks, and resource allocation rules.

Option A (Storage Containers) cannot be categorizedin Prism Central. Storage policies apply at the container level but are not managed via categories.

Option D (ISO Images) cannot be categorizedbecause ISOs arestatic objects, not active entities.