According to the NDB documentation, the NDB patching process for MongoDB Server Cluster follows these steps1:
* NDB identifies the primary member of the MongoDB Server Cluster and patches it first.
* NDB triggers a failover to elect a new primary member from the remaining secondary members.
* NDB patches the former primary member, which becomes a secondary member after the failover.
* NDB patches the remaining secondary members one by one.
* NDB verifies the patching status and the cluster health.
This process ensures that the MongoDB Server Cluster always has a primary member available to handle write operations, while minimizing the downtime and the impact on the cluster performance.
References: Nutanix Support & Insights, section "Patching a MongoDB Server Cluster"

An administrator needs to provision multiple database clones from the same source database for different purposes (e.g., QA and Test/Development) while avoiding resource starvation by differentiating VM resources for each department. The most efficient way to achieve this is by creating multiple Compute profiles in NDB. Compute profiles define CPU, memory, and other resource allocations for VMs, allowing the administrator to tailor resource limits (e.g., higher resources for QA, lower for Development) and apply them during clone provisioning. This approach is built into NDB, ensuring consistent resource management without manual adjustments.
* Option A (Create multiple Compute profiles) is correct as it provides a scalable and efficient way to allocate resources per department.
* Option B (Leverage NCM Self Service to deploy database clones) is incorrect because Nutanix Cluster Management (NCM) Self Service is for end-user provisioning, not resource differentiation.
* Option C (Use a VM Template for each department) is incorrect because VM templates are less flexible and not natively integrated with NDB clone provisioning.
* Option D (Generate a playbook to resize database VMs when released) is incorrect because playbooks are for automation, not initial resource allocation, and resizing post-provisioning is less efficient.
This method optimizes resource use across departments.
References
* Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section:
Configuring Compute Profiles
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Servers

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) v7.5Knowledge Objectives, Section 3:
Manage NDB Solutions, Objective 3.2: Register and Manage DB Server VMs (applicable to v7.5).
Nutanix NDB Administration Guide: "Registering a Database Server VM" section.

When an Oracle database is upgraded using Era, the type of upgrade category is an "In-place upgrade". This method involves upgrading the database software within the same Oracle home as the existing database. The AutoUpgrade utility is used to automate the upgrade process, both before starting upgrades, during upgrade deployments, and during post-upgrade checks and configuration migration1. This method is preferred due to its simplicity and efficiency1.

To enable iSCSI connections between the Nutanix Database Service (NDB) server, Controller VMs (CVMs), and Prism Element, a Data Services IP must be configured in Prism Element. The Data Services IP acts as a cluster-wide address that facilitates iSCSI target discovery and connectivity. It is used by Nutanix Volumes (a block storage service) to present storage to external clients or services, such as the NDB server, via the iSCSI protocol. This IP ensures that iSCSI traffic is routed correctly and remains available even if a CVM fails, as ownership of the Data Services IP can move to another CVM in the cluster.
Configuring the Data Services IP is a prerequisite for integrating NDB with a Nutanix cluster, as NDB relies on iSCSI to manage database storage operations like provisioning and cloning. Without this configuration, the NDB server cannot establish the necessary connections to the CVMs for database-related tasks. Options like Virtual IP, Secondary DNS IP, and Backplane IP are not relevant in this context:
Virtual IP: This is typically associated with high-availability setups for applications, not iSCSI connectivity.
Secondary DNS IP: This pertains to network resolution, not storage connectivity.
Backplane IP: This is an internal network IP for cluster communication, not for external iSCSI access.
Thus, the correct and verified answer is the Data Services IP.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.2: Configuring NDB Prerequisites.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2:
Deploy and Configure an NDB Solution (applicable to v7.5 as foundational concepts remain consistent).
Nutanix Support & Insights Portal: "Configuring iSCSI Data Services IP for Nutanix Volumes" (general Volumes configuration applicable to NDB).