Nutanix Enterprise Cloud Fundamentals and Architecture
What this domain tests
This domain checks whether you can explain Nutanix as a distributed enterprise cloud platform rather than a SAN-plus-hypervisor stack. Expect questions on AOS, AHV, Prism, the Controller VM (CVM), cluster architecture, and scale-out design.
Core architecture rules
- AOS is the distributed storage and data-services layer; it runs in a CVM on every node.
- Each node contributes CPU, memory, and local SSD/HDD. The CVMs form a distributed system and present storage to VMs.
- AHV is Nutanix's native KVM-based hypervisor. ESXi and Hyper-V are also supported in many configurations.
- Prism Element manages one cluster. Prism Central manages many clusters and adds categories, images, and cloud services.
- VM I/O goes to a CVM, local first where possible, and the Distributed Storage Fabric places and protects the data.
- Data locality and tiering are automatic. The cluster scales by adding nodes, not by adding a SAN.
Worked example
A four-node cluster with 8 TB raw per node has 32 TB raw. With RF2, data is protected across nodes, so usable capacity is roughly half before reserve and metadata. If the customer needs 12 TB usable, four nodes may look sufficient on raw math, but you must subtract metadata, snapshot reserve, and rebuild headroom, then check performance. A fifth node increases both capacity and failure tolerance.
Traps that cost marks
Do not call the CVM a single point of failure; there is one per node. Do not say Prism Central is required to run a cluster. Do not assume AHV is mandatory. Do not describe local disks as hypervisor-owned JBOD; AOS owns and abstracts them.