An administrator renames a production cluster from 'Prod-01' to 'Prod-Core' in Prism Element to align with a new naming convention. The cluster is registered to Prism Central and managed by LCM. What effect does the rename have on Prism Central and LCM management of the cluster?

Every Nutanix cluster has a cluster UUID that is generated when the cluster is created and never changes. Prism Central, LCM and the other management services key their records on that UUID, while the cluster name is only a display attribute stored alongside it. Renaming the cluster in Prism Element updates that attribute, and Prism Central picks up the new name the next time it syncs with the registered cluster, so metrics, alerts, LCM inventory and update operations continue without interruption. Manual re-registration is not required, because the registration itself is bound to the UUID and the trust established when the cluster was registered, not to the name. A rename is a lightweight metadata change, so it does not reboot CVMs, and it does not restart Stargate, which is the data-path service that serves VM I/O rather than management API calls. Exam caveat: separate mutable labels (cluster name, VM names, categories) from immutable identifiers (cluster UUID, VM UUID) when you reason about what a change can break; also remember that DNS records, certificates or scripts that reference the old name are your own dependencies to update. Operational check: after the rename, open the cluster in Prism Central and confirm the new name appears with the same cluster UUID shown by 'ncli cluster info' on a CVM.