Nutanix NCA-7.5 - Nutanix Certified Associate (NCA) 7.5 Exam

A conventional five-node Nutanix HCI cluster has five Controller VMs—one CVM running on each node. AOS operates as a distributed storage and data-services system rather than relying on a single centralized storage controller. The per-node CVM architecture provides local access to the node’s storage devices while cooperating with the CVMs on the other nodes to form the distributed AOS storage fabric.

The CVMs collectively provide services associated with data placement, replication, metadata, caching, compression, deduplication, snapshots, and cluster storage management. If a CVM becomes unavailable, the host can access storage services through another CVM, subject to cluster health and connectivity. The remaining CVMs also maintain the distributed cluster services required for continued operation.

The number of CVMs therefore normally matches the number of HCI nodes: three nodes produce three CVMs, four nodes produce four, and five nodes produce five. The count does not represent the replication factor or the number of simultaneously tolerated failures.

Compute-only nodes are a specific exception because they do not run a CVM. However, the question explicitly describes a five-node HCI cluster, so each node contributes storage and runs a Controller VM.

NHCF/NCA reference: Nutanix HCI architecture, AOS, nodes, and Controller VMs. Official references: Infrastructure Resilience and Compute-Only Nodes .

Nutanix Data Services for Kubernetes (NDK) provides application-centric protection and data-management capabilities for stateful Kubernetes workloads. It is designed to protect persistent application data together with relevant Kubernetes configuration, allowing administrators to apply policies for snapshots, replication, recovery, migration, and disaster recovery. This includes persistent block volumes backed by Nutanix Volumes and, in supported releases, file-based persistent storage.

A generic replication policy does not by itself establish Kubernetes-aware protection. Effective recovery must account for both persistent data and application objects such as namespaces, StatefulSets, services, ConfigMaps, and secrets. NDK coordinates these elements and supplies policy-driven recovery workflows at the application level. Prism Central disaster-recovery capabilities primarily protect supported VM workloads and do not automatically provide the Kubernetes-native application awareness required here. Nutanix Objects replication protects object-store data and buckets rather than persistent block volumes consumed by containerized applications.

Nutanix describes NDK as extending enterprise data services to containerized applications and providing built-in disaster recovery with policy-driven data management. This directly matches the stated requirement. Reference: Nutanix Data Services for Kubernetes . NHCF alignment: recognizing Nutanix cloud-native products and matching NDK to stateful Kubernetes data protection.

===============

CPU Ready Time measures the percentage of time that a VM’s virtual CPUs are ready to execute but cannot be scheduled on physical CPU resources. It is therefore a direct indicator of processor contention or CPU oversubscription. A VM can show moderate CPU utilization while still suffering poor response times because its vCPUs are waiting for execution time.

Prism Central supports user-defined alert policies based on infrastructure metrics, including VM CPU Ready Time. The administrator can define a threshold and evaluation period so that an alert is generated when scheduling delays exceed an acceptable level during peak demand. This produces proactive notification instead of requiring periodic manual review.

Pulse sends diagnostic information to Nutanix Support but does not create the workload-specific threshold requested. Increasing vCPU allocation without first validating contention may worsen CPU Ready Time because the hypervisor must schedule additional virtual processors. Reviewing average CPU usage is retrospective and does not automatically generate an alert. The most precise control is therefore a custom CPU Ready alert. References: Prism Central 7.5 – Alert Metrics and Intelligent Operations – Chart Metrics .

===============

The VM’s memory-consumption line remains inside the blue baseline band, so its behavior falls within the learned baseline range. Prism Central uses historical observations and machine-learning analysis to establish the range of values normally expected for an entity and metric. The blue band represents that expected operating range; a value outside the band may be identified as anomalous, depending on duration and deviation.

The displayed value of approximately 42.95% is below 50%, which immediately invalidates option A. More importantly, memory-utilization percentage represents the portion of the VM’s allocated memory currently being consumed. It does not mean the host can provide only that percentage of the requested memory, so option C incorrectly interprets utilization as a resource-allocation failure.

