After a successful LCM upgrade of a Nutanix cluster running AHV, an administrator notices Prism Central did not change version but continues to manage the cluster. What compatibility consideration should be verified before declaring the change complete?
Select an answer to reveal the explanation.
Short Explanation
Think of Prism Central and the cluster like a phone and its OS: they can move at different speeds, but only if the app store says they're compatible. You don't panic because Prism Central didn't upgrade too—you check the compatibility matrix for that AOS release and Prism Central release. If it's listed, you're good; if not, you've got a support problem, not a magic rediscovery trick.
Full Explanation
Nutanix compatibility is governed by the published interoperability matrix, not by a rule that every component must share one release string. LCM can bring a cluster, its AHV hosts, and the cluster-local Prism Element to a newer supported stack while Prism Central remains at a supported management release, provided the matrix lists that combination. That matters because Prism Central is a management plane: it must speak a supported API and feature set to the cluster, but it does not become incompatible merely because its version number did not move. The first wrong idea is rolling the cluster back solely because Prism Central was not upgraded; that treats version alignment as a mechanical requirement instead of checking whether the combination is supported. The second wrong idea is forcing Prism Central to rediscover the cluster by using a changed CVM address; cluster discovery and management registration do not depend on treating CVM addresses as the cluster endpoint, and a normal LCM upgrade does not make the cluster a new entity. The third wrong idea is manually upgrading Prism Element to match Prism Central; cluster-local management and central management can remain on different supported releases, and forcing a match can create unnecessary change risk. Exam caveat: supportability, not version equality, decides whether a mixed management stack is acceptable. Operational check: compare the upgraded AOS/Prism Element release and current Prism Central release against the current Nutanix compatibility matrix before signing off.