Free Nutanix NCP-DB Practice Exam with Questions & Answers | Set: 8

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.

Nutanix Era leverages the Nutanix time-efficient snapshots to create the clones1. These database clones are highly space-efficient, consuming near-zero bytes by having only the further writes constituting to its size1. Therefore, an administrator would find the total space being used by all Era clones for a specific database under the Cloning widget on the Databases > Clones database summary page. The other options do not specifically provide information about the total space used by all Era clones for a specific database. Therefore, the correct answer is A. Under the Cloning widget on the Databases > Clones database summary page.

A Development team requesting updated data for a cloned MongoDB instance used as source data for a script needs the latest snapshot or point-in-time data. In NDB, the "Clone Refresh" task updates an existing clone with the most recent data from the source database, ensuring the development team has access to current information without recreating the clone. This is the most efficient approach for maintaining an updated clone.

Option A (Clone the DB from the latest point in time data) is incorrect because it creates a new clone, duplicating effort instead of refreshing the existing one.

Option B (Execute a clone update) is incorrect as "clone update" is not a standard NDB task; refresh is the correct term.

Option C (Provision a MongoDB instance) is incorrect because it provisions a new instance, not an update to the clone.

Option D is correct as Clone Refresh syncs the clone with the latest source data.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Clones and Refresh

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

In Nutanix Database Service (NDB), patching Oracle database engines requires the "Update" button to be available on the database server VM’s management interface. If this button is missing, it typically indicates a configuration issue preventing NDB from performing the patching operation. The most common and critical reason is that the operating system (OS) credentials for the database server VM have not been set or registered with NDB. These credentials are necessary for NDB to authenticate and execute patching tasks on the VM, such as accessing the Oracle software and applying updates via a software profile.

Option A is correct because missing OS credentials prevent NDB from establishing the required connection to the VM, disabling the Update button.

Option B (Database parameters are missing) is incorrect because while database parameters are important for configuration, they do not directly control the visibility of the Update button for patching.

Option C (Oracle DB engines cannot be patched) is incorrect as NDB explicitly supports patching Oracle databases when properly configured.

Option D (Software profile is not published) is incorrect because an unpublished software profile might limit availability to users, but the Update button’s presence relies on VM connectivity, not profile publication status.

To resolve this, the administrator must register valid OS credentials for the VM in NDB, enabling the patching functionality.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Patching Database Engines

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Missing Update Button in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles

To release PostgreSQL HA instances using a dedicated subnet in Nutanix Database Service (NDB), the administrator must create a network profile that defines the subnet and its associated VLAN. Before creating this network profile, it is mandatory to add a VLAN to the NDB Networks configuration. This VLAN ensures that the dedicated subnet is recognized and manageable within NDB, allowing the HA instances to be provisioned with isolated network connectivity. The VLAN must be configured in the NDB Networks page to be available for selection during network profile creation.

Option A (The subnet in Prism Element must be IPAM configured) is incorrect because IP Address Management (IPAM) configuration in Prism Element is optional and not a mandatory prerequisite for creating a network profile in NDB.

Option B (The DB VMs must be registered first) is incorrect because VM registration is a subsequent step, not a prerequisite for network profile creation.

Option C (A VLAN must be added to NDB networks) is correct as it is a required step to define the network infrastructure before creating the profile.

Option D (Configure Network Segmentation) is incorrect because network segmentation is an advanced feature and not mandatory for basic network profile setup.

This ensures the dedicated subnet is properly integrated into NDB for HA provisioning.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring Network Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment