Free NCP-DB Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

To ensure the NDB server, NDB agent, and NDB database agent can communicate with the registered

cluster via REST API calls, port 2009 must be opened. This port is used by NDB components to

facilitate RESTful communication with the Nutanix cluster (e.g., Prism Element or Prism Central) for

operations such as provisioning, monitoring, and management. Proper firewall configuration to

allow traffic on this port is a prerequisite for NDB’s integration with the cluster.

Other options are incorrect:

B . 3205: Not a standard NDB port; used for other Nutanix services.

C . 3260: Associated with iSCSI, not REST API communication.

D . 9440: Used for Prism Element’s HTTPS management interface, not NDB-specific REST calls.

Thus, the verified answer is A, reflecting NDB’s REST API requirements.

Official Nutanix Database Automation Reference:

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring

an NDB Solution, Lesson 2.1: Network and Port Requirements.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section

2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v6.10).

Nutanix NDB Installation Guide: "Network Ports and Protocols" section, specifying port 2009.

There are two ways to upgrade an NDB Server: one-click upgrade and offline upgrade. One-click

upgrade is the recommended method, as it automatically downloads and installs the latest NDB

software version from the Nutanix portal. Offline upgrade is an alternative method, which requires

you to manually download the NDB software bundle and upload it to the NDB Server VM. Both

methods require you to have a valid Nutanix account and an internet connection. Reference::

Nutanix Certified Professional - Database Automation (NCP-DB), Section 6 - Administer an NDB

Environment

Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 10, Objective 6.2

Nutanix Database Management & Automation (NDMA) course, Module 6, Lesson 6.1 - NDB Software

Upgrade

NDB supports patching for PostgreSQL database instances. Patching for PostgreSQL is validated on

VMs provisioned by NDB (greenfield deployments). To patch PostgreSQL database server VMs, you

must create a software profile version by uploading the PostgreSQL update file in NDB. You can then

use the PostgreSQL update to patch other database server VMs or provision a new database server

VM with the updated software profile. The first step in the NDB patching workflow is to create a

software profile version with the desired PostgreSQL version.

Reference::

Nutanix Database Automation (NCP-DB) Course Details, Section 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.1: Perform Database

Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) User Guide, Section 4.4: Patch PostgreSQL Database

Software

In Nutanix Era, an administrator can modify the Alert Severity level by navigating to the Alerts

Policies from the dropdown menu. Once there, they can select the Policy that needs to be modified

and set the desired severity level1. This allows the administrator to customize the alerts according to

their requirements, ensuring that they are notified of the most critical events in their

environment21.

To add Time Machine data access to a Nutanix cluster, the first step is to register the cluster in NDB.

This will allow NDB to discover and manage the databases and snapshots on the cluster. You can

register multiple Nutanix clusters in NDB using the Add Cluster option in the NDB settings page. You

can also specify the cluster role, such as source, target, or both, depending on the data access and

replication needs. Enabling or disabling multi-cluster in NDB is not the first step, as this is a global

setting that affects the entire NDB instance. Deleting the TM data from the source database is not the

first step, as this will remove the data protection and availability of the database. Reference::

Nutanix Database Management & Automation Training Course, Module 6: Managing NDB Multi-

Cluster, Lesson 1: NDB Multi-Cluster Overview, Slide 5: Registering Nutanix Clusters

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 6: Administer an

NDB Environment, Objective 6.4: Apply procedural concepts to add Nutanix clusters to NDB

To increase storage for a MongoDB database provisioned using NDB, the administrator needs to use

the extend_storage parameter in the input file for the NDB CLI. This parameter specifies the amount

of additional storage to be added to the database server VM in GB. For example, if the current

storage size is 100 GB and the administrator wants to increase it to 150 GB, the input file should

contain the following line:

extend_storage: 50

The other parameters are not relevant for this operation. The update parameter is used to update

the database software version, the database parameter is used to specify the database name, and

the data_percent parameter is used to specify the percentage of data to be copied during a clone

operation. Reference:: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database

Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist,

[Nutanix Database Automation User Guide].

Page files are temporary files that Windows uses to store data that does not fit in the physical

memory. Page files can interfere with the registration of a database server VM with NDB, as they can

cause errors or performance issues. Therefore, page files should be located in a separate drive or

partition from the C:\ drive, where the NDB agent and other files are installed. System, database, and

backup files do not prevent the registration of a database server VM with NDB, as long as they are

not corrupted or incompatible with the NDB requirements. Reference::

Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring

an NDB Solution, Lesson 2: Configuring an NDB Instance, Slide 13: Registering Database Server VMs

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and

Maintain an NDB Environment, Objective 4.1: Apply procedural concepts to register database server

VMs and databases

The default continuous recovery for the Gold SLA in Era Time Machine is 30 days1. This means that

the system keeps a continuous recovery point for the last 30 days, allowing you to restore your

database to any point within this period1.

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.

