NCP-MCI-6.10 Questions and Answers

When synchronous replication has been configured and a planned failover is required for datacenter maintenance, Nutanix recommends performing aplanned failoverto ensure data consistency and a clean transition of services.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“A planned failover ensures that data replication is complete and consistent between the primary and standby sites before the workload is migrated. This prevents data loss and ensures seamless recovery.”

Additionally:

“A planned failover can be initiated either from the primary site or from the standby site. This provides flexibility depending on operational preferences and site availability during maintenance windows.”

“Unplanned failovers should only be used in the event of unexpected site outages or catastrophic failures, as they may involve data loss or incomplete synchronization.”

Therefore, the correct approaches are to conduct a planned failover either from the standby site (B) or from the primary site (D). This ensures seamless workload transition during the datacenter maintenance event.

When a node is placed intoMaintenance Mode, Nutanix follows a structured process to ensureservice continuity and data integrity.

Option B (All eligible VMs on the host are migrated to other hosts) is correct:

Live Migration automatically moves VMs to other hoststo avoid downtime.

This ensures workloads remain operational during maintenance.

Option D (Non-migratable VMs are powered off) is correct:

Some VMs, such as those usingGPU pass-through or local storage dependencies,cannot be live-migrated.

These VMsmust be powered offbefore placing the host into Maintenance Mode.

Option A is incorrect:

Non-migratable VMs are not automatically restarted on other hosts—they remain powered off until manually restarted.

Option C is incorrect:

Eligible VMs are live-migrated, not powered off.

Multicast traffic can generate unnecessary overhead if it is not properly managed.IGMP Snooping (Option C)ensures thatmulticast packets are only sent to VMs that have requested them, rather than broadcasting to all VMs.

Option C (IGMP Snooping) is correct:

Itreduces unnecessary multicast trafficby ensuring that only subscribed VMs receive the packets.

It is supportednatively in AHV networking.

Option A (LACP) is incorrect:

Link Aggregation Control Protocol (LACP)improves bandwidth and redundancy but doesnot control multicast traffic.

Option B (UDP) is incorrect:

UDP (User Datagram Protocol) is a transport protocol, not a network optimization feature.

Option D (Network Segmentation) is incorrect:

Segmentation (VLANs, VPCs) isolates networksbut does not optimizemulticast traffic specifically.

The Nutanix Enterprise Cloud Administration (ECA) course provides detailed guidance on managing images in a multicloud environment, particularly when administering multiple clusters across different geographic sites via a single Prism Central instance. The goal of optimizing image uploads to all locations involves ensuring efficient image availability, minimizing latency, and balancing storage and network resource usage. The ECA course emphasizes the use ofImage Placement Policiesto control how images are distributed and stored across clusters registered with Prism Central.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Image Management, Section: Image Placement Policies"Prism Central allows administrators to manage images centrally for multiple clusters. Image Placement Policies define how images are distributed to clusters. A policy with Soft Enforcement ensures that images are uploaded to a preferred cluster and replicated to other clusters as needed, optimizing for network efficiency and availability while allowing flexibility if a target cluster is unavailable."

Module: Prism Central Management, Section: Multi-Cluster Image Management"For environments with clusters at different geographic sites, an Image Placement Policy with Soft Enforcement is recommended to optimize image uploads. This policy allows Prism Central to select a primary cluster for image storage and replicate the image to other clusters based on demand, reducing unnecessary uploads while ensuring images are available where needed."

Explanation of Options:

A. Image Placement Policy with Soft EnforcementThis is the correct answer. The ECA course highlights that anImage Placement Policy with Soft Enforcementis designed to optimize image distribution in multi-cluster environments, especially across geographic sites. With Soft Enforcement, Prism Central uploads the image to a designated cluster (e.g., the closest or most available) and replicates it to other clusters as needed, based on workload requirements or VM deployment demands. This approach minimizes redundant uploads, reduces network congestion, and ensures images are available efficiently across sites. The "soft" aspect allows flexibility—if a target cluster is offline or has insufficient storage, Prism Central can select an alternative cluster, ensuring operational continuity.

Supporting Extract:"Soft Enforcement allows Prism Central to prioritize a primary cluster for image storage but permits fallback to other clusters if the primary is unavailable, optimizing upload efficiency and image availability across multiple sites."

