[Q78-Q96] Master 2026 Latest The Questions NCM-MCI and Pass NCP-MCI-6.10 Real Exam!

When usingFQDN instead of a Virtual IP in a scale-out Prism Central deployment, Nutanixenables load balancing across multiple Prism Central instances.
* Option A (Load balancing) is correctbecause it ensures that requests are distributedamong multiple Prism Central nodes, improving performance and redundancy.
* Option B (Resiliency) is incorrectbecause resiliency is achieved through HA and replication, not through FQDN configuration.
* Option C (Segmentation) is incorrectbecause network segmentation is handled at the VLAN or security policy level.
* Option D (SSL Certificate) is incorrectbecause SSL certificates can be applied regardless of whether FQDN or Virtual IP is used.
References:
* Nutanix Prism Central Deployment Guide
* Nutanix Best Practices for Scale-Out Prism Central
* Nutanix Support KB: Configuring FQDN for Prism Central

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.
References:
* Nutanix Prism Element Guide #Configuring HA Reservation
* Nutanix Bible #High Availability (HA) and Failover
* Nutanix Support KB #VM Recovery with HA Enabled

Nutanix Capacity Planning and Runway calculations analyze CPU, memory, and storage growth trends independently. The “Overall Runway” metric reflects the shortest runway across these three resources. The Capacity Planning documentation explains that “the scenario result may show the cluster in a healthy state if the most critical resource remains sufficiently available, even when the overall runway falls below longer- term thresholds.” Storage is often the dominant factor in determining long-term viability. If the storage runway remains strong, the system may indicate that the environment is in good shape even though the overall runway appears shorter due to CPU or memory projections. Because the question refers to the scenario still indicating a good cluster state, the most accurate interpretation is that storage runway remains healthy, and thus the system does not consider the cluster at risk.

The “nutanix” user is a system-level account required by the platform for internal operations, automation, cluster communication, and support access. It cannot be deleted or renamed. Nutanix security guidelines state:
“The correct method to prevent password-based SSH access for system accounts is to use Cluster Lockdown mode, which disables password authentication and enforces key-based access for all system-level CVM accounts.” Cluster Lockdown modifies SSH configuration across all CVMs, ensuring:
* password authentication is disabled
* only key-based authentication is permitted
* privileged system accounts such as ‘nutanix’ cannot log in interactively Blocking port 22 is not appropriate because it would block SSH entirely, including legitimate administrative access. The “nutanix” user cannot be renamed or removed due to system dependency.
Thus, enabling Cluster Lockdown is the proper Nutanix-approved method to remove password-based SSH access for system accounts.

Within Nutanix Recovery Plans, IP address transformations are handled through an automated mechanism known asIP Address Mapping. The documentation describes two methods: fixed mappings and offset-based mappings.
Offset-based mapping allows administrators to maintain consistent host identity attributes such as the last octet while shifting only the subnet portion during DR failover. The internal guidance states, “Offset-based mapping enables automatic recalculation of target IP addresses using offsets applied to source subnets, allowing preservation of host-specific octets across networks.” Custom scripts are possible but not recommended because Nutanix already provides a built-in, automated IP transformation system. Editing IPs inside VMs after failover is operationally expensive and defeats the purpose of an orchestrated DR workflow. IPAM is useful for dynamic IP assignment but does not preserve the last octet mapping requirement.
Thus, Offset-based IP mapping is the correct mechanism for this requirement.

Moving vDisks to a storage container with compression enabled ensures better data efficiency without downtime.
* Option A (Migrate vDisks) is correct:
* vDisk migration is non-disruptiveand allows compression settings to be applied dynamically.
* Option B (Recreate the VM) is incorrect:
* Rebuilding the VM is unnecessaryand would causedowntime.
* Option C (Migrate the VM) is incorrect:
* VM migration does not guarantee that only vDisks move, and it may disrupt performance.
* Option D (Recreate vDisk) is incorrect:
* This method ismanual and time-consuming, while Nutanix provides anautomated approach.
References:
Nutanix Storage Optimization Guide#Enabling Compression on Existing vDisks Nutanix KB#Migrate vDisks Between Storage Containers for Optimization

Nutanix AHV networking documentation explains that high-connection-count workloads can saturate a single network queue, causing receive-side bottlenecks. VirtIO-Net supports Multi-Queue with Receive-Side Scaling (RSS), allowing the VM to distribute packet processing across multiple vCPUs. The documentation states,
“Enabling RSS Multi-Queue improves performance for workloads handling a large number of simultaneous network flows by parallelizing packet handling.” Trunk mode does not solve per-queue packet processing limitations. Adding vNICs is not recommended because the bottleneck is at the queue level, not the number of interfaces. Using the e1000 adapter results in lower performance compared to VirtIO and is discouraged. Therefore, enabling RSS Multi-Queue is the correct performance optimization for a VM handling thousands of client connections.

