An administrator wants to verify NDB high-availability functionality.

The first verification should be a nondisruptive health check in the NDB Service Topology view. This view displays the components that form the NDB high-availability deployment, including service clusters and the API, repository, and HAProxy virtual machines. Confirming that all expected services and topology members are active establishes that the HA configuration is healthy before an administrator performs a failover test. Restarting an API leader VM is a disruptive validation activity and should not be the initial step when the existing service state has not been verified. Storage-utilization reports do not confirm NDB service availability, while a successful clone validates a database workflow rather than the health of every HA component. The official Nutanix description of NDB Service Topology explains that the Topology tab presents the structure and components of an NDB HA deployment.