The Nutanix ECA course covers migration options for VMs in multi-cluster environments, particularly when minimizing downtime is critical, such as during scheduled maintenance. The scenario involves two identical clusters with guest VMs using pass-through GPUs, managed by separate Prism Central instances, requiring a migration method that ensures minimal disruption.
Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:
Module: VM Management, Section: Cross-Cluster Live Migration"Cross-Cluster Live Migration allows administrators to migrate VMs between clusters managed by different Prism Central instances with minimal downtime. This feature supports live migration of VMs with pass-through GPUs, ensuring continuous operation during maintenance activities." Module: Cluster Management, Section: Migration Strategies"For scenarios requiring minimal downtime, such as planned maintenance, Cross-Cluster Live Migration is the preferred method. It enables seamless VM migration across clusters, even those managed by separate Prism Central instances, while maintaining VM availability." Explanation of Options:
A). Run a Recovery Plan planned failoverThis is incorrect. A Recovery Plan planned failover is part of Nutanix's disaster recovery (DR) solution, used to execute failover for Protection Domains in scenarios like site failure. It is not designed for routine maintenance migrations and may involve downtime, especially for VMs with pass-through GPUs, as failover requires VM restart on the target cluster. The ECA course states:" Recovery Plans are used for DR failover, not for live migrations during maintenance, and may result in downtime." B). Use Cross-Cluster Live MigrationThis is the correct answer. Cross-Cluster Live Migration, introduced in later AOS versions, allows VMs to be migrated between clusters, even those managed by different Prism Central instances, with minimal downtime. The ECA course confirms that this feature supports VMs with pass-through GPUs, as the migration process preserves VM state and connectivity. This method is ideal for planned maintenance, ensuring VMs remain operational.
Supporting Extract:"Cross-Cluster Live Migration minimizes downtime by transferring VM state and data live, supporting complex configurations like pass-through GPUs, making it suitable for maintenance scenarios." C). Perform a Nutanix Move migration planThis is incorrect. Nutanix Move is a tool for migrating VMs from non-Nutanix environments (e.g., VMware or Hyper-V) to a Nutanix cluster, not for migrations between Nutanix clusters. It is not optimized for live migrations within a Nutanix environment and may involve downtime. The ECA course notes:"Nutanix Move is designed for external-to-Nutanix migrations, not for intra- Nutanix cluster migrations, and is not suitable for minimizing downtime." D). Migrate Asynchronous Protection DomainsThis is incorrect. Migrating Asynchronous Protection Domains involves replicating snapshots to a remote cluster for DR purposes, not live VM migration. This process is asynchronous, involves downtime during failover, and is not suitable for maintenance scenarios requiring minimal disruption. The ECA course clarifies:"Asynchronous Protection Domains are used for DR replication, not for live VM migration, and require VM restart during failover." Additional Context from ECA:
Cross-Cluster Live Migration: This feature leverages Nutanix's hypervisor-agnostic migration capabilities, ensuring that VMs with pass-through GPUs are migrated seamlessly. The process involves copying VM memory and state while keeping the VM running, minimizing downtime to seconds or less.
Maintenance Scenario: For scheduled maintenance, Cross-Cluster Live Migration ensures that VMs remain available, which is critical for GPU-intensive workloads that cannot tolerate extended downtime.
Supporting Reference from Web Results:
The Nutanix Support Portal (https://portal.nutanix.com) aligns with the ECA documentation:"Cross-Cluster Live Migration supports live VM migration between clusters, including those with pass-through GPUs, ensuring minimal downtime for maintenance tasks."

Nutanix storage container configuration guidance specifies that "Advertised Capacity" is the setting used to define a maximum limit for the container. This value enforces a hard cap on space usage. Reserved Capacity, in contrast, defines a minimum guarantee of space for the container and does not limit growth.
Prism Element is the correct interface for creating storage containers with specific data reduction settings such as compression and deduplication, as the container-level storage policies are applied directly at the cluster's storage layer.
The documentation further clarifies that RF1, inline compression, and deduplication settings are configured within Prism Element under container creation. Therefore, to enforce the 100 GiB limit, the administrator must create the container in Prism Element and set the Advertised Capacity to 100 GiB.

When Life Cycle Manager (LCM) reports thata newer framework version is available, thecorrect actionis toperform an inventory scan (Option C).
Performing an inventory scan updates the available firmware/software versionsand allows LCM to download required updates.
Option A (Run an AOS upgrade)is unrelated to the LCM framework update process.
Option B (Run an AHV upgrade)is a separate component update and does not affect the LCM framework.
Option D (Download manually from a CVM)is not necessary because LCM updates are automatically pulled after an inventory scan.
References:
Nutanix LCM User Guide #Updating LCM Framework and Performing Inventory Scans Nutanix KB #Best Practices for LCM Updates Nutanix Prism Central #LCM Update Workflow

Data-in-Transit Encryption ensures that replication traffic is encrypted while being sent over the internet.
* Option D (Enable Data-in-Transit Encryption) is correct:
* This encryptsreplicated data between clusters, ensuring security againstman-in-the-middle attacks.
* Option A (Self-encrypting drive) is incorrect:
* This protects data at rest, not during transmission.
* Option B (UEFI Secure Boot) is incorrect:
* Secure Boot prevents unauthorized OS modifications, but doesnot encrypt network traffic.
* Option C (Data-at-Rest Encryption) is incorrect:
* This encryptsstored data but does not secure replication traffic.
References:
* Nutanix Security Guide #Configuring Data-in-Transit Encryption
* Nutanix KB #Protecting Replication Traffic Over Public Networks