In this scenario, a PostgreSQL instance managed by NDB on a Linux VM is malfunctioning after a manual OS update, and a new Linux DB server VM has been prepared to host the data. To migrate the data to the new VM, the administrator must integrate the new VM into NDB's management framework. The correct action is to register the new DB Server VM in NDB, which allows NDB to recognize and manage the VM as a database server. Once registered, the administrator can use NDB's features (e.g., cloning, restoring, or reprovisioning) to migrate the data from the broken instance to the new VM.
Here's why the other options are incorrect:
* A. Provision a new PostgreSQL instance from the Databases page: This creates a fresh instance without migrating existing data, losing the broken instance's data unless separately restored.
* B. From The Machine policy, Authorize Database Server VMs: Machine policies in NDB define rules for VM management, but authorizing VMs is not a direct migration action and assumes prior registration.
* C. Follow the Provision a PostgreSQL Instance wizard: Similar to A, this provisions a new instance rather than migrating data to an existing prepared VM.
Registering the new VM in NDB (via the "Database Server VMs" section) enables the administrator to associate it with the existing PostgreSQL instance's configuration and perform a data migration (e.g., using a snapshot or backup). This aligns with NDB's workflow for replacing a broken server. Thus, the verified answer is D.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.3: Registering and Managing Database Server VMs.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
3: Manage NDB Solutions, Objective 3.2: Register and Manage DB Server VMs (applicable to v6.10).
* Nutanix NDB Administration Guide: "Registering a Database Server VM" section.