Objective 1.1 Recognize Nutanix solutions, use cases, and features of Nutanix Cloud Infrastructure (NCI) technologies
1.1.1 Identify supported hypervisors for NCI
NCI (Nutanix Cloud Infrastructure) runs on AHV, Nutanix's own KVM-based hypervisor that is included at no extra cost, and on VMware ESXi. Check the Supported Hypervisors and Supportability of Features (by Hypervisor) pages for your AOS release, because some features exist only on AHV.
Many features are AHV-only, for example Flow microsegmentation, Image Placement Policies, ADS and Agent VMs. If a question names a feature and asks about ESXi, check the feature matrix before assuming parity.
1.1.2 Describe the core components included in NCI
The core pieces: AOS (the storage and cluster OS), whose Distributed Storage Fabric (DSF) pools every node's local disks into one shared storage layer; AHV; Prism Element (manages one cluster, served by the CVMs); Prism Central (a separate VM that manages many clusters); and LCM for upgrades.
Every node runs a Controller VM (CVM). The CVM owns the node's disks and serves storage I/O. Its main services are Stargate (data I/O), Cassandra (distributed metadata), Curator (background cleanup and rebalancing), Zookeeper (cluster configuration) and Prism.
Prism Element is reached on the IP of any CVM or the cluster virtual IP. It is not reached on the hypervisor host IP or the Foundation VM.
1.1.3 Identify core component-related configurations
Storage is layered as storage pool β storage container β vDisks. Policies such as replication factor, compression, deduplication and erasure coding are set on the container, not on the VM or the pool.
Data is written RF2 (two copies) or RF3 (three copies) across different nodes. Data locality keeps a VM's data on the node it runs on, so reads stay local.
1.1.4 Identify common deployment scenarios of NCI
Common shapes: single-node (ROBO or edge, no node redundancy), two-node (ROBO; needs a Witness VM to avoid split-brain), three nodes or more (the standard FT1/RF2 cluster), and five or more for RF3/FT2. Clusters can also run in the public cloud as NC2 (Nutanix Cloud Clusters on AWS or Azure).
RF3 / FT2 needs a minimum of 5 nodes.
1.1.5 Align an NCI component with its use case
Match the product to the job. Flow Network Security handles VM microsegmentation by category. Nutanix Disaster Recovery handles protection policies, recovery plans and replication between sites. NC2 extends a cluster to public cloud. LCM handles firmware and software lifecycle. Storage-only nodes add capacity without adding hypervisor compute.
When a CVM's services fail (for example Stargate or Cassandra), the cluster redirects that node's I/O path to another CVM (autopathing). Guest VMs keep running while that happens.
The App Mobility Fabric is the marketing name for letting workloads move between clouds and hypervisors. Expect it as a distractor or a definition question.
Official docs for 1.1 (20)
- Introduction to AOS
- AHV Overview
- Supported Hypervisors
- Supportability of Features (by Hypervisor)
- Built-in AHV Virtualization
- Two-Node Clusters
- Three-Node Cluster Considerations
- Replication Factor
- Life Cycle Manager (LCM) Overview
- LCM Framework Update using Dark Site Method
- LCM Limitations
- Using 1-Click Upgrade in the Prism Element Web Console
- Performing initial cluster configuration
- Adding an AHV Storage-Only Node
- Disaster Recovery using Multicloud Snapshot Technology (MST)
- Nutanix Flow
- Nutanix Disaster Recovery
- Nutanix Cloud Clusters (NC2)
- Nutanix Konnector Overview
- Nutanix Central Overview