Study guide

9.2 NCI Core Components, Configurations, and Common Deployment Scenarios

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

9.2 NCI Core Components, Configurations, and Common Deployment Scenarios

Key Takeaways Explain This Topic AI

Objective 1.1 asks you to describe the core components in NCI, identify core component-related configurations, identify common deployment scenarios, and align a component with its use case.

Single-node and two-node clusters exist specifically for edge and remote-office deployments; two-node clusters require an external Witness VM to arbitrate.

Three nodes is the minimum for a standard RF2 cluster, and five nodes is the minimum for RF3.

Nutanix Central is a SaaS control plane that gives a single global view across on-premises clusters and NC2, sitting above individual Prism Central instances.

Multicloud Snapshot Technology (MST) writes protected snapshots to object storage, giving a low-cost disaster recovery target without a second full cluster.

Last updated: September 2026

9.2 NCI Core Components, Configurations, and Common Deployment Scenarios

Objective 1.1 contains four knowledge statements that all circle the same skill: given a customer situation, recognize which Nutanix building block fits. This section is that mapping exercise.

The Core Components Included in NCI

Nutanix Cloud Infrastructure is a software bundle, not a single program. The components you must be able to name:

  • Component What it is What it does for you
  • AOS The Acropolis Operating System The distributed system that turns independent servers into a cluster

DSF Distributed Storage Fabric Pools every node's drives into one logical storage layer with replication and data efficiency

  • CVM Controller VM One per node; runs the AOS services and owns the local drives via passthrough
  • AHV The included hypervisor Runs guest VMs without separate hypervisor licensing
  • Prism Element Per-cluster management UI Day-to-day operation of a single cluster

Prism Central Multi-cluster management plane One console across clusters; home of categories, templates, and policy

  • Flow Virtual Networking Software-defined networking Virtual switches, subnets, IPAM, and network policy
  • Cluster Sizing: The Configurations That Follow From Replication Factor

"Identify core component-related configurations" is largely a question about node counts, and the numbers come straight from how many copies of data the cluster keeps:

  • Topology Minimum nodes Failures tolerated Typical use
  • Single-node cluster 1 Drive-level only Edge sites, small ROBO, backup targets
  • Two-node cluster 2 + Witness VM 1 node Remote and branch offices needing node redundancy cheaply
  • Standard RF2 cluster 3 1 node The mainstream production configuration
  • RF3 cluster 5 2 nodes simultaneously Large or high-criticality clusters

Important

Memorize 3 for RF2 and 5 for RF3 . The logic: to keep n copies of data and still have somewhere to rebuild after a failure, the cluster needs more nodes than copies. These two numbers appear on Nutanix exams at every level.

Why Two-Node Clusters Need a Witness

A two-node cluster has an unsolvable problem on its own: if the two nodes stop seeing each other, each one believes the other has failed. If both keep serving writes, the data diverges — split brain .

The Witness VM solves this. It runs outside the cluster, at a third location or in another site, and does exactly one thing: when the two nodes lose contact, each races to claim the Witness, and the one that succeeds continues as a single-node cluster while the other stops serving I/O. The Witness holds no user data and arbitrates rather than participating.

The Witness VM is also named separately in Objective 1.3 as one of the seven tools you must recognize, so it earns points twice.

Node Types Within a Cluster

Not every node is a full hyperconverged node:

Hyperconverged (standard) node — contributes CPU, memory, and storage, and hosts guest VMs.

Storage-only node — contributes storage and CVM resources, hosts no guest VMs, and always runs AHV. Used to grow capacity faster than compute, and to add capacity to an ESXi cluster without extra hypervisor licensing.

Compute-only node — contributes CPU and memory and hosts guest VMs, but contributes no storage to the fabric. Used when an application needs cores far out of proportion to its capacity, often for licensing reasons.

The recognition rule: storage-heavy workload growing faster than compute → storage-only. Compute-heavy workload with modest data → compute-only.

Common Deployment Scenarios

Core datacenter. Multi-node RF2 or RF3 clusters, registered to Prism Central, running mixed enterprise workloads. The default shape.

Edge and ROBO. Single-node or two-node clusters at retail sites, factories, clinics, or branches. Low node count, remote administration through Prism Central, and often a dark site with no direct internet access — which shapes how licensing and LCM updates are performed.

Public cloud with NC2. Nutanix Cloud Clusters (NC2) runs the native AOS and AHV stack directly on bare-metal instances in AWS and Azure. Because it is the same software, VMs and data move between on-premises and cloud without reformatting or nested virtualization.

Disaster recovery. Either a second cluster receiving replication, or — increasingly — Multicloud Snapshot Technology (MST) , which writes protected snapshots to object storage instead of requiring a full standby cluster. MST appears explicitly in the blueprint reference list as "Disaster Recovery using Multicloud Snapshot Technology," and its use case is cheap retention and recovery without paying for idle compute.

Platform-Level Services Above the Cluster

Two newer services appear in the Objective 1.1 references and are unfamiliar to anyone studying from older material:

Nutanix Central — a SaaS control plane that provides a single global view across all your Nutanix deployments, on-premises and NC2 alike. Where Prism Central manages a set of clusters, Nutanix Central sits above Prism Central instances and gives fleet-wide visibility, capacity, and alert summaries from one console.

Nutanix Konnector — a service in Prism Central and Nutanix Central that automatically registers clusters, notably Nutanix Kubernetes Platform clusters, so they appear in the management console without a manual onboarding step.

Tip

Keep the hierarchy straight: Prism Element manages one cluster, Prism Central manages many clusters, and Nutanix Central gives one view across many Prism Centrals and cloud deployments.

Loading diagram... NCI Deployment Scenarios and Management Hierarchy