B. Custom Image Upload RoleThis is incorrect. The ECA course does not define a "Custom Image Upload Role" as a feature in Prism Central for optimizing image uploads. While Prism Central supports role-based access control (RBAC) for managing permissions, including image management, these roles govern who can upload or manage images, not how images are distributed or optimized across clusters. The ECA materials state:"RBAC in Prism Central allows administrators to assign permissions for image management, but it does not influence the placement or optimization of image uploads."This option is irrelevant to the question’s focus on optimizing image distribution.

C. Bandwidth Throttling PolicyThis is incorrect. While bandwidth throttling can regulate network usage during data transfers (e.g., during replication or migration), it does not directly optimize image uploads for availability or efficiency across multiple clusters. The ECA course mentions bandwidth throttling in the context of data protection and replication:"Bandwidth Throttling Policies can be applied to replication schedules to manage network usage, but they are not used for image placement or upload optimization in Prism Central."Throttling could even slow down image distribution, counteracting the goal of optimization, especially in a multi-site scenario.

D. Image Placement Policy with Hard EnforcementThis is incorrect. AnImage Placement Policy with Hard Enforcementstrictly mandates that images be uploaded to specific clusters as defined in the policy. If the designated cluster is unavailable (e.g., due to network issues, storage constraints, or downtime), the upload fails, which can disrupt operations in a multi-site environment. The ECA course notes:"Hard Enforcement ensures images are only stored on specified clusters, but this can lead to upload failures if the target cluster is offline or lacks capacity, making it less suitable for geographically distributed environments."This rigidity makes Hard Enforcement less optimal compared to Soft Enforcement, which provides flexibility and ensures image availability.

Additional Context from ECA:

Image Management Workflow: The ECA course explains that Prism Central’s Image Service centralizes image management for all registered clusters. When an image is uploaded, the Image Placement Policy determines where it is stored and how it is replicated. For geographically dispersed clusters, Soft Enforcement balances efficiency and availability by prioritizing a primary cluster (e.g., based on proximity or storage capacity) while allowing replication to other clusters as needed for VM provisioning or workload deployment.

Extract:"In multi-site deployments, Soft Enforcement optimizes image uploads by reducing redundant data transfers and ensuring images are accessible across clusters without requiring manual intervention."

Practical Consideration: In a multi-site scenario, network latency and storage availability vary across clusters. Soft Enforcement allows Prism Central to adapt dynamically, ensuring images are uploaded to a viable cluster and replicated efficiently, which aligns with the goal of optimization.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) reinforces the ECA documentation: "Image Placement Policies in Prism Central streamline image management across clusters. Soft Enforcement is ideal for multi-site environments, as it allows flexible image placement and replication, ensuring efficient uploads and availability."This confirms that Soft Enforcement is the recommended approach for optimizing image uploads in a multi-cluster, multi-site setup.

Nutanix storage containers allow administrators to configure capacity reservations and advertised limits for better resource management.

Option D (Set Reserved Capacity to 10 GiB and Advertised Capacity to 500 GiB) is correct:

Reserved Capacityensures that10 GiB is always available for this container and not consumed by other containers.

Advertised Capacitydefines alogical limit of 500 GiBto prevent over-allocation.

Option A is incorrect:

Advertised Capacity of 10 GiB is too lowand does not match the requirement of a500 GiB storage container.

Option B is incorrect:

Only setting Advertised Capacity does not guarantee Reserved Capacity, meaning other containers could consume the reserved space.

Option C is incorrect:

Setting only Reserved Capacity does not enforce an upper limit, which could lead to overprovisioning.

In Nutanix Protection Domain-based replication, both thesourceanddestinationstorage containersmust have the same Replication Factor (RF)to ensure consistent data protection and replication. This is a key requirement for the data’s protection and integrity.

From theNutanix ECAdocumentation:

“Replication and recovery require that the source and destination containers have the same RF setting (either RF2 or RF3). If the RF does not match, replication and recovery points will not be generated in the DR site.”

The other options:

A (NGT): NGT is not required for crash-consistent protection.

C (Windows updates): Updates are not directly relevant to replication consistency.

D (container name): Names can differ; what matters is the container’s RF setting.

By default, Nutanix Prism Central retains the last 10 instances of a report if no retention policy is configured.

Option B (10) is correct:

Nutanixstores up to 10 reports, after which older reports areautomatically deleted.

Options A (5), C (15), and D (20) are incorrect:

Whileretention policies can be customized, thedefault setting is 10 reports.

