Study guide
11.4 Cluster Expansion: Node Types and In-Node Expansion Capabilities
Nutanix Certified Associate NCA
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Nutanix Cloud Platform & HCI Foundations
1.1 Nutanix NCA Exam Overview, Format, and Objectives 1.2 Hyperconverged Infrastructure (HCI) vs. Traditional 3-Tier Architecture 1.3 The Nutanix Enterprise Cloud Portfolio (NCI, NUS, NCM, EUC, NC2)
2 Chapter 2: Platform Architecture & Distributed Core Services
2.1 Hardware Building Blocks: Nodes, Blocks, Clusters, and Quorum 2.2 Controller VM (CVM) Architecture, Datapath, and Autopathing 2.3 Core Distributed Services: Cassandra, Stargate, Curator, Zookeeper, and Genesis
3 Chapter 3: Prism Administration & Cluster Operations
3.1 Prism Element vs. Prism Central Architecture and Interface Navigation 3.2 Entity Management, Categories, and Role-Based Access Control 3.3 Nutanix Licensing Tiers, Add-ons, and Pulse Telemetry
4 Chapter 4: AOS Distributed Storage Fabric & Data Placement
4.1 Storage Pools, Storage Containers, and vDisk Virtual Architecture 4.2 Redundancy Factor (RF2 vs. RF3), Failure Domains, and Fault Tolerance 4.3 Data Locality Mechanics and Intelligent Lifecycle Management (ILM)
5 Chapter 5: Storage Optimization & Business Continuity
5.1 Storage Efficiency: Compression, Deduplication, and Erasure Coding (EC-X) 5.2 Space-Efficient Redirect-on-Write (ROW) Snapshots and Zero-Byte Clones 5.3 Protection Domains, Consistency Groups, and Disaster Recovery Replication
6 Chapter 6: AHV Virtual Machine Lifecycle Management
6.1 AHV VM Provisioning, Resource Allocation (vCPU, vRAM, Disks), and Boot Types 6.2 Nutanix Image Service and Virtual Machine Templates 6.3 Nutanix Guest Tools (NGT) Architecture, Features, and Deployment 6.4 AHV High Availability (HA), Acropolis Dynamic Scheduling (ADS), and Affinity Rules
7 Chapter 7: AHV Networking & Flow Security Fundamentals
7.1 AHV Virtual Networking Architecture, Open vSwitch (OVS), and Bridges 7.2 Host Network Uplinks, Virtual Switch Configuration, and NIC Bonding Modes 7.3 Virtual Networks: Managed vs. Unmanaged Networks and IPAM 7.4 Nutanix Flow Network Security & Microsegmentation Fundamentals
8 Chapter 8: Cluster Maintenance, Health Monitoring & Support
8.1 Nutanix Cluster Health Monitoring, Alerts, and Events Engine 8.2 Nutanix Cluster Check (NCC) Architecture and Execution 8.3 Life Cycle Manager (LCM) and Rolling Non-Disruptive Upgrades 8.4 Nutanix Support Ecosystem: Diagnostics, Log Gathering, and Support Bundles
9 Chapter 9: Recognizing Nutanix Solutions, Hypervisors & the Product Portfolio
9.1 Supported Hypervisors for NCI and Feature Supportability 9.2 NCI Core Components, Configurations, and Common Deployment Scenarios 9.3 Nutanix Unified Storage: Files, Objects, and Volumes Use Cases 9.4 Nutanix Database Service (NDB) and Database Automation 9.5 Nutanix Kubernetes Platform, Enterprise AI, and End-User Computing
10 Chapter 10: Nutanix Tools — Migration, Deployment, and Validation
10.1 Nutanix Move: Cross-Hypervisor and Cloud Migration 10.2 Foundation and Foundation Central: Imaging and Cluster Deployment 10.3 X-Ray, Collector, and the Objective 1.3 Tool Inventory
11 Chapter 11: Cluster Configuration, Security & Hardware Maintenance
11.1 Cluster Services Configuration: DNS, NTP, SMTP, and SNMP 11.2 Cluster Security Options: Lockdown, Encryption, and the Recycle Bin 11.3 Node Maintenance Mode, Host Shutdown, and Cluster Shutdown 11.4 Cluster Expansion: Node Types and In-Node Expansion Capabilities 11.5 Out-of-Band Management and Remote Console Access
12 Chapter 12: Storage, Network, and Software Administration Tasks
12.1 Volume Groups, vDisk Placement, and Live vDisk Migration 12.2 Network Visualizer, Physical Switch Monitoring, and Network Segmentation 12.3 The Software Compatibility Matrix and Upgrade Path Planning 12.4 Taking and Managing VM Snapshots in Prism 12.5 License Operations: State, Assignment, Reclamation, and Expiry
13 Chapter 13: Performance Analysis, Reporting & Support Operations
13.1 Prism Analysis: Metric Charts, Entity Charts, and Custom Reports 13.2 Custom Alert Policies and Behavioural Anomaly Detection 13.3 Interpreting Workload Performance: CPU Contention, CPU Ready, Memory, and I/O Latency 13.4 Creating Support Cases, Required Documentation, and Insights
11.4 Cluster Expansion: Node Types and In-Node Expansion Capabilities
Key Takeaways Explain This Topic AI
Objective 3.2 distinguishes two kinds of growth: adding nodes to a cluster, and expanding capabilities within an existing node.
The Prism Expand Cluster workflow discovers candidate nodes, images them to match the cluster AOS and hypervisor version, and adds them without downtime.
Storage-only nodes add capacity and run AHV regardless of cluster hypervisor; compute-only nodes add CPU and memory but contribute no storage.
Expanding within a node means adding drives to empty bays, adding memory, or adding network adapters, constrained by the platform model.
Adding a node triggers automatic background rebalancing of data across the enlarged cluster rather than requiring a manual migration.
Last updated: September 2026
11.4 Cluster Expansion: Node Types and In-Node Expansion Capabilities
Objective 3.2 contains two adjacent knowledge statements: "identify the node types for expansion" and "identify expansion capabilities within a node." They describe two different answers to "we need more," and part of the skill is knowing which question is being asked.
Scaling Out: Adding Nodes
The defining property of a scale-out architecture is that growth is incremental and non-disruptive . Where a traditional array forces a forklift replacement when the controllers run out of headroom, a Nutanix cluster grows a node at a time, and every node added brings compute, storage, and controller capacity together .
The Expand Cluster workflow
From Prism Element, Expand Cluster runs the process:
Discovery. Prism discovers candidate nodes on the network that are not yet part of a cluster.
Selection and addressing. You select nodes and supply host, CVM, and out-of-band management IP addresses.
Imaging if required. If the new node is running a different AOS or hypervisor version than the cluster, it is imaged to match . This is the step that makes expansion safe: a cluster is not left running mixed versions.
Addition. The node joins the cluster and its storage becomes part of the storage pool.
Rebalancing. Data is automatically redistributed in the background so the new node carries its share.
The workflow is non-disruptive. Guest VMs continue running throughout, and the rebalance is a background activity rather than a migration you plan.
Tip
The pre-check step matters: the blueprint references "Prerequisites and Requirements for Expanding a Cluster." Candidate nodes must be network reachable, compatible with the cluster, and have the necessary addressing available. Failed expansions are usually addressing or reachability problems rather than hardware faults.
The Three Node Types
Choosing the node type is a matching exercise between the shape of the shortage and the shape of the node:
- Node type Contributes Hosts guest VMs? Runs which hypervisor? Use when
- Hyperconverged CPU, memory, storage Yes The cluster hypervisor Balanced growth — the default
Storage-only Storage + CVM resources No Always AHV Capacity is growing faster than compute; or adding capacity to an ESXi cluster without extra hypervisor licensing
Compute-only CPU and memory Yes The cluster hypervisor An application needs cores far out of proportion to its data, often for licensing reasons
Storage-only nodes
A storage-only node runs a CVM and contributes its drives to the storage pool, but never hosts guest VMs. Two properties make it examinable:
It always runs AHV , even when the cluster hosts its workloads on ESXi. Because it runs no guests, no ESXi licensing is required for it — which makes storage-only nodes the standard way to add capacity to a VMware-based Nutanix cluster economically.
It changes the compute-to-capacity ratio of the cluster, which is precisely the point when data grows faster than the workload that produces it.
Compute-only nodes
The mirror image: CPU and memory, no contribution to the storage fabric. VMs on a compute-only node read and write across the network to CVMs on other nodes, so they do not benefit from data locality in the same way. Use them when the constraint is genuinely cores — a workload licensed per core, or a compute-heavy application with a modest data footprint.
Important
A cluster cannot be made only of compute-only nodes. They add compute to a cluster whose storage is provided by hyperconverged and storage-only nodes.
Scaling Within a Node
Sometimes the answer is not another node. "Identify expansion capabilities within a node" covers growth inside the chassis you already own:
Adding drives to empty bays. Most node models ship partially populated. Filling empty bays adds capacity to the storage pool without adding a node, and is by far the cheapest form of growth when the bays exist.
Adding memory. Subject to the platform's DIMM slots and supported configurations. Memory is frequently the first resource a cluster exhausts, because AHV VMs are fixed-size by default.
Adding or upgrading network adapters. Additional NICs for more bandwidth or redundancy, or faster adapters where the uplinks have become the constraint.
Every one of these is model-constrained . How many bays, how many DIMM slots, which drive types are supported, which NICs are qualified — these come from the platform specification and the Compatibility and Interoperability Matrix, not from a general rule.
Tip
Decision shortcut. Are there empty drive bays or DIMM slots? If yes, in-node expansion is usually cheaper and faster. Do you need more controller and compute capability, not just capacity? Then you need nodes, because adding drives does not add a CVM.
After Expansion
Adding capacity, whether by node or by drive, triggers automatic background rebalancing . Curator redistributes data so the new capacity is used and the cluster returns to an even distribution. No manual data migration is required, and it happens as background work rather than as a maintenance activity.