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
Which statement best describes what happens when a 3rd-party backup tool is chosen to manage log backups for Microsoft SQL in NDB?
- A . If exclusive log access is not granted to NDB, the Point-in-Time (PIT) recovery will not be supported, but snapshot-based recovery of the databases is supported.
- B . Third-party backups vendors can continue to backup the archived logs from the database log destination. NDB will still be able to capture the logs, considering the log catch-up begins before the logs get backed up
- C . If exclusive log access is not granted to NDB, the Point-in-Time (PIT) recovery will be supported, but snapshot-based recovery of the databases is not supported.
- D . Third-party backups vendors can continue to backup the binary logs from the binary log location. NDB will still be able to capture the logs, considering the log catch-up begins before the logs get purged.
B
Explanation:
NDB supports two modes of log backup management for Microsoft SQL databases: NDB-managed and 3rd-party managed. In the NDB-managed mode, NDB takes full control of the log backups and stores them in the Cerebro log location. In the 3rd-party managed mode, NDB allows the use of external backup tools to backup the logs from the database log destination. However, NDB still needs to capture the logs for its own operations, such as point-in-time recovery, clone refresh, and log catch-up. Therefore, NDB will periodically scan the database log destination and copy the logs to the Cerebro log location. This process requires that the log catch-up begins before the logs get backed up by the 3rd-party tool, otherwise NDB will miss some logs and the operations will fail. If the 3rd-party tool grants exclusive access to the logs, then NDB will not be able to capture them at all, and the operations will not be supported.
Reference: Nutanix Database Management & Automation (NDMA) course, Module 5, Lesson 5.2 – Log Backup Management
Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Log Backup Management
What is the first step to add Time Machine (TM) data access to a Nutanix cluster?
- A . Enable multi-cluster in NDB.
- B . Disable multi-cluster in ND8.
- C . Register the required Nutanix clusters in ND8.
- D . Delete the TM data from the source database.
C
Explanation:
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
Which action must an administrator take in Era Networks before using Era to provision a MSSQL AG cluster?
- A . A network in each data center must be configured for Era.
- B . A private network must be configured in Era for the heartbeat traffic.
- C . A that has a static pool managed by Era must be configured.
- D . A network that has a DHCP pool must be configured in Era.
B
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, before using Era to provision a MSSQL AG cluster, an administrator must configure a private network in Era for the heartbeat traffic1. This is because the heartbeat traffic is crucial for maintaining the health and status of the MSSQL AG cluster. The heartbeat traffic is used by the nodes in the cluster to communicate with each other and check the status of the other nodes. If a node does not receive a heartbeat from another node within a certain time frame, it assumes that the other node has failed and takes appropriate action234.
An administrator needs to change the maximum number of database connections during the cloning workflow.
Which Era profile should the administrator choose?
- A . Compute
- B . Database Parameters
- C . Network
B
Explanation:
In Nutanix Database Automation (NCP-DB), the Database Parameters profile is used to manage database-specific settings, including the maximum number of database connections. This profile would be the appropriate choice when an administrator needs to change these settings during the cloning workflow1.
What is purpose of the NDB Database Agent service?
- A . Temporarily stores the transaction logs.
- B . Hosts one or more source databases for the same time machine.
- C . Schedules and monitors the NDB-related operations.
- D . Contains an instance of the database engine software.
C
Explanation:
The correct answer is C because the NDB Database Agent service is responsible for scheduling and monitoring the NDB-related operations, such as provisioning, patching, cloning, and restoring databases. The NDB Database Agent service is deployed on the NDB server and on each of the database server VMs provisioned by NDB. It contains the tools required to perform each task and communicates with the NDB server through the NDB API. The other options are not correct because they describe different components or functions of the NDB solution. Option A is not correct because the transaction logs are not stored by the NDB Database Agent service, but by the NDB Time Machine service, which is a distributed file system that stores the database snapshots and logs. Option B is not correct because the source databases are not hosted by the NDB Database Agent service, but by the database server VMs, which are virtual machines that contain an instance of the database engine software and the database files. Option D is not correct because the NDB Database Agent service does not contain an instance of the database engine software, but only the tools required to perform the NDB-related operations. The database engine software is installed on the database server VMs, which are provisioned by NDB using the profiles defined by the administrator.
Reference: 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
What is the first step to install NDB on a Nutanix AHV cluster?
- A . NDB is offered as a SaaS service and doesn’t require any installations.
- B . Download the QCOW2 image file of NDB and upload it to Prism Element.
- C . Run LCM update to get the latest version of NDB.
- D . Open Prism Central and enable the NDB VM in the settings menu.
B
Explanation:
To install NDB on a Nutanix AHV cluster, you need to download the QCOW2 image file of NDB from the Nutanix Support Portal and upload it to Prism Element. This image file contains the NDB software and the CentOS operating system. After uploading the image, you need to create a VM from the image and configure the network settings. Then, you need to register the NDB VM with Prism Central and enable the NDB service in the settings menu.
Reference: Nutanix Support & Insights, Professional Services: NDB Database Cloning
What are the three severity levels displayed under the Alert dashboard?
- A . Critical. Waiting, Failed
- B . Failed, Warning, Stopped
- C . Critical, Warning Info
- D . Failed, Warning, Error
C
Explanation:
The Alerts dashboard in Nutanix displays alert messages with three severity levels: Critical, Warning, and Info1. These severity levels help users understand the importance and urgency of each alert, allowing them to prioritize their responses accordingly1.
An administrator needs to roll back an Oracle patch on a database server VM using NDB.
What is required for this action to be successful?
- A . The patch must have been applied using NDB.
- B . The database must be shut down.
- C . The patch must have been applied on Grid home only using NDB.
- D . The database must be in read-only mode.
A
Explanation:
To roll back an Oracle patch on a database server VM using NDB, the patch must have been applied using NDB in the first place. This is because NDB maintains a patch inventory and history for each database server VM and database that it manages. NDB uses this information to determine which patches can be rolled back and how to revert the changes made by the patch. If the patch was applied outside of NDB, NDB would not have the patch information and would not be able to roll back the patch. Therefore, the patch must have been applied using NDB for the rollback action to be successful. The other options are not required for the rollback action. The database does not need to be shut down or in read-only mode, as NDB can perform the rollback operation online. The patch does not need to be applied on Grid home only, as NDB can roll back patches applied on both Grid home and Database home.
Reference: Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Section 4 – Operate and Maintain an NDB Environment, Objective 4.4: Determine the correct method to apply Linux OS patches
Nutanix Database Management & Automation (NDMA) Course, Module 5: Nutanix Database Service (NDB) Patching, Lesson 5.1: Patching Overview, Topic: Patching Concepts
[Nutanix Database Service (NDB) User Guide], Chapter 7: Patching, Section: Rolling Back a Patch
An administrator is trying to register a database server VM with NDB.
Which file types will prevent the registration from being successful if located in the C: drive?
- A . Page
- B . System
- C . Database
- D . Backup
A
Explanation:
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
Refresh the source database
(C) l. update Log Catch-up interval from Tme Machine 2. Refresh the source database
C) 1. Update Log Catch-up interval from Tame Machine 2. Refresh the clone database
How is the size of a database time machine defined?
- A . Only the size of all reclaimable snapshots maintained by Era
- B . The size of all snapshots and/or transaction logs maintained by Era
- C . Only the size of all transaction logs maintained by Era
- D . The size of all snapshots and clones maintained by Era
B
Explanation:
The Nutanix Era platform provides a feature called Time Machine, which is designed to manage the lifecycle of database copies and clones1. When a new table is added to the source database, the administrator should perform a Log Catch-up using the source database’s Time Machine. This action ensures that the Time Machine captures the latest state of the source database, including the newly added table1. After performing the Log Catch-up, the administrator should refresh the clone database. The refresh operation updates the clone with the latest state captured by the Time Machine, thereby publishing the new table to the clone1.