The administrator should perform a rolling upgrade, applying the patch to the secondary members

first, followed by the primary member, to accomplish the task of patching a MongoDB server cluster

within an NDB environment. A rolling upgrade is a method of applying patches or updates to a

cluster without downtime or interruption of service. The administrator can use the NDB patching

feature to perform a rolling upgrade on a MongoDB server cluster, which consists of a primary

member and one or more secondary members that form a replica set. The NDB patching feature

allows the administrator to select the software profile version, the database parameters profile, and

the network profile for the patching operation. The NDB patching feature also automates the steps of

the rolling upgrade, such as:

Step 1: The administrator initiates the patching operation on the NDB instance, and selects the

MongoDB server cluster to be patched.

Step 2: The NDB instance verifies the prerequisites and compatibility of the patching operation, and

creates a pre-patch snapshot of the MongoDB server cluster.

Step 3: The NDB instance applies the patch to the first secondary member of the MongoDB server

cluster, and waits for the patching to complete successfully.

Step 4: The NDB instance verifies the status and functionality of the patched secondary member, and

repeats the patching process for the remaining secondary members of the MongoDB server cluster,

one at a time.

Step 5: The NDB instance performs a failover of the primary member to one of the patched

secondary members, and applies the patch to the original primary member.

Step 6: The NDB instance verifies the status and functionality of the patched primary member, and

performs a failback of the primary member to the original primary member, if desired.

Step 7: The NDB instance creates a post-patch snapshot of the MongoDB server cluster, and

completes the patching operation.

Performing a rolling upgrade, applying the patch to the secondary members first, followed by the

primary member, is the recommended and best practice method of patching a MongoDB server

cluster within an NDB environment, as it ensures the high availability, consistency, and performance

of the MongoDB server cluster and the databases.

Performing a rolling upgrade, applying the patch to the primary member first, followed by the

secondary members, is not a valid or feasible method of patching a MongoDB server cluster within

an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB

server cluster and the databases. Applying the patch to the primary member first would disrupt the

replication and synchronization of the MongoDB server cluster, and would require manual

intervention and recovery steps to restore the MongoDB server cluster to a functional state.

Applying the patch to all nodes at once is not a valid or feasible method of patching a MongoDB

server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency

of the MongoDB server cluster and the databases. Applying the patch to all nodes at once would

require shutting down the entire MongoDB server cluster, and would expose the MongoDB server

cluster and the databases to potential errors, failures, and corruption during the patching process.

Disabling the replica set while patching is not a valid or feasible method of patching a MongoDB

server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency

of the MongoDB server cluster and the databases. Disabling the replica set while patching would

break the replication and synchronization of the MongoDB server cluster, and would require manual

intervention and recovery steps to re-enable the replica set and restore the MongoDB server cluster

to a functional state.

Reference::

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations,

Lesson 5.1: Nutanix Era Operations, slides 11-12, 15-16.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations,

Lesson 5.3: Nutanix Era Patching, slides 5-9.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations,

Lesson 5.4: Nutanix Era Patching Lab, slides 5-10.

Nutanix Database Management & Automation Training Course, Module 7: Nutanix Era

Troubleshooting, Lesson 7.1: Nutanix Era Troubleshooting, slide 6.

For an NDB offline upgrade, you need to download the upgrade bundle from the Nutanix Support

Portal and copy it to the NDB server. Then, you need to use the NDB CLI command upload

upgrade_bundle with the path parameter to specify the location of the upgrade bundle file. This

command will upload the upgrade bundle to the NDB server and verify its integrity. After uploading

the upgrade bundle, you can use the upgrade command to perform the upgrade. Reference:: Nutanix

Support & Insights, Cisco Nexus Data Broker Deployment Guide, Release 3.10.x

The NDB user interface supports multiple languages, including English, Chinese, and Japanese. You

can change the language pReference: in the NDB settings page. The NDB user interface does not

support Korean, French, or German languages at this time. Reference::

Nutanix Database Management & Automation Training Course, Module 1: Introduction to Nutanix

Era, Lesson 1: Nutanix Era Overview, Slide 7: NDB User Interface

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 1: Describe NDB

Concepts, Objective 1.6: Languages

Nutanix Database Service (NDB) uses software profiles for database patching to keep your databases

secure and optimized1. When a new database is provisioned, it will be on your current

environment’s database version to maintain consistency and stop version sprawl1. Therefore, after

an administrator has applied an Oracle security patch to a database server VM registered in Era, the

change can be made available to other existing database instances by creating a new software profile

in Era from the patched VM1.

The correct answer is D because it matches the requirement of taking multiple snapshots per day

and retaining them for one week. Option A is incorrect because it only takes one snapshot per day,

which is not enough for the administrator’s need. Option B is incorrect because it only retains the

snapshots for one week, which means the older snapshots will be deleted after seven days. Option C