The Nutanix ECA course provides guidance on performance monitoring and troubleshooting for VMs, including metrics to analyze when determining whether additional vCPUs are needed. The scenario involves a VM experiencing performance issues, with the cluster performing well overall, suggesting the issue is VM-specific.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Performance Monitoring, Section: VM Performance Metrics"To determine if a VM requires additional vCPUs, analyze VM CPU Usage and VM CPU Ready Time. High CPU Usage indicates the VM is under heavy load, while high CPU Ready Time suggests the VM is waiting for CPU resources, both justifying additional vCPUs."

Module: Troubleshooting, Section: VM Performance Issues"When a VM experiences performance issues, VM CPU Usage and VM CPU Ready Time are critical metrics. CPU Usage shows demand, while CPU Ready Time indicates contention or scheduling delays, helping determine if more vCPUs are warranted."

Explanation of Options:

A. VM CPU UsageThis is correct. VM CPU Usage measures the percentage of CPU resources the VM is consuming. High CPU Usage (e.g., consistently above 80–90%) indicates that the VM is under heavy load and may benefit from additional vCPUs to handle the workload. The ECA course emphasizes:"VM CPU Usage is the primary metric to assess whether a VM’s CPU allocation is sufficient for its workload."

B. VM CPU Ready TimeThis is correct. VM CPU Ready Time measures the time a VM is ready to run but waiting for CPU resources from the hypervisor due to contention or oversubscription. High CPU Ready Time (e.g., above 5–10%) suggests that the VM is not getting enough CPU cycles, and adding vCPUs could alleviate the issue. The ECA course notes:"High VM CPU Ready Time indicates CPU contention, often resolved by adding vCPUs or optimizing resource allocation."

C. Host Memory Swap Out RateThis is incorrect. Host Memory Swap Out Rate indicates memory pressure on the host, causing memory pages to be swapped to disk. While this can affect VM performance, it is unrelated to CPU performance and does not justify adding vCPUs. The ECA course states:"Host Memory Swap Out Rate is relevant for memory-related issues, not CPU allocation decisions."

D. Host CPU UsageThis is incorrect. Host CPU Usage measures the overall CPU utilization of the host, not the specific VM. Since the cluster is performing well overall, high Host CPU Usage is unlikely, and it does not directly indicate whether the VM needs more vCPUs. The ECA course clarifies:"Host CPU Usage is a cluster-wide metric and less relevant for diagnosing VM-specific CPU performance issues."

Additional Context from ECA:

Performance Monitoring Tools: In Prism Element or Prism Central, VM CPU Usage and CPU Ready Time can be monitored underVM > Monitoror through dashboards. These metrics provide insight into the VM’s CPU demand and contention.

Adding vCPUs: The ECA course advises caution when adding vCPUs, as over-allocation can increase CPU Ready Time due to scheduling overhead. However, if both CPU Usage and Ready Time are high, adding vCPUs is justified.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports: "For VM performance issues, analyze VM CPU Usage and CPU Ready Time to determine if additional vCPUs are needed, as these metrics directly indicate CPU demand and contention."

In a dark site deployment, LCM does not automatically fetch updates from the internet. The administrator must manually upload compatibility bundles.

Option B (The latest compatibility bundle has not been uploaded) is correct:

Thecompatibility bundlecontainsfirmware mappings, allowing LCM to detect the correct BIOS version.

Option A is incorrect:

AOSdoes not need to be upgraded firstfor a BIOS update.

Option C is incorrect:

TheBMC firmware does not always need updatingbefore BIOS updates.

Option D is incorrect:

In a dark site deployment,LCM does not rely on an internet connection, so webserver access is not required.

Storage Policies in Nutanix are applied through Categories, allowing policy-based automation and enforcement.

Option D (Assign the VM or VG to the same Category as the Storage Policy) is correct:

Nutanixapplies Storage Policies based on VM Categories, enablingflexibility in policy enforcement.

Option A is incorrect:

Storage Policies are not directly assigned at the VM or VG level—they apply through Categories.

Option B is incorrect:

Policies must be assigned toCategories, not directly to individual VMs/VGs.

Option C is incorrect:

Migrating to a storage container does not automatically apply a Storage Policy.

