Nutanix NCP-DB-6.5 Practice Exams
Last updated on Oct 06,2026- Exam Code: NCP-DB-6.5
- Exam Name: Nutanix Certified Professional - Database Automation (NCP-DB) v6.5
- Certification Provider: Nutanix
- Latest update: Oct 06,2026
Question #31
An administrator needs to increase storage for a MongoDB database provisioned using NDB. After launching the NDB CLI, the administrator begins with creating the input file for this operation.
Which parameter should the administrator include within the input file?
- A . extend_storage
- B . update
- C . database
- D . data_percent
Correct Answer: A
A
Explanation:
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].
A
Explanation:
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].
Question #32
An administrator is tasked with providing a Jr DBA with access to NBD with limited capabilities.
This user should only be able to:
• Provision Databases
• Provision Database Servers
• Create Ones
• Refresh Clones
• Patch Database Servers
How can the administrator complete this task?
- A . Clone the Database Admin role, and add the desired privileges.
- B . Create a role with only those privileges, assign the role to the Jr DBA user.
- C . Create a user for the Jr DBA, and assign only those privileges.
- D . Clone the Database Admin role, and remove all but the desired privileges.
Correct Answer: B
B
Explanation:
The correct answer is B because it allows the administrator to create a custom role with the specific privileges that the Jr DBA user needs, and then assign that role to the user. This way, the administrator can control the access level of the Jr DBA user without affecting the existing roles or users in NDB. Option A is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then adding more privileges, which is unnecessary and redundant. Option C is incorrect because it involves creating a user for the Jr DBA, but not assigning a role to the user, which means the user will not have any privileges in NDB. Option D is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then removing some of the privileges, which is inefficient and risky.
Reference: The following sources provide more information about the user roles and privileges in NDB:
Nutanix Database Management & Automation (NDMA) course, Module 8: Administering an NDB Environment, Lesson 8.6: Managing Access Controls in NDB
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 6 – Administer an NDB Environment
Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.6: Managing Access Controls in NDB
B
Explanation:
The correct answer is B because it allows the administrator to create a custom role with the specific privileges that the Jr DBA user needs, and then assign that role to the user. This way, the administrator can control the access level of the Jr DBA user without affecting the existing roles or users in NDB. Option A is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then adding more privileges, which is unnecessary and redundant. Option C is incorrect because it involves creating a user for the Jr DBA, but not assigning a role to the user, which means the user will not have any privileges in NDB. Option D is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then removing some of the privileges, which is inefficient and risky.
Reference: The following sources provide more information about the user roles and privileges in NDB:
Nutanix Database Management & Automation (NDMA) course, Module 8: Administering an NDB Environment, Lesson 8.6: Managing Access Controls in NDB
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 6 – Administer an NDB Environment
Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.6: Managing Access Controls in NDB
Question #33
An administrator needs to work with databases and time machines, but not database parameter profiles.
Which role satisfies this requirement?
- A . Database Administrator (DBA)
- B . super Administrator
- C . Database Infrastructure Administrator
- D . Infrastructure Administrator
Correct Answer: A
A
Explanation:
In the Nutanix Database Automation (NCP-DB) framework, the role that allows an administrator to work with databases and time machines, but not database parameter profiles, is the Database Administrator (DBA)123. This role provides the necessary permissions to manage databases and time machines, which are essential components of the Nutanix Era solution. However, it does not grant access to database parameter profiles, which are typically managed by other roles45.
A
Explanation:
In the Nutanix Database Automation (NCP-DB) framework, the role that allows an administrator to work with databases and time machines, but not database parameter profiles, is the Database Administrator (DBA)123. This role provides the necessary permissions to manage databases and time machines, which are essential components of the Nutanix Era solution. However, it does not grant access to database parameter profiles, which are typically managed by other roles45.
Question #34
An administrator needs to perform patching on a MongoDB server cluster within an NDB environment.
How should the administrator accomplish this task?
- A . Perform a rolling upgrade, applying the patch to the primary member first, followed by the secondary members.
- B . Apply the patch to all nodes at once.
- C . Perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member.
- D . Disable the replica set while patching.
Correct Answer: C
C
Explanation:
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.
C
Explanation:
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.
Question #35
When an Oracle database is upgraded using Era, what is the type of upgrade category?
- A . In-place upgrade
- B . Out-of-place upgrade
- C . Disruptive upg raze
- D . Non-disruptive upgrade
Correct Answer: A
A
Explanation:
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.
A
Explanation:
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.
Question #36
How would an administrator enter the NDB command line to change the static IP address on the NDB VM?
- A . era-server
- B . era
- C . cerebro_cli
- D . arithmos cli
Correct Answer: C
C
Explanation:
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.
Reference: 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
C
Explanation:
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.
Reference: 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
Question #37
What is required to cre110ate a network profile in Era?
- A . The network must contain static IP addresses.
- B . The network must be added to Era.
- C . The network must be managed by Era.
- D . The network must provide IP address management.
Correct Answer: B
B
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, to create a network profile in Era, the network must be added to Era1. This is because Era needs to have control over the network in order to manage the databases effectively1. Once the network is added to Era, it can be used for various operations such as provisioning new databases, managing existing databases, and more1.
B
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, to create a network profile in Era, the network must be added to Era1. This is because Era needs to have control over the network in order to manage the databases effectively1. Once the network is added to Era, it can be used for various operations such as provisioning new databases, managing existing databases, and more1.
Question #38
Where can an administrator configure a custom SSL certificate for Era?
- A . Era CLI
- B . Era UI
- C . Prism CLI
- D . Prism Ul
Correct Answer: B
B
Explanation:
An administrator can configure a custom SSL certificate for Era through the Era User Interface (UI)1. This can be done by logging into the Nutanix Console and selecting SSL Certificates from the drop-down list inside the gear icon23. In the SSL Certificate dialog box, the administrator can click Replace Certificate, then select the Import Key and Certificate radio button23. This process ensures secure communication within the Nutanix Era environment4.
B
Explanation:
An administrator can configure a custom SSL certificate for Era through the Era User Interface (UI)1. This can be done by logging into the Nutanix Console and selecting SSL Certificates from the drop-down list inside the gear icon23. In the SSL Certificate dialog box, the administrator can click Replace Certificate, then select the Import Key and Certificate radio button23. This process ensures secure communication within the Nutanix Era environment4.
Question #39
An administrator is tasked with auditing NDB SLAs.
What data will the administrator be reviewing?
- A . Snapshot schedules
- B . Clone Management
- C . Data retention policies
- D . Recovery Time Objective
Correct Answer: C
C
Explanation:
NDB SLAs are service level agreements that define the data protection and recovery objectives for NDB-managed databases. NDB SLAs consist of data retention policies that specify how long the snapshots and log backups of a database are kept in the Time Machine. Data retention policies can be customized to meet different business and compliance requirements, such as daily, weekly, monthly, or yearly retention periods. NDB SLAs also determine the frequency and schedule of the snapshots and log backups, as well as the storage location and replication options. An administrator who is tasked with auditing NDB SLAs will be reviewing the data retention policies of each database and Time Machine, as well as the snapshot and log backup history and status. The administrator will also be able to monitor the storage usage and performance of the NDB SLAs, and modify or delete the SLAs as needed. The other options are not part of the NDB SLAs, but rather separate features or concepts of NDB. Snapshot schedules are the intervals at which NDB takes snapshots of the databases, which are determined by the SLAs. Clone management is the process of creating, refreshing, or deleting database clones from the Time Machine. Recovery time objective (RTO) is the maximum acceptable time for restoring a database after a failure, which is influenced by the SLAs, but not defined by them.
Reference: Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Section 5 – Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies
Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: SLA Concepts Nutanix Database Service (NDB) User Guide, Chapter 6: SLAs, Section: SLA Overview
C
Explanation:
NDB SLAs are service level agreements that define the data protection and recovery objectives for NDB-managed databases. NDB SLAs consist of data retention policies that specify how long the snapshots and log backups of a database are kept in the Time Machine. Data retention policies can be customized to meet different business and compliance requirements, such as daily, weekly, monthly, or yearly retention periods. NDB SLAs also determine the frequency and schedule of the snapshots and log backups, as well as the storage location and replication options. An administrator who is tasked with auditing NDB SLAs will be reviewing the data retention policies of each database and Time Machine, as well as the snapshot and log backup history and status. The administrator will also be able to monitor the storage usage and performance of the NDB SLAs, and modify or delete the SLAs as needed. The other options are not part of the NDB SLAs, but rather separate features or concepts of NDB. Snapshot schedules are the intervals at which NDB takes snapshots of the databases, which are determined by the SLAs. Clone management is the process of creating, refreshing, or deleting database clones from the Time Machine. Recovery time objective (RTO) is the maximum acceptable time for restoring a database after a failure, which is influenced by the SLAs, but not defined by them.
Reference: Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Section 5 – Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies
Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: SLA Concepts Nutanix Database Service (NDB) User Guide, Chapter 6: SLAs, Section: SLA Overview
Question #40
Which Time Machine feature allows developers to automate the data refresh for their clones?
- A . Manual Backup
- B . update
- C . Log Catchup
- D . Schedule
Correct Answer: D
D
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, the Schedule feature of the Time Machine allows developers to automate the data refresh for their clones1. This feature eliminates the time-consuming, complex process of database clone/refresh, allowing admins to create database clones/refresh to any point in time in just a few minutes1. Please refer to the official Nutanix documentation and training materials for more detailed information2.
D
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, the Schedule feature of the Time Machine allows developers to automate the data refresh for their clones1. This feature eliminates the time-consuming, complex process of database clone/refresh, allowing admins to create database clones/refresh to any point in time in just a few minutes1. Please refer to the official Nutanix documentation and training materials for more detailed information2.