Free Practice Questions for Nutanix NCP-DB Exam

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.

For restoring a database provisioned on Storage Spaces, especially when virtual disks are shared among multiple databases, the supported method is a copy-based restore via the NDB GUI. This method allows for a precise and controlled restoration process suitable for shared storage environments.

The correct answer is B because the Time Machine feature of NDB collects logs and snapshots from databases and stores them in a distributed file system. The Time Machine enables the administrator to protect, clone, and restore databases using the SLA policies and the NDB UI or API. The Time Machine also manages the replication of database snapshots in an NDB multicluster environment. The other options are not correct because they describe different features or functions of NDB. Option A is not correct because Database Restore is an operation that uses the Time Machine to restore a source database or a clone to a previous point in time. Option C is not correct because SLA is a policy that defines the frequency and retention of database snapshots and logs. Option D is not correct because One-click Patching is a feature that allows the administrator to test, publish, and apply database patches using the NDB UI or API. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Support & Insights

When running the Linux prerequisites script for NDB, the -t argument is a required parameter that specifies the timeout interval. This argument defines the maximum time (in seconds) the script will wait for certain operations (e.g., connectivity checks, package installations) to complete before timing out. This is critical during the preinstallation phase to ensure the environment is properly configured and responsive, avoiding indefinite hangs. Other options are not associated with -t:

A. Operating System type: This is not a typical argument for the prerequisites script.

C. NDB server IP: This would be specified separately (e.g., via -s or a similar flag).

D. Database engine: This is irrelevant to the prerequisites script, which focuses on system setup.

Thus, the verified answer is B, aligning with the script’s purpose of managing execution timeouts.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.1: Running Prerequisites Scripts.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v7.5).

Nutanix NDB Installation Guide: "Running the Linux Prerequisites Script" section, detailing -t usage.

When upgrading NDB and the upgrade includes updates to out-of-the-box (OOB) software profiles (e.g., predefined profiles for database software like PostgreSQL, SQL Server, etc.), NDB manages older versions of these profiles based on their usage. If the older OOB software profiles are not actively in use by any database VMs, NDB automatically deletes all versions of those profiles from its metadata and associated protection domains during the upgrade process. This cleanup mechanism helps maintain a lean and efficient system by removing obsolete profiles that are no longer relevant or required.

Option A is incorrect because the condition about Time Machines and snapshots in the last 24 hours is not a documented criterion for profile deletion during an NDB upgrade.

Option B is correct as it reflects NDB’s behavior of removing unused OOB software profiles during upgrades to optimize resource usage and metadata.

Option C is incorrect because shutting down database VMs does not trigger automatic deletion of software profiles; the key factor is whether the profiles are in use.

Option D is incorrect because the concept of a "base version" is not relevant here; deletion depends solely on whether the profiles are unused, not on versioning specifics.

This behavior ensures that only active and necessary profiles persist post-upgrade, streamlining administration.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Upgrading NDB, Section: Handling Software Profile Updates

Nutanix Support & Insights, Technical Note: "NDB Upgrade Process and Software Profile Management"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 6: Administer an NDB Environment

NDB executes complex lifecycle operations as workflows containing multiple subtasks. In the Operations dashboard, an administrator can open an operation and review each subtask’s name, status, start time, end time, and duration. If the overall operation fails, this task-level view identifies the precise workflow step that failed, allowing the administrator to investigate the relevant error instead of relying on one generic timeout code. The dashboard does not automatically capture all network traffic, create an external support case, or guarantee an automatic database rollback. Depending on the failed operation, remediation or rollback may require a separate supported procedure. Nutanix’s official instructions for viewing operation logs confirm that detailed subtask information is available for monitoring and troubleshooting operations.

A Time Machine frozen status indicates that the database that was associated with the Time Machine has been de-registered from NDB, but the Time Machine itself has not been deleted. This means that the Time Machine still contains the snapshots and logs of the de-registered database, but it cannot perform any further operations on it. To resume the normal functioning of the Time Machine, the administrator can either re-register the database with NDB, or delete the Time Machine and free up the storage space.

 Nutanix Support & Insights, section “Resolving All Alerts for a Time Machine”

To change the static IP address on the NDB VM, an administrator would need to enter the NDB command line using the cerebro_cli command. The cerebro_cli command is used to access the Cerebro service, which is responsible for managing the NDB instance and its components. The cerebro_cli command can be run from the NDB VM or from any other VM that has network connectivity to the NDB VM. The cerebro_cli command has various subcommands and options to perform different tasks, such as changing the IP address, hostname, password, or certificate of the NDB VM. To change the static IP address, the administrator would need to use the cerebro_cli network update subcommand with the appropriate parameters, such as the new IP address, netmask, gateway, and DNS servers. The cerebro_cli network update subcommand also requires the administrator to provide the current password of the NDB VM for authentication. After changing the IP address, the administrator would need to restart the NDB VM for the changes to take effect. References:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.2: Configure an NDB Instance

Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.2: Configuring NDB, Topic: Changing the IP Address of the NDB VM

Nutanix Database Service (NDB) Command Line Interface Guide, Chapter 2: Cerebro CLI, Section: cerebro_cli network update

The Nutanix Era Time Machine provides various capabilities depending on the Service Level Agreement (SLA) selected during database registration1. For a database with a Bronze SLA, the Time Machine supports both “Log Catch up” and "Snapshots"2. “Log Catch up” allows the Time Machine to keep up with the latest changes in the database by capturing log data2. “Snapshots” are point-in-time copies of the database that can be used for recovery or cloning2.

NDB sends alert notifications using configurations auto-populated from the cluster during the initial setup, typically relying on default SMTP settings. If a dedicated SMTP server is required (e.g., for security or compliance), the administrator must change the SMTP Server configuration in NDB Service. This is configured under the NDB Admin Center, where the administrator can specify the dedicated SMTP server’s details (e.g., hostname, port, credentials, and security settings like TLS/SSL).

Other options are incorrect:

A. IDP configuration in Admin Center IAM page: Identity Provider (IDP) settings are for authentication, not email alerts.

B. Alert Email configuration in Prism Element: Prism Element manages cluster alerts, not NDB-specific email settings.

D. SNMP configuration in Prism Central: SNMP is for network monitoring, not email notifications.

Thus, the verified answer is C, reflecting NDB’s alert notification setup.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.1: Configuring Alert Notifications.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.2: Manage Alerts (applicable to v7.5).

Nutanix NDB Administration Guide: "Configuring SMTP for Alerts" section.