The Nutanix ECA course covers various methods for organizing and managing virtual machines (VMs) within a Nutanix environment, particularly in Prism Central. The question focuses on easily grouping a set of VMs, which requires a mechanism that is flexible, scalable, and straightforward to apply across multiple VMs for management, reporting, or policy application.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Prism Central Management, Section: Entity Organization"Tags provide a flexible way to group entities such as VMs in Prism Central. Tags are key-value pairs that can be assigned to VMs to categorize them for management, reporting, or policy enforcement. They are easy to apply and can be used to group VMs dynamically across clusters."

Module: VM Management, Section: Grouping VMs"To group a set of VMs for simplified management, Tags are the recommended approach. Unlike Categories, which are used for role-based access control and policy enforcement, Tags are lightweight and ideal for custom grouping without additional configuration overhead."

Explanation of Options:

A. Catalog ItemsThis is incorrect. Catalog Items in Nutanix are used within the Nutanix Calm or Marketplace to manage application blueprints or service offerings, not for grouping VMs. The ECA course states:"Catalog Items represent deployable applications or services in the Marketplace, not a mechanism for grouping existing VMs."They are unrelated to VM organization.

B. LabelsThis is incorrect. The term "Labels" is not used in Nutanix ECA documentation for grouping VMs. While Labels may be a generic term in other platforms, Nutanix uses "Tags" or "Categories" for similar purposes. The ECA materials do not reference Labels as a feature in Prism Central or Prism Element for VM grouping.

C. ProjectsThis is incorrect. Projects in Nutanix Prism Central are used to manage resources, users, and policies for a group of workloads, typically for multi-tenancy or resource allocation. While VMs can be associated with Projects, this involves additional configuration (e.g., assigning users, quotas, and policies) and is not the easiest way to group VMs. The ECA course notes:"Projects are used for resource governance and multi-tenancy, requiring additional setup compared to Tags for simple VM grouping."

D. TagsThis is the correct answer. Tags are lightweight, user-defined key-value pairs that can be applied to VMs in Prism Central to group them for management, monitoring, or reporting purposes. The ECA course emphasizes that Tags are easy to assign and manage, making them ideal for grouping VMs without the overhead of other mechanisms like Categories or Projects. Tags can be applied to multiple VMs at once and used in searches, dashboards, or scripts.

Supporting Extract:"Tags allow administrators to quickly group VMs by assigning custom key-value pairs, such as ‘Department: HR’ or ‘Environment: Production.’ They are ideal for ad-hoc grouping and can be leveraged in Prism Central for filtering and management tasks."

Additional Context from ECA:

Tags are managed in Prism Central under theEntities > Tagssection, where administrators can create, assign, and manage Tags for VMs and other entities. The ECA course highlights their simplicity:"Tags require minimal configuration and can be applied to VMs in bulk, making them the easiest method for grouping."

Unlike Categories, which are used for policy enforcement (e.g., security or placement policies), Tags are purely for organizational purposes, aligning with the question’s focus on ease of use.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) aligns with the ECA documentation: "Tags in Prism Central provide a simple and flexible way to organize VMs and other entities, enabling administrators to group resources for management or reporting without complex configurations."

The Nutanix ECA course provides detailed procedures for performing hardware upgrades, such as adding host memory, to ensure cluster stability and data availability. Upgrading host memory requires safely preparing the node to avoid disrupting running VMs or cluster operations.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Cluster Management, Section: Hardware Upgrades"Before performing hardware upgrades, such as adding host memory, the node must be placed into maintenance mode. This ensures that all VMs are migrated to other nodes and the host is safely isolated from cluster operations."

Module: Host Maintenance, Section: Maintenance Mode"Placing a node into maintenance mode is the first step for hardware upgrades. Maintenance mode migrates all VMs to other nodes, stops the Controller VM (CVM), and prepares the host for safe shutdown or hardware changes."

Explanation of Options:

A. Gracefully stop the host by using the out of band management interfaceThis is incorrect. Stopping the host via the out-of-band management interface (e.g., IPMI or iLO) without first entering maintenance mode risks disrupting running VMs and cluster services. The ECA course warns:"Shutting down a host without maintenance mode can cause VM crashes and data unavailability, as VMs are not migrated."

B. Remove node from the clusterThis is incorrect. Removing a node from the cluster is a permanent action that detaches it from the cluster’s metadata and storage pool, requiring re-imaging to rejoin. It is not appropriate for a temporary hardware upgrade like adding memory. The ECA course states:"Removing a node is not required for hardware upgrades and should be avoided, as it disrupts cluster configuration."