is incorrect because it only takes two snapshots per week, which is not frequent enough for the

administrator’s need.

Reference:: The following sources provide more information about the SLA retention policies and

how to create and modify them in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases

Using Time Machine, Lesson 4.1: Creating and Modifying SLA Retention Policies

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section

5 - Protect NDB-managed Databases Using Time Machine

Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine,

Section 6.1: Creating and Modifying SLA Retention Policies

The correct answer is C because it follows the recommended procedure for applying a CU to a SQL

Server Software Profile in NDB. By applying the patch to the profile VM, the administrator ensures

that the CU is compatible with the existing Software Profile settings and configuration. By creating a

new Software Profile version, the administrator preserves the previous version of the Software

Profile for rollback purposes and allows the new version to be tested and published. Option A is

incorrect because it deletes the existing Software Profile, which may cause data loss and prevent

rollback. Option B is incorrect because it does not apply the patch to the profile VM, which may result

in errors or inconsistencies in the Software Profile. Option D is incorrect because it creates a new

Software Profile instead of a new version, which may cause confusion and duplication.

Reference:: The following sources provide more information about the Software Profile management

and patching in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 5: Patching Databases Using

NDB, Lesson 5.2: Creating and Modifying Software Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section

4 - Operate and Maintain an NDB Environment

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.2:

Creating and Modifying Software Profiles

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.3:

Testing and Publishing Database Patches

The Database Agent is used to temporarily store the transaction logs of the source database before

they are copied to the log. This is a critical component for ensuring data consistency and recovery in

database operations.

Reference:: Nutanix Database Automation documentation, focusing on database agents and their

roles in transaction log management.

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 Reference:

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) v6.5 Knowledge Objectives, Section

2: Deploy and Configure an NDB Solution (applicable to v6.10 as foundational concepts remain

consistent).

Nutanix Support & Insights Portal: "Configuring iSCSI Data Services IP for Nutanix Volumes" (general

Volumes configuration applicable to NDB).

The correct answer is B and D because these are the two status values that can be set within the

Alerts Dashboard in NDB. Resolved means that the alert has been fixed and no longer requires

attention. Acknowledged means that the alert has been seen and is being worked on. Option A is

incorrect because Auto is not a status value, but a mode that automatically resolves alerts based on

predefined rules. Option C is incorrect because Data Resiliency is not a status value, but a feature

that ensures the availability and integrity of the data in NDB.

Reference:: The following sources provide more information about the Alerts Dashboard and its

status values in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 3: Monitoring Alerts and

Storage Usage Within an NDB Implementation, Lesson 3.1: Monitoring Alerts

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section

3 - Monitor Alerts and Storage Usage Within an NDB Implementation

Nutanix Database Service (NDB) User Guide, Chapter 3: Monitoring Alerts and Storage Usage Within

an NDB Implementation, Section 3.1: Monitoring Alerts

[Nutanix Support & Insights], Resolving All Alerts Related to a Database or Database Server VM in

NDB

To apply the latest OS security patches on a Windows server managed by NDB, the user should

create and apply a Maintenance Plan within the NDB interface. NDB provides a Maintenance Plan

feature that allows administrators to schedule and automate OS patching for database server VMs,

ensuring patches are applied in a controlled manner without disrupting database operations. This

includes validating the patch process, rolling back if needed, and maintaining compliance with

security standards. The plan can be configured to target the specific Windows server and include the

latest security updates from Microsoft.

Other options are incorrect or insufficient:

A . Reboot the system: A reboot alone does not apply patches; it may only activate previously

installed updates.

C . Update the database: This focuses on database software, not OS security patches.

D . Use update functionality directly on the VM: Manual updates bypass NDB’s control, risking

inconsistency and potential downtime without proper validation.

Thus, the verified answer is B, leveraging NDB’s centralized maintenance capabilities.

Official Nutanix Database Automation Reference:

Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and

Patching, Lesson 6.3: Creating Maintenance Plans.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section

6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v6.10).

Nutanix NDB Administration Guide: "Maintenance Plans for OS Patching" section.

The NDB alert retention feature allows the database administrator to configure the duration for

which the NDB alerts are stored and displayed in the NDB instance. The NDB alert retention feature

supports alert retention globally, meaning that the same retention period applies to all the alerts

generated by the NDB instance, regardless of the source cluster, policy, or operation. The database

administrator can set the alert retention period from 1 day to 365 days, or choose to retain the alerts

indefinitely. The NDB alert retention feature helps to manage the storage space and the visibility of

the NDB alerts.

The NDB alert retention feature does not support retention at the individual policy, grouped policy,

or registered cluster level. The NDB alert retention feature applies to all the alerts uniformly, and

does not allow the database administrator to specify different retention periods for different policies

or clusters.

Reference::

Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment,

Lesson 3.2: Nutanix Era Deployment, slide 11.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations,

Lesson 5.1: Nutanix Era Operations, slide 6.