Study guide
12.5 License Operations: State, Assignment, Reclamation, and Expiry
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.5 License Operations: State, Assignment, Reclamation, and Expiry
Key Takeaways Explain This Topic AI
Objective 2.4 breaks licensing into five operational tasks: identify current state, assign, reclaim and unassign, inspect available licenses, and verify expiration.
Seamless licensing applies license actions automatically for internet-connected clusters, while manual license management uses a downloaded and uploaded license file for dark sites.
Reclaiming a license returns it to the available pool so it can be assigned elsewhere, which is the required step before decommissioning or destroying a cluster.
Destroying a cluster without first reclaiming its licenses strands that entitlement and requires Nutanix support to recover it.
Some Nutanix products and features do not require a license at all, so a license is not the explanation for every unavailable capability.
Last updated: September 2026
12.5 License Operations: State, Assignment, Reclamation, and Expiry
Objective 2.4 is unusually specific. It does not ask you to explain licensing philosophy — it lists five tasks: identify current license state, assign/reclaim/unassign licenses, inspect available licenses, verify licensing expiration, and identify the correct license by use case. Section 3.3 covered the tiers and what they contain; this section covers the operations.
Where Licensing Is Managed
Licensing is administered through the License Manager , reached from the Nutanix Support Portal and from Nutanix Central , and license state is visible from Prism . The mental model:
Your account holds an entitlement pool — the licenses you have purchased.
Licenses are assigned from that pool to clusters.
Reclaiming returns a license to the pool so it can be assigned somewhere else.
Because the pool is the account-level construct, "do we have a spare license?" is answered in the License Manager, not on any individual cluster.
Identifying Current License State
The licensing page in Prism reports what the cluster is running under:
- What you read Why it matters
- Tier in use — Starter, Pro, or Ultimate Determines which features are permitted
- Add-ons applied — Flow, NUS, NCM and others Add-ons are licensed separately from the NCI tier
- Compliance status Whether the cluster is correctly licensed for what it is doing
- Expiration date The renewal deadline
A cluster can drift out of compliance without anyone doing anything wrong — most commonly by being expanded . Licensing is metered by capacity, so adding nodes to a cluster can push it beyond what its assigned license covers. Checking license state after an expansion is the habit to build.
Two Ways to Apply License Actions
This is the same split you saw for LCM updates in section 8.3, and for the same reason.
Seamless licensing — for connected clusters
Where the cluster can reach Nutanix over the internet, license actions are applied directly. You perform the action and the cluster and portal reconcile between themselves. Assigning, reclaiming, and unlicensing a cluster are all handled this way, with no files to move.
Manual license management — for dark sites
Where there is no outbound connectivity — the dark site case introduced in section 8.3 — licensing becomes a three-step file exchange:
Download a cluster summary file from Prism.
Upload it to the Support Portal , which generates a license file for that cluster.
Download the license file and apply it in Prism.
Tip
The recognition point: connectivity determines the workflow. A question describing an air-gapped or dark-site cluster is describing manual license management; a question about a normally connected cluster is describing seamless licensing.
Assign, Reclaim, and Unassign
Assigning allocates a license from the pool to a cluster, which is what happens when a cluster is first licensed or when it is expanded and needs more capacity covered.
Reclaiming returns a license to the pool. The situations that require it:
Decommissioning a cluster. The entitlement should go back so it can be used elsewhere.
Moving a license between clusters. Reclaim from one, assign to the other.
Downgrading a tier , where a cluster no longer needs Ultimate.
Rebuilding a cluster , where the licence must be released before the cluster is destroyed.
Warning
Reclaim licenses before destroying a cluster. This is the single most examinable point in the objective, and the most costly one to get wrong in real life. A destroyed cluster cannot return its licenses, so the entitlement is stranded and recovering it becomes a support request. The blueprint names "Reclaiming Licenses when Destroying a Cluster" as its own reference for exactly this reason.
Unlicensing a cluster removes its license assignment entirely, returning the cluster to its unlicensed state and the license to the pool.
Inspecting Available Licenses and Verifying Expiration
Available licenses are inspected in the License Manager, which shows what has been purchased, what is currently assigned and to which clusters, and what remains free to assign. This is what you consult before planning an expansion — discovering mid-project that no entitlement is available is an avoidable delay.
Expiration is visible both per cluster in Prism and across the estate in the License Manager. Checking it matters because licenses expire on their own schedule, independent of anything happening on the cluster, and an expiry that passes unnoticed is a compliance problem discovered at the worst time.
License tags
Tags let an organization label licenses with its own metadata — a business unit, a project, a cost centre — so that entitlement can be tracked and attributed across a large estate. They are an administrative convenience rather than a technical control, but the blueprint names them, so recognize what they are for.
Not Everything Needs a License
The blueprint closes Objective 2.4 with a reference titled "Products that do not require a license," and it is there to correct a common assumption. Some Nutanix products and capabilities carry no separate license — several of the Objective 1.3 tools, for instance, are free downloads from the Support Portal.
The exam-relevant consequence: do not reflexively answer "a license is required" when a capability is unavailable. The cause may equally be the hypervisor in use, the cluster size, an unmet configuration prerequisite, or an unsupported version combination.
Task Summary
- Task Where Note
- Identify current license state Prism licensing page Tier, add-ons, compliance, expiry
- Inspect available licenses License Manager The account-level entitlement pool
- Assign a license Seamless, or manual for dark sites Needed after expansion
- Reclaim / unassign Seamless, or manual Always before destroying a cluster
- Verify expiration Prism and License Manager Independent of cluster activity
- Choose the right license By use case NCI tier plus add-ons such as Flow, NUS, NCM