TheBully VMs List (Option C)in Prism Central’sIntelligent OperationsidentifiesVMs consuming excessive CPU, memory, or storage, which negatively affects other VMs.
* Option A (Inactive VMs List)is used foridentifying unused VMsbut does not detect performance issues.
* Option B (Overprovisioned VMs List)helps identifyVMs with excessive allocated resources, but it does not focus on live performance impact.
* Option D (Constrained VMs List)highlightsVMs suffering from resource contention, not those causing it.
References:
* Nutanix Prism Central #Intelligent Operations and Performance Tuning
* Nutanix KB #Identifying and Managing Resource-Hogging VMs

The Nutanix data protection guide specifies that NearSync replication provides an RPO between 1 and 15 minutes, which is the lowest RPO available for standard asynchronous-based replication models. The documentation further states that NearSync is the supported method for achieving sub-hour RPO on one- and two-node clusters. Asynchronous replication has a minimum RPO of 60 minutes and therefore cannot be used for lowest RPO requirements. While scheduling intervals such as 1-15 minutes appear similar, Nutanix notes that these intervals are only achievable under the NearSync replication mode. Therefore, selecting NearSync is the required configuration to meet the goal of achieving the lowest RPO.

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.
References:
* Nutanix LCM Guide#Firewall Rules for LCM Connectivity
* Nutanix KB#Troubleshooting LCM Update Failures

Nutanix LCM architecture supports firmware, BIOS, BMC, disk controller, and drive updates only when the environment includes multiple nodes that can provide redundancy during the upgrade process. The LCM documentation specifies that firmware upgrades require node evacuation and rolling upgrade sequencing so that workloads remain available. A single-node cluster does not have node-level redundancy and therefore cannot support firmware upgrade operations that require putting a node into maintenance automatically. The guidance clearly states that “firmware upgrades are not supported for single-node clusters because the host cannot be safely placed into a maintenance mode during the LCM workflow.” LCM is supported for software inventory, but not for firmware activation on single-node clusters. This explains why no firmware updates appear in the LCM interface.

The Nutanix ECA course covers storage optimization techniques for Nutanix storage containers, particularly for workloads like persistent desktops, which require efficient capacity utilization due to their repetitive data patterns. Persistent desktops typically store user-specific data and configurations, making them ideal candidates for storage optimization techniques like compression, deduplication, or erasure coding. The question asks for the setting that provides thebest possible capacity savings.
Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:
Module: Storage Management, Section: Storage Optimization”Erasure Coding provides the highest capacity savings for workloads with large amounts of data, such as persistent desktops. By distributing data and parity across nodes, Erasure Coding reduces storage overhead compared to replication factor (RF) while maintaining fault tolerance.” Module: Storage Configuration, Section: Optimization for Virtual Desktops”For persistent desktop workloads, Erasure Coding is recommended to maximize capacity savings. It is more efficient than compression or deduplication alone, as it reduces the storage footprint by encoding data across nodes, making it ideal for environments with high data redundancy.” Explanation of Options:
A). Erasure CodingThis is the correct answer. Erasure Coding (EC-X) is a storage optimization technique in Nutanix AOS that distributes data and parity information across nodes, reducing the storage overhead compared to traditional replication factor (RF) settings. For persistent desktops, which often have large datasets with redundant patterns, Erasure Coding provides significant capacity savings by encoding data efficiently while maintaining fault tolerance. The ECA course highlights that Erasure Coding is particularly effective for workloads with cold or less frequently accessed data, which aligns with persistent desktop storage.
Supporting Extract:”Erasure Coding can achieve up to 50% or more capacity savings compared to RF=2 for workloads like virtual desktops, making it the most effective optimization for capacity-constrained environments.” B). Inline compression with a delay of 0 minutesThis is incorrect. Inline compression reduces data size in real- time as it is written to storage, but it provides less capacity savings compared to Erasure Coding for persistent desktops. Compression is effective for reducing the size of compressible data, but persistent desktops often benefit more from Erasure Coding due to their larger datasets and redundancy. Additionally, a delay of 0 minutes means compression occurs immediately, which may increase write latency without maximizing savings. The ECA course notes:”Inline compression is useful for general workloads but is less effective than Erasure Coding for high-capacity workloads like persistent desktops.” C). Inline Deduplication of Read CachesThis is incorrect. Deduplication removes duplicate data blocks, but
“Inline Deduplication of Read Caches” is not a standard Nutanix feature for storage containers. Nutanix supports inline and post-process deduplication, but these apply to data writes, not specifically to read caches.
Even if deduplication were applied, it would provide less capacity savings than Erasure Coding for persistent desktops, as deduplication depends on data similarity, whereas Erasure Coding optimizes storage across all data types. The ECA course states:”Deduplication is effective for workloads with high data similarity, but Erasure Coding provides broader capacity savings for large-scale desktop deployments.” D). Post Process DeduplicationThis is incorrect. Post-process deduplication analyzes and removes duplicate data after it is written, which can save capacity but is less efficient than Erasure Coding for persistent desktops. Deduplication requires significant data similarity to achieve savings, and its post-process nature delays optimization, potentially leading to temporary storage overuse. The ECA course clarifies:”Post-process deduplication is suitable for specific workloads, but Erasure Coding is preferred for persistent desktops due to its superior capacity efficiency and immediate applicability across nodes.” Additional Context from ECA:
Erasure Coding Details: Erasure Coding works by splitting data into fragments, adding parity information, and distributing these across nodes. For a storage container with persistent desktops, enabling Erasure Coding (e.g., with a stripe width of 4+2) can significantly reduce the storage footprint compared to RF=2 or RF=3.
The ECA course notes:”Erasure Coding is ideal for containers with large datasets, such as VDI environments, where capacity savings are critical.” Persistent Desktops: These desktops store user data and configurations, leading to large, redundant datasets.
Erasure Coding’s ability to optimize storage across nodes makes it the best choice for capacity savings, as confirmed by the ECA materials.
Supporting Reference from Web Results:
The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports the ECA documentation:” Erasure Coding (EC-X) provides the highest capacity efficiency for workloads like persistent desktops, reducing storage overhead by distributing data and parity across nodes, outperforming compression and deduplication in capacity-constrained environments.”