The graph also does not provide sufficient evidence to halve the VM’s configured memory. Right-sizing requires longer-term utilization, swap activity, workload requirements, peak behavior, and operational policy—not a single observed percentage. Option D therefore recommends an unsupported configuration change.

The correct operational conclusion is limited and precise: the measured behavior is within the VM’s learned normal range and is not shown as an anomaly.

NHCF/NCA reference: Prism metrics, behavioral baselines, anomalies, and VM monitoring. Official references: Prism Central Metrics Tab and Cluster Details and Baseline Range .

===============

Nutanix Enterprise AI is specifically designed to simplify the deployment, management, validation, monitoring, and consumption of large language models. It provides an enterprise-grade interface for importing or selecting supported models, deploying inference endpoints, managing API access, testing model endpoints, and observing resource and endpoint behavior. Integration with sources such as NVIDIA NIM and Hugging Face further supports validated model deployment and controlled custom-model use.

Nutanix Intelligent Operations focuses on infrastructure visibility, capacity planning, optimization, anomaly detection, and operational automation. It can monitor the infrastructure supporting AI workloads, but it is not the dedicated platform for managing and testing LLM endpoints. Nutanix Marketplace supplies deployable applications and blueprints rather than a complete LLM operations environment. Nutanix Cloud Clusters extends Nutanix infrastructure into supported public clouds; it provides an execution environment but not the specialized LLM lifecycle and endpoint-management capabilities described in the question.

The Nutanix Enterprise AI datasheet explicitly identifies the ability to find, deploy, manage, and test generative AI LLMs. That product-purpose match makes option C unambiguous. Reference: Nutanix Enterprise AI datasheet . NHCF alignment: Nutanix solution identification and matching products to business use cases.

===============

Nutanix AOS automatically disables compression when metadata usage becomes high. The Prism 7.5 storage documentation explicitly identifies this condition and states that an alert is generated when automatic disablement occurs. Consequently, option D is the verified answer, replacing the supplied answer A.

Compression requires AOS metadata resources to track compressed extents and the associated data layout. If metadata consumption reaches a protective threshold, continuing compression could place additional pressure on the metadata services required for normal storage operation. AOS therefore prioritizes platform stability and metadata availability by disabling compression and notifying the administrator. The corresponding health alert should be investigated to determine why metadata usage has increased and whether workload characteristics or another storage condition requires remediation.

High write activity may increase storage workload and influence when post-process compression can execute, but it is not the documented automatic-disable trigger in this question. High reads similarly do not directly cause compression to be disabled. High physical-capacity consumption generates its own capacity warnings and corrective requirements but is distinct from the metadata threshold governing compression.

NHCF/NCA reference: Storage Concepts—capacity optimization, compression and storage-container administration; NCA Section 2, “Discuss storage operations.” Official references: Prism 7.5—Compression , Prism 7.5—Storage Alert Reference .

===============

AHV provides integrated IP Address Management through a managed virtual network. Enabling IPAM on the VM’s existing virtual network and defining a DHCP address pool allows AHV to intercept the guest’s DHCP request and allocate an available address from that pool. During VM or vNIC configuration, the administrator can then select DHCP assignment, allowing the platform to manage address allocation automatically.

Option B is the complete action for converting the VM’s current network into an IPAM-capable network. Although an IPAM-enabled network can also be created from the beginning, option C creates a different network and does not, by itself, ensure that the existing VM is connected to it. Option A may provide conventional external DHCP, but it does not constitute AHV-managed IPAM. Option D is invalid because the Controller VM is not intended to be repurposed as an administrator-configured DHCP server.

The DHCP pool must contain valid addresses for the subnet and exclude reserved infrastructure addresses. The VM must also be attached to that managed network and configured for DHCP; otherwise, AHV cannot complete the allocation.