C. Execute "shutdown -h now" from the AHV command line interfaceThis is incorrect. Running shutdown -h now on the AHV host without entering maintenance mode will abruptly stop the host, potentially crashing VMs and disrupting cluster operations. The ECA course notes:"Directly shutting down a host via CLI without maintenance mode risks data loss and service disruption."

D. Place node into maintenance modeThis is the correct answer. Placing the node into maintenance mode is the first step for hardware upgrades, as it safely migrates all VMs to other nodes, stops the CVM, and prepares the host for shutdown or hardware changes. The ECA course emphasizes that maintenance mode ensures cluster stability during upgrades.

Supporting Extract:"To upgrade host memory, place the node into maintenance mode using Prism Element or the CLI command ncli host maintenance_mode. This ensures safe VM migration and host isolation."

Additional Context from ECA:

Maintenance Mode Process: In Prism Element, maintenance mode can be enabled underHardware > Host > Enter Maintenance Mode. The process automatically migrates VMs using live migration, stops the CVM, and isolates the host. For AHV, the CLI command is ncli host maintenance_mode id= enable=true.

Memory Upgrade: After entering maintenance mode, the host can be safely powered off to add memory, then powered back on and exited from maintenance mode.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) confirms: "Maintenance mode is the required first step for host hardware upgrades, ensuring VMs are migrated and the node is isolated before changes like memory upgrades."

Windows Defender Credential Guard requires UEFI firmware and Secure Boot to function properly.

Option B (Enable UEFI with Secure Boot) is correct:

Credential Guardrequires a UEFI-based boot moderather thanLegacy BIOS.

Secure Boot ensures only trusted OS components load, reducing attack surface for credential theft.

Option A (Update vCPU to 8) is incorrect:

Increasing vCPUs does not impactCredential Guard compatibility.

Option C (Use Windows Server 2022) is incorrect:

Windows Server 2019supports Credential Guard; upgrading to 2022 isnot required.

Option D (Update Memory to 16GB) is incorrect:

Credential Guard has no minimum RAM requirementbeyond general OS needs.

Understanding the Exhibit & Memory Allocation

Thehost has 128GB of physical RAM.

Thecurrent memory allocationacrossthree VMs (VM1, VM2, VM3) is 128GB, but only92GB is actually utilized.

This means there is36GB of unutilized memory available for allocation.

Step-by-Step Breakdown

Existing Memory Usage Before Adding VM4

Total Physical RAM:128GB

Used by running VMs (VM1, VM2, VM3):92GB

Unutilized Memory Available:36GB

After Creating and Running VM4

VM4 is allocatedmemory but only utilizes 28GB.

The table does not show VM4’s allocated RAM, but assuming it was given a reasonable allocation, it must have been taken from the36GB unutilized memory pool.

IfVM4 uses 28GB, theremaining unutilized memory is now (36GB - 28GB) = 8GB.

Maximum Memory Allocation for VM5

Sinceonly 8GB remains unutilized, the maximum memory VM5 can be allocated while still allowing it to power on is8GB.

Evaluating the Answer Choices

(A) 4GB❌(Incorrect)

More memory (8GB) is available, so limiting to 4GB is unnecessary.

(B) 8GB✅(Correct)

Theremaining unutilized memory after VM4 is 8GB, so VM5 can be allocated up to8GBwhile ensuring it can power on.

(C) 16GB❌(Incorrect)

Only8GB is left, so 16GB isnot possible.

(D) 32GB❌(Incorrect)

There isnot enough unutilized memoryto allocate 32GB.

Key Concept: Nutanix Memory Overcommit

Nutanix AHV supportsmemory overcommit, meaning VMs can be allocated more memory than physically available usingmemory ballooning and swapping.

However,to power on VM5 without impacting performance, it must fit within the available unutilized memory, which is8GB.

Storage Policies in Nutanix allow administrators to configuredata protection and performance settingsat thestorage container level.

Replication Factor (RF)definesthe number of copies of datastored across nodes for fault tolerance.

Encryptionensures thatdata at rest is protectedvia Nutanix-native encryption methods.

Option A (Storage Containers and Volume Groups)refers tostorage organization, not policies.

Option C (Shares and Object Stores)applies tofile and object storage services, not VM storage policies.

Option D (Data Protection and Security)is a broad term but does not definespecific policy attributes.

NutanixIntelligent Operations Reports(Option D) provideweekly summariesof cluster health, performance, and resource consumption.

These reports includerecommendations for optimization, alerts, and forecasted resource usage trends.