Nutanix uses IPv4 multicast for automatic node discovery and cluster expansion.
* Option D (IPv4 multicast must be allowed) is correct:
* When adding new nodes,the Nutanix Cluster automatically detects themusingIPv4 multicast traffic.
* If multicast isblocked at the switch level, the new nodeswill not be discoveredautomatically.
* Option A (Hypervisor version must match) is incorrect:
* While thehypervisor version should be compatible, itdoes not impact node discovery.
* Option B (IPv6 multicast) is incorrect:
* Nutanixdoes not use IPv6 multicast for cluster discovery.
* Option C (AOS version must match) is incorrect:
* Nodes can haveslightly different AOS versions, butdiscovery still works as long as they are compatible.
References:
* Nutanix Best Practices #Cluster Expansion & Auto-Discovery
* Nutanix KB #Why Nutanix Requires IPv4 Multicast for Node Discovery

Upgrading an AHV host with GPUs requires that the correct GPU drivers be manually uploaded to LCM, as GPU firmware is not updated automatically.
* Option C (Use Direct Uploads to upload appropriate driver bundles) is correct:
* LCM does notautomatically fetch GPU drivers.
* The administrator mustdownload and manually upload the appropriate firmware bundle before upgrading.
* Option A is incorrect:
* Agent VMs are not requiredfor GPU updates.
* Option B is incorrect:
* Running LCM indark site mode does not impact GPU firmware updates.
* Option D is incorrect:
* Updating NCCis a best practice but does not resolve GPU driver issues.
References:
* Nutanix LCM Guide#Manually Uploading GPU Firmware Bundles
* Nutanix KB#Updating AHV Hosts with GPUs

When usingFQDN instead of a Virtual IP in a scale-out Prism Central deployment, Nutanixenables load balancing across multiple Prism Central instances.
* Option A (Load balancing) is correctbecause it ensures that requests are distributed among multiple Prism Central nodes, improving performance and redundancy.
* Option B (Resiliency) is incorrectbecause resiliency is achieved through HA and replication, not through FQDN configuration.
* Option C (Segmentation) is incorrectbecause network segmentation is handled at the VLAN or security policy level.
* Option D (SSL Certificate) is incorrectbecause SSL certificates can be applied regardless of whether FQDN or Virtual IP is used.
References:
Nutanix Prism Central Deployment Guide
Nutanix Best Practices for Scale-Out Prism Central
Nutanix Support KB: Configuring FQDN for Prism Central

Data-in-Transit Encryption for Prism Central and CVMs requires specific internal communication ports to be open. Nutanix internal component documentation states:
“Port 2020 is used by the Nutanix encryption service for encrypted CVM-to-CVM communication during Data-in-Transit Encryption operations.” This port is essential for establishing secure tunnels between control-plane services. Ports 2009 and 2010 are used by other CVM services (e.g., Stargate, Curator coordination) but not for transport encryption. Port 9440 is for Prism UI/API traffic, and while it must be accessible for management, it does not enable encrypted back- end service traffic.
Thus, the administrator must ensure that port 2020 is permitted to enable Data-in-Transit Encryption functionality.

ForMetro Availability to work properly, the storage containers at both the primary and secondary sites must meet certain requirements:
* The storage containers must have the same name(Option D). This ensures that replication and failover work seamlessly. If the names do not match, the storage containers will not be listed as compatible.
* The destination storage container must be empty(Option C). Metro Availability requires a clean storage container at the secondary site to receive data. If the container already contains data, it cannot be used.
* Option A is incorrect: Different vendor hardware does not affect Metro Availability compatibility.
* Option B is incorrect: Compression does not affect Metro Availability compatibility. However, it is recommended to keep compression settings aligned between sites.
References:
* Nutanix Documentation: Metro Availability Deployment Guide
* Nutanix Best Practices for Metro Availability
* Nutanix KB 2093: Troubleshooting Metro Availability Storage Container Issues