Study guide

10.2 Foundation and Foundation Central: Imaging and Cluster Deployment

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

10.2 Foundation and Foundation Central: Imaging and Cluster Deployment

Key Takeaways Explain This Topic AI

Foundation is the Nutanix imaging tool that installs the hypervisor and AOS onto bare-metal nodes and forms them into a cluster.

Foundation can run as a standalone VM, from a portable Foundation applet, or from the CVM of an existing node, and the Foundation Use Case Matrix decides which to use.

Foundation Central extends imaging to remote sites: nodes shipped to a branch call home to Foundation Central and are imaged without an engineer travelling there.

Foundation Central runs as a service associated with Prism Central, which is what makes zero-touch remote deployment possible.

Foundation is a deployment tool used once per node; ongoing software and firmware updates are the job of the Life Cycle Manager instead.

Last updated: September 2026

10.2 Foundation and Foundation Central: Imaging and Cluster Deployment

Objective 1.3 asks you to "identify Foundation/Foundation Central use cases and features." They are two tools with one purpose — turning bare-metal servers into a working Nutanix cluster — separated by where the servers are .

Foundation: Imaging and Cluster Creation

Foundation is the Nutanix bare-metal imaging tool. Given a set of nodes with nothing useful installed, Foundation:

Discovers the nodes on the network.

Images each node with the chosen hypervisor and the chosen AOS version .

Applies the network configuration — host IP, CVM IP, and out-of-band management IP for each node, plus netmask and gateway.

Creates the cluster from the imaged nodes.

The result is a running cluster you can log into with Prism Element. This is a deployment-time activity: for most nodes it happens exactly once.

Where Foundation Runs

There is more than one way to run Foundation, and the blueprint points at the Foundation Use Case Matrix for choosing between them:

Form When you use it

Standalone Foundation VM The general case. Import the Foundation VM onto a laptop or an existing host on the same network as the new nodes, and drive imaging from its web UI.

Foundation applet / portable Foundation A lighter-weight option for smaller jobs where deploying a full VM is unnecessary.

CVM-based Foundation Nodes that already have a CVM — for example factory-imaged nodes or nodes being re-imaged — can be imaged from the CVM of an existing node without a separate Foundation VM.

Tip

The recognition point is simply that Foundation is not a single fixed artefact. If a question offers "you must always deploy a dedicated Foundation VM" as an option, it is wrong — the use case matrix exists precisely because there are several valid paths.

What Foundation Needs

Network reachability to the nodes, typically on the same Layer 2 segment for discovery.

The AOS and hypervisor images you intend to install.

The IP addressing plan — three addresses per node is the usual arithmetic: host, CVM, and out-of-band management.

That last point connects to Objective 3.2, which asks about out-of-band management use cases. Foundation configures the OOB interface as part of imaging, which is what lets you manage the node later without an operating system running.

Foundation Central: Imaging Nodes You Cannot Reach

Foundation solves the problem of imaging nodes on your network. Foundation Central solves the harder problem: imaging nodes at sites where you have no Nutanix expertise and no engineer .

The scenario is the classic retail or branch rollout. A hundred stores each need a small cluster. Flying an engineer to a hundred sites is unaffordable, and store staff cannot be expected to image nodes.

Foundation Central inverts the direction of the connection:

Foundation Central runs centrally , as a service associated with Prism Central .

Nodes are shipped directly from the factory to the remote site.

On-site staff perform only physical tasks: rack the nodes, connect power, connect the network.

Each node calls home to Foundation Central using configuration supplied through DHCP options or a small amount of pre-staged information.

Foundation Central images the nodes and forms the cluster remotely .

The operational win is that skilled work happens once, centrally, and the site work is reduced to cabling.

  • Foundation Foundation Central
  • Runs Locally, near the nodes Centrally, with Prism Central
  • Connection direction Foundation reaches out to nodes Nodes call home to Foundation Central
  • Requires on-site expertise Yes No — racking and cabling only
  • Typical use Datacenter build, single cluster Many remote/branch sites at scale
  • Foundation Is Not LCM

This distinction is worth stating explicitly because it maps onto two different blueprint objectives:

Foundation (Objective 1.3) is a deployment tool. It creates clusters from bare metal, and it images nodes.

Life Cycle Manager (Objective 3.3) is a maintenance tool. It performs inventory and updates AOS, AHV, firmware, and other components on a cluster that already exists, non-disruptively.

If a scenario says "the cluster is running and we need to update AHV," the answer is LCM. If it says "the nodes arrived and there is nothing on them," the answer is Foundation. A node being re-imaged — reset back to a clean state, perhaps to change hypervisor — goes back to Foundation, and the blueprint reference "Prepare Bare-Metal Nodes for Imaging" under Objective 3.2 is where that intersects hardware maintenance.

Summary

  • Scenario Tool
  • Build a new cluster from bare-metal nodes in your datacenter Foundation
  • Change a node's hypervisor by re-imaging it Foundation
  • Deploy clusters at 100 branch sites without travelling to them Foundation Central
  • Update AOS, AHV, or firmware on a running cluster Life Cycle Manager

Loading diagram... Foundation vs. Foundation Central Deployment Models