Option A (Admin Center LCM)managesfirmware and software upgradesbut does not generate weekly performance reports.

Option B (Prism Central Syslog)is used forlogging and event tracking, not performance summaries.

Option C (Infrastructure VMs List)provides astatic list of VMsbut does not generate periodic reports.

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.

TheBully VMs Listview in Prism Central’sIntelligent Operationsidentifies VMs that are consumingexcessive resources(CPU, memory, or storage IO) and causing resource starvation for other VMs.

From theNutanix ECA documentation:

“Bully VMs List identifies virtual machines with high resource consumption, enabling administrators to investigate and take action to prevent performance degradation in other VMs.”

The other options:

A (Constrained VMs): Shows VMs that are being starved of resources.

C (Inactive VMs): Shows VMs that are using little to no resources.

D (Overprovisioned VMs): Shows VMs with allocated resources beyond actual usage.

To ensureVM high availability (HA) in the event of a node failure, the administrator mustenable HA Reservation (Option B)in Prism Element.

High Availability (HA) in Nutanix ensures that VMs restart on another available node if the host they are running on fails.

Option A (Redundancy Factor 3)affectsstorage redundancy, not VM failover.

Option C (Protection Domains)is related todisaster recovery (DR), not local HA failover.

Option D (RF1 Storage Container)would reduce fault tolerance and is not recommended for production environments.

Enabling "Cluster Lockdown" in Nutanix is the best security measure to prevent password-based SSH logins.

Option C (Enable Cluster Lockdown) is correct:

Cluster Lockdowndisables password-based SSHandrequires key-based authentication.

Option A (Rename the nutanix user) is incorrect:

The Nutanix useris a system accountand cannot be renamed.

Option B (Block port 22) is incorrect:

This wouldprevent all SSH connections, includingkey-based logins, making administration difficult.

Option D (Delete the nutanix user) is incorrect:

Thenutanix useris required for system operations and cannot be removed.

For cross-hypervisor DR failover (e.g., ESXi to AHV), Nutanix Guest Tools (NGT) must be installed on VMs to ensure proper configuration and recovery.

Option D (NGT must be installed on source guest VMs) is correct:

NGTensures correct reconfiguration of VM devices and networking settingsduring failover.

Ithandles disk and driver reassignmentsbetween ESXi and AHV.

Option A (Utilize delta disks) is incorrect:

Delta disks are used insnapshot optimization, not DR failover.

Option B (Deploy Legacy BIOS boot) is incorrect:

AHV prefers UEFI boot mode, and Legacy BIOS is not a requirement.

Option C (Use raw device mappings) is incorrect:

RDMs areVMware-specificand arenot used in AHV failover scenarios.

LCM (Life Cycle Manager) fetches software updates from Nutanix’s repositories, requiring access to specific URLs.

Option A (download.nutanix.com) is correct:

This domainhosts all software update filesfor AOS, AHV, and other Nutanix components.

Option C (release-api.nutanix.com) is correct:

This domain is used forLCM to fetch update metadataand check for new versions.

Option B (mynutanix.com) is incorrect:

This domain is used foraccount management, not LCM updates.

Option D (portal.nutanix.com) is incorrect:

TheNutanix support portal is not used for automated LCM updates.

For workloads requiring new IP addresses and DNS server settings during DR recovery, using custom scripting within the Recovery Plan is the recommended and supported method.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Recovery Plans support scripting within the Recovery Sequence to enable administrators to perform post-recovery customization tasks, such as updating IP addresses, configuring DNS, or applying application-specific settings.”

“This scripting capability provides a flexible, automated approach to ensure that VMs are correctly reconfigured to operate within the DR environment’s network and DNS settings.”

This avoids the need for manual reconfiguration post-recovery or adjusting settings in production prior to failover.

https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Security-Guide-v6_10:mul-configure-data-in-transit-encryption-pc-t.html

"Ensure that port 2009 is open between the Prism Central instances for the KMS cluster to communicate."This is explicitly stated in the "Firewall rules for Data-in-Transit Encryption" section for Prism Central.

Technical Context:

Port 2009 is used by ZooKeeper (the coordination service for the KMS cluster) in Scale-Out Prism Central deployments.

DiTE in Prism Central relies on a dedicated KMS cluster that synchronizes encryption keys across PC instances using this port.

Firewall blocks on port 2009 break KMS quorum, preventing key exchange and causing DiTE to fail.