Study guide

12.3 The Software Compatibility Matrix and Upgrade Path Planning

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

12.3 The Software Compatibility Matrix and Upgrade Path Planning

Key Takeaways Explain This Topic AI

The Compatibility and Interoperability Matrix on the Nutanix Support Portal is the authoritative source for which software, hypervisor, hardware, and third-party product versions are supported together.

Nutanix publishes AOS releases on Long Term Support and Short Term Support tracks, and the choice between them shapes how often a cluster must be upgraded.

Upgrade paths are not always direct: a cluster several versions behind may need an intermediate hop, which the matrix and upgrade path tool identify.

Compatibility extends beyond AOS and AHV to Prism Central, NCC, Foundation, firmware, and third-party products such as backup software.

LCM enforces dependency order at execution time, but checking the matrix beforehand is what prevents planning an upgrade that cannot be performed.

Last updated: September 2026

12.3 The Software Compatibility Matrix and Upgrade Path Planning

Section 8.3 covered how the Life Cycle Manager performs upgrades. This section covers what you check before starting one — Objective 3.3's "describe software compatibility matrix."

Why a Matrix Exists

A Nutanix cluster is not one product on one version. At any moment it is running a specific version of each of:

  • AOS
  • The hypervisor (AHV, or ESXi at its own version)
  • Prism Central
  • NCC
  • Foundation
  • Firmware for BIOS, BMC, drives, and network adapters
  • Add-on products such as Files, Objects, and NKP
  • Third-party products integrated with the cluster, most commonly backup software

Not every combination of these is supported or even functional. The Compatibility and Interoperability Matrix on the Nutanix Support Portal is the authoritative record of which combinations are.

Important

The matrix is a support statement , not documentation. "This combination works in my lab" and "this combination is supported" are different claims, and only the second one gets you help at 2 a.m. That distinction is exactly why the blueprint names the matrix in Objective 3.3 and again in Objective 1.1 for hypervisor support.

What the Matrix Answers

  • Question Which view
  • Is AHV version X supported with AOS version Y? Software interoperability
  • Is this hardware platform supported on this AOS release? Hardware compatibility
  • Does my backup product support this AOS version? Third-party interoperability
  • Can I upgrade directly from my current AOS to the target? Upgrade paths
  • Which Prism Central version manages this cluster version? Software interoperability

The blueprint also references "Prism Central and Prism Element Specifications" and "Determining Compatibility Between Hardware and Supported Products," which are the specific views behind the second and fifth rows.

Long Term Support vs. Short Term Support

Nutanix publishes AOS on two release tracks, and the choice materially changes an organization's upgrade cadence:

  • Long Term Support (LTS) Short Term Support (STS)
  • Support window Longer Shorter
  • New features Fewer; stability-oriented Earliest access to new features
  • Upgrade cadence forced on you Lower Higher — support ends sooner
  • Typical fit Production estates that value stability Environments that need a specific new capability

The trade is straightforward: LTS buys you time between mandatory upgrades; STS buys you features sooner at the cost of upgrading more often. An organization that adopts an STS release and then never upgrades will find itself unsupported far faster than it expected.

Upgrade Paths Are Not Always Direct

The assumption that any version can upgrade straight to any newer version is wrong, and it is the practical reason this objective exists.

A cluster several releases behind may need to move to an intermediate version first , because the upgrade code path from a very old release to the newest one has not been validated. The matrix and the upgrade path tooling identify these hops.

The planning implications:

A long-deferred upgrade is a multi-step project , not one maintenance window. Each hop is its own rolling upgrade with its own validation.

Falling far behind is expensive , which is the strongest operational argument for a regular upgrade rhythm.

Component order matters too. LCM enforces dependencies at execution time — for example, updating the LCM framework itself before the components it manages, and observing the documented order between AOS, AHV, firmware, and Prism Central. Prism Central generally needs to be at a version that supports the clusters it manages.

How This Fits With LCM

A useful division of labour:

The matrix is planning. Before you schedule anything: is the target combination supported, and can I get there directly?

LCM pre-checks are enforcement. At execution time, LCM runs pre-checks and refuses to proceed if the cluster is not in a fit state — insufficient resiliency, a node already in maintenance mode, an unsupported step.

Both exist because both failures are real. LCM will stop you from executing a bad upgrade; only the matrix stops you from planning one that was never going to work.

Tip

The exam-ready sentence: the Compatibility and Interoperability Matrix on the Nutanix Support Portal is the authoritative source for supported version combinations and upgrade paths. If an option offers release notes, the Nutanix Bible, community forums, or the hardware vendor's documentation as the authority for support status, it is wrong.

Common Software Maintenance Tasks

Objective 3.3 closes with "identify common software maintenance tasks." The recurring ones, all driven through LCM or Prism:

LCM inventory , to discover current versions across the cluster.

AOS and AHV upgrades , performed as rolling, non-disruptive updates.

Firmware updates for BIOS, BMC, drives, and NICs.

Prism Central upgrades , coordinated with the clusters it manages.

NCC upgrades , which follow their own release cycle independent of AOS (section 8.2).

NGT upgrades , which can be applied in bulk across many VMs rather than guest by guest.

Loading diagram... Upgrade Planning: Matrix First, Then LCM