NHCF/NCA reference: Networking—AHV networking basics, managed networks, IPAM and virtual-network configuration; NCA Section 2, “Identify virtual networking tasks.” Official references: AHV IP Address Management , Creating an AHV VM .

===============

Nutanix Guest Tools is a collection of guest-resident services and utilities that extends the integration between a deployed virtual machine and the Nutanix platform. One of its principal capabilities is Self-Service Restore, also described as file-level restore. When the feature is enabled and NGT is installed, an authorized VM administrator can access files from a Nutanix-protected snapshot without requiring the infrastructure administrator to restore the entire VM.

NGT establishes the guest-side functionality required to expose and use supported recovery services. Depending on the operating system and enabled components, NGT also supports functions such as application-consistent snapshot coordination and guest communication with the Nutanix platform.

The other tools serve different lifecycle stages. Nutanix X-Ray validates platform performance, resilience and infrastructure behavior. Foundation images physical nodes and creates or expands Nutanix clusters. Nutanix Move migrates workloads from supported source environments to Nutanix AHV or other supported targets. None of these tools supplies guest-level file recovery after normal VM deployment.

NHCF/NCA reference: VM Management and Nutanix tools; VM protection, recovery points and guest integration; NCA Section 1, “Recognize the use cases and features of Nutanix tools.” Official references: Prism Central 7.5—Nutanix Guest Tools Overview , Prism 7.5—Self-Service Restore .

===============

Nutanix Cloud Clusters, commonly identified as NC2, deploys the core Nutanix Cloud Infrastructure software stack on bare-metal resources supplied by public-cloud providers. That stack includes AOS, AHV, and Prism, giving administrators a consistent infrastructure and operational model across on-premises Nutanix environments and supported public clouds. For the examination scope, AWS and Microsoft Azure are the relevant providers.

NC2 does not merely expose external storage to an existing cloud-native hypervisor. It establishes a Nutanix cluster on cloud bare-metal instances, allowing workloads to retain familiar Nutanix storage, virtualization, management, and resilience characteristics. This supports migration, disaster recovery, datacenter extension, and temporary capacity expansion without requiring applications to be substantially refactored.

Nutanix Flow supplies networking and security capabilities; it is not the platform that instantiates NCI clusters on public-cloud bare metal. AOS Storage is the distributed storage layer within the Nutanix platform, not the complete cloud deployment solution. “NCI with External Storage” describes neither the recognized product name nor the NC2 deployment architecture.

The operative phrases are “NCI,” “AWS or Microsoft Azure,” and “bare-metal infrastructure.” Together, they identify NC2 unambiguously.

NHCF/NCA reference: Nutanix solution portfolio, hybrid multicloud deployment models, NCI, and NC2. Official reference: Nutanix Cloud Clusters , particularly the NC2 architecture and public-cloud availability sections.

===============

Nutanix Marketplace provides a centralized location within Prism Central for discovering and deploying Nutanix Apps and certified Preferred Partner Apps. Once applications are deployed, the My Apps workspace supplies a consolidated management view for their configuration, status, audit information and supported lifecycle operations.

Nutanix Apps can include platform services offered directly by Nutanix, while Preferred Partner Apps are developed and certified through collaboration between Nutanix and approved technology partners. Marketplace simplifies deployment by presenting supported application packages and guided configuration workflows rather than requiring administrators to assemble each product manually.

Marketplace is not a cloud-compute purchasing portal. Public-cloud infrastructure used by NC2 is obtained and managed through the relevant cloud provider and the applicable Nutanix deployment workflow. Marketplace also does not serve as the Nutanix license-renewal system; licensing and subscription management are handled through Prism licensing functions and Nutanix License Manager.

Option D precisely reflects the purpose stated in the Prism Central Admin Center documentation.

NHCF/NCA reference: Nutanix solutions, centralized application management and Nutanix tools; NCA Section 1, “Recognize Nutanix solutions, use cases and features.” Official references: Prism Central 7.5—Marketplace , Prism Central 7.5—My Apps .

===============