[Q99-Q117] Latest Nutanix NCP-DB First Attempt, Exam real Dumps Updated [Oct-2026]

[Q99-Q117] Latest Nutanix NCP-DB First Attempt, Exam real Dumps Updated [Oct-2026]

October 29, 2026 latestexam 0 Comments

Rate this post

Latest Nutanix NCP-DB First Attempt, Exam real Dumps Updated [Oct-2026]

Get the superior quality NCP-DB Dumps Questions from LatestCram. Nobody can stop you from getting to your dreams now. Your bright future is just a click away!

NO.99 When managing Microsoft SQL Server instances with NDB, an administrator wants to simplify operations for multiple databases that have identical Recovery Point Objective and data-retention requirements.
If the administrator provisions the databases using the “Group Database with One Time Machine” configuration, which statement accurately describes the architecture?

All databases in the Database Group share one unified set of virtual storage disks.

Databases in a Database Group are automatically distributed across different SQL Server Always On Availability Group nodes.

A Database Group prevents an administrator from restoring or cloning an individual database.

Each database in the Database Group retains its own dedicated set of storage disks while being managed through one collective Time Machine and SLA.

A SQL Server Database Group in NDB is a logical protection construct for databases that have common recovery-point and retention requirements. The databases are managed by one collective Time Machine and SLA, allowing NDB to coordinate snapshots and log backups and reduce Time Machine sprawl. However, grouping does not merge all database files into one common virtual-disk set. Each database retains its own set of storage disks while participating in the group-level protection workflow. The group also does not force databases onto different Always On Availability Group nodes, and it does not prevent an administrator from restoring or cloning an individual database. Those facts eliminate A, B, and C. Option D correctly describes separate per-database storage combined with centralized Time Machine management. Nutanix NDB Database Groups

NO.100 Which statement correctly describes MongoDB patching in NDB?

Rolling patching is supported for replica sets.

Rolling patching is supported for sharded clusters.

All replica-set members are patched in parallel to reduce the patching duration.

The primary member is patched first.

NDB patches MongoDB replica sets through a rolling workflow designed to minimize database unavailability. It first applies the selected patch to available secondary members one at a time. After the secondary members are successfully patched and validated, NDB performs the required replica-set role transitions and patches the primary member last. This order preserves service availability and avoids simultaneously taking every voting member offline. Nutanix explicitly documents rolling upgrades for MongoDB replica sets; NDB does not patch all members in parallel, and the primary is not the first member patched. Current NDB documentation also lists patching and upgrading MongoDB sharded clusters as unsupported. Therefore, the verified positive statement about the supported patching workflow is that rolling patching is available for replica sets. Nutanix MongoDB cluster-patching documentation

NO.101 An administrator needs to capture the database transaction logs.
Which Time Machine operation does NDB use to satisfy this requirement?

Write-Ahead Logging

Log Flush

Log Catch-up

Snapshots

To capture database transaction logs in NDB, the Log Catch-up operation within the Time Machine is used.
Log Catch-up retrieves and applies transaction logs (e.g., PostgreSQL WAL, SQL Server logs) to a snapshot, ensuring the database can be restored to a specific point in time. This operation bridges gaps between snapshots by incorporating log data, maintaining a continuous recovery chain.
Other options are incorrect:
A). Write-Ahead Logging: A database feature (e.g., in PostgreSQL), not an NDB Time Machine operation.
B). Log Flush: Refers to writing logs to disk, not capturing them for recovery.
D). Snapshots: Capture the database state but do not handle transaction logs specifically.
Thus, the verified answer is C, aligning with NDB’s log management.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Time Machines.
Nutanix Certified Professional – Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 5:
Protect Databases Using NDB, Objective 5.2: Manage Time Machine Operations (applicable to v7.5).
Nutanix NDB Administration Guide: “Log Catch-up Operation” section.

NO.102 Which port should be opened to ensure the NDB server, NDB agent, and NDB database agent can communicate with the registered cluster via REST API calls?

2009

3205

3260

9440

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 References
* 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.

NO.103 An administrator needs to provision a PostgreSQL cluster instance with an external Load Balancer. Which software can be omitted on the Reference VM while creating the Software Profile?

Patron

HAProxy

keepalived

etcd

When provisioning a PostgreSQL cluster instance with an external load balancer in NDB, the administrator creates a software profile from a reference VM. The reference VM typically includes software like Patroni (for HA management), HAProxy (for internal load balancing), keepalived (for high availability IP management), and etcd (for distributed configuration). Since an external load balancer is used, the internal HAProxy can be omitted from the reference VM. NDB will rely on the external load balancer to distribute traffic, eliminating the need for HAProxy in the software profile, while the other components remain essential for cluster management.
Option A (Patroni) is incorrect because Patroni is required for PostgreSQL HA management.
Option B (HAProxy) is correct as it can be omitted when an external load balancer is configured.
Option C (keepalived) is incorrect because keepalived is needed for HA IP failover.
Option D (etcd) is incorrect because etcd is necessary for distributed configuration in the cluster.
This adjustment streamlines the profile for external load balancer use.
References
Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Creating Software Profiles for HA Instances Nutanix Certified Professional – Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Software Profiles

NO.104 What does a Time Machine frozen status indicate?

The database is paused on the database VM.

The database was de-registered from NDB without removing the associated time machine.

The NDB agent is stopped on the database VM.

The Time Machine is paused and all automatic snapshot and log catch-up activities are halted.

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”

NO.105 Within NDB, an administrator needs to register a PostgreSQL database server VM with a database.
Where should the database data and log files be located in order to successfully complete this task?

On a separate mount point

On the same mount point

On the same disk as the binary installation

On the same disk as the operating system

To register a PostgreSQL database server VM with a database on NDB, the database data and log files must be located on a separate mount point from the operating system and the binary installation. This is because NDB uses the mount point as the identifier for the database server VM and the database. If the data and log files are on the same mount point as the operating system or the binary installation, NDB will not be able to recognize them as a valid database server VM or database. Therefore, the administrator should create a separate mount point for the data and log files and specify it during the registration process. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [How to Allow Remote Access to PostgreSQL database], [5 Ways to Host PostgreSQL Databases], [Starting the Database Server].

NO.106 An administrator wants to apply patches to the Microsoft SQL Server databases in an NDB environment.
What needs to be done in NDB to accomplish this?

Create a Maintenance window schedule and associate the SQL server with that maintenance window in the Database VM Menu.

Apply the patch to the database VM then create a new software profile using that updated VM as the source.

Apply the patch to the database VM, then create a new software profile version using that updated database VM as the source, publish the updated software profile then apply that patch under the database VM Menu for each database server.

Create a new software profile version with the downloaded cumulative update from Microsoft, publish the updated software profile, then apply the update under the database VM Menu for each database server.

To apply patches to Microsoft SQL Server databases in an NDB environment, the administrator should follow a structured process:
* Create a new software profile version: Download the latest cumulative update (CU) or patch from Microsoft and use it to create a new version of the existing SQL Server Software Profile in NDB. This ensures the patch is integrated into NDB’s management framework.
* Publish the updated software profile: Promote the new version to “Published” status, making it available for use across the environment.
* Apply the update: Navigate to the “Database VM Menu” for each database server, select the updated software profile, and apply the patch. This automates the patching process while maintaining database consistency and allowing rollback if needed.
Other options are incorrect or incomplete:
* A. Create a Maintenance window schedule and associate the SQL server with that maintenance window in the Database VM Menu: Maintenance windows manage downtime, not patch application for databases.
* B. Apply the patch to the database VM then create a new software profile using that updated VM as the source: This manual approach bypasses NDB’s structured patching and lacks version control.
* C. Apply the patch to the database VM, then create a new software profile version using that updated database VM as the source, publish the updated software profile then apply that patch under the database VM Menu for each database server: This is overly complex and risky, as manually patching a VM first can lead to inconsistencies.
Thus, the verified answer is D, aligning with NDB’s best practices for database patching.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.2: Patching SQL Server Databases.
* 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: “Patching Microsoft SQL Server” section.

NO.107 One node of an NDB-managed three-node Oracle RAC cluster has become corrupted and the RAC environment must be restored. Which statement is valid regarding restoration through NDB?

NDB repairs the corruption at the storage layer and restores the failed node.

NDB restores only the failed RAC node.

NDB restores all nodes in the RAC environment.

NDB automatically resynchronizes the failed node from the other RAC nodes.

NDB treats an Oracle RAC database as one managed database rather than as unrelated per-node databases.
Nutanix documentation states that NDB creates a single Time Machine for a registered RAC database while collecting metadata for all nodes and instances forming that database. Consequently, an NDB database restore targets the RAC database environment as a whole, making option C the valid statement among the choices. It is not a node-level storage-repair or operating-system reconstruction function, and NDB does not restore only one RAC node or automatically rebuild that node by copying it from its peers. If the node’s VM, operating system, Grid Infrastructure, or database binaries are corrupted, those components may require separate remediation before the database-level restore. Nutanix’s Oracle RAC documentation confirms the single- Time-Machine management model, and its restore procedure applies to RAC databases.

NO.108 Which two options can NDB leverage to refresh a database clone? (Choose two.)

Cerebro logs

Snapshots

Transaction logs

Templates

NDB can leverage snapshots and transaction logs to refresh a database clone to the latest state of the source database. Snapshots are point-in-time copies of the database that are stored on the Nutanix cluster. Transaction logs are records of the changes made to the database after the snapshot was taken. NDB can use either snapshots or transaction logs, or a combination of both, to refresh a database clone. Cerebro logs and templates are not used for refreshing database clones. Cerebro logs are used for log catch-up operations, which are different from refresh operations. Templates are used for provisioning new databases, not for refreshing existing ones. References:
* Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.3 – Refreshing Clones
* Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Clone Database Management

NO.109 An administrator would like to provide a group of users the ability to add a new VLAN or IP Pool in Era.
What minimum role should the administrator assign to this group?

Super Admin

Database Admin

Infrastructure administrator

Database Infrastructure Admin

In Nutanix Era, the ability to add a new VLAN or IP Pool is typically associated with the role of an Infrastructure Administrator12. This role has the necessary permissions to manage network configurations, including the creation of VLANs and IP Pools12. It’s important to note that the exact permissions may vary depending on the specific configuration and policies of your organization12.

NO.110 An administrator needs to patch multiple Microsoft SQL Server databases managed by NDB.
Which NDB capability simplifies this operation?

Database Grouping

Software Profile versions

Database Cloning

Maintenance Windows

Maintenance Windows simplify coordinated patching by allowing administrators to define when operating- system or database software updates should run and associate multiple database server VMs with that schedule. At execution time, NDB connects to the associated servers, performs its prechecks, identifies applicable patching tasks, and updates the database software to the recommended published software profile version. Software profile versions contain the target software or patch level, but they do not independently coordinate patch execution across multiple servers. Database Groups primarily provide collective protection, snapshot, log-management, clone, and recovery behavior for related SQL Server databases; they are not the scheduling mechanism for fleet patching. Database Cloning is unrelated to software maintenance. The official Nutanix Maintenance Window documentation states that database patching performed through a maintenance window updates databases to the recommended software profile version.

NO.111 An administrator needs to provision a 3-node MSSQL Server AG with the following configuration:
* Two database server VMS including the primary replica on a local site
* A third database server VM on a remote site
How many IP addresses will the network at each site require?

2 Cluster VIP and 1 listener IP on the local site

1 Cluster VIP and 1 listener IP on the remote site
2 IPs in the local site and 1 on the remote site for the database server nodes
1 Cluster VIP on the local site
1 Cluster VIP and 1 Listener IP on the remote site
2 IPs in the local site and 1 on the remote site for the database server nodes

I Cluster VIP end I Listener IP on the local site
1 Listener IP on the local site
2 IPs in the local site and I on the remote site for the database server nodes

Cluster VIP end I Listener IP on the local site
1 Cluster VIP and 1 Listener IP on the remote site
2 IPs in the local site and 1 on the remote site for the database server nodes

The correct answer is D. When setting up a 3-node MSSQL Server AG with two database server VMs on a local site and a third database server VM on a remote site, the network at each site will require the following IP addresses:
* 1 Cluster VIP and 1 Listener IP on the local site123.
* 1 Cluster VIP and 1 Listener IP on the remote site123.
* 2 IPs in the local site and 1 on the remote site for the database server nodes123.
This configuration ensures that each node in the cluster has a unique IP address, and each cluster and listener also has a unique IP address. This is necessary for the proper functioning of the cluster and to ensure that all nodes can communicate with each other and with clients123.

NO.112

An administrator needs to restore a source database from a point in time at 21:50, but the restore option is not available.
What could explain the matter?

Point in time must be within the most recent range.

Selected Restore time is not available.

Change to snapshot option.

Logs to Backup must be run first.

The provided exhibit shows the NDB Time Machine restore interface for October 31, 2024, with a Point-in- Time (PIT) restore option selected at 21:50. However, the restore option is unavailable, as indicated by the question. The exhibit includes a warning: “Logs to Backup: The database may contain additional logs. Backup any remaining logs before restore or they will be lost.” This suggests that PIT restore requires continuous log retention, and if logs since the last snapshot (at 01:10:00) are not backed up, the restore to 21:50 cannot proceed. Running the “Logs to Backup” operation ensures all transaction logs are captured, enabling PIT restore by allowing NDB to replay logs to the desired point.
* Option A (Point in time must be within the most recent range) is incorrect because the selected 21:
50 is within the log retention period shown (up to the current time), but logs need to be backed up.
* Option B (Selected Restore time is not available) is incorrect because 21:50 is a valid time within the log range, but log backup is the issue.
* Option C (Change to snapshot option) is incorrect because switching to a snapshot limits the restore to the snapshot time (01:10:00), not 21:50.
* Option D (Logs to Backup must be run first) is correct as the warning indicates that backing up remaining logs is necessary for PIT restore.
After running the backup, the administrator can proceed with the PIT restore.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Point- in-Time Restore Requirements
* Nutanix Support & Insights, Knowledge Base Article: “Troubleshooting PIT Restore Issues in NDB”
* Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

NO.113 An administrator needs to replace the default Nutanix self-signed certificates in Era.
Which SSL Certificate file format is supported?

PKCS#7

DER encoded binary X.509

Base-64 encoded X 509

PKCS#12

According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era supports x509 certificates in Base-64 encoded PEM format1. This format is used when an administrator needs to replace the default Nutanix self-signed certificates in Era1.

NO.114 An administrator has been tasked with cloning a production HR database but needs to anonymize the database during the cloning process.
Which command should the administrator execute using the NDB CLI to anonymize the database?

clone snapshot id= < clone_id > snapshot_name= < snapshot_name > sanitised=true delete_sanitised_snapshot_in_days= < no_of_days >

clone snapshot id= < clone_id > snapshot_name= < snapshot_name > sanitised=no delete_sanitised_snapshot_in_days= < no_of_days >

clone snapshot id= < clone_id > snapshot_name= < snapshot_name > sanitised=yes delete_sanitised_snapshot_in_days= < no_of_days >

clone snapshot id= < clone_id > snapshot_name= < snapshot_name > sanitised=false delete_sanitised_snapshot_in_days= < no_of_days >

NDB performs anonymization through a sanitized snapshot workflow. In the CLI syntax, sanitised is a Boolean flag; it must be set to true to request the creation of a sanitized snapshot. The delete_sanitised_snapshot_in_days parameter defines how long NDB retains that sanitized artifact before deleting it, while id identifies the clone and snapshot_name supplies the sanitized snapshot name. Values such as yes and no are not the documented Boolean forms for this parameter, and setting the flag to false would disable the sanitation request. Option A is therefore the valid command form. This method keeps the masking or anonymization operation inside the managed NDB lifecycle and allows retention to be controlled explicitly. Nutanix documents these parameters in its sanitized snapshot creation procedure.

NO.115 How does NDB send notifications when alerts are generated?

SNMP

APIs

Pulse

NDB sends notifications when alerts are generated via email. The email notifications can be configured to send to one or more recipients, and can be customized to include the alert severity, category, description, and resolution steps. The email notifications help to inform the database administrator and other stakeholders about the status and issues of the NDB-managed databases and operations.
NDB does not send notifications via SNMP, APIs, or Pulse. SNMP is a protocol for collecting and organizing information about managed devices on a network. APIs are interfaces for communicating and exchanging data between different applications or systems. Pulse is a feature of the Nutanix cluster that collects and sends diagnostic and usage data to Nutanix for analysis and support.
References:
* 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.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.2: Nutanix Era Alerts and Notifications, slides 5-7.

NO.116 Which two methods can be used to upgrade Era? (Choose two.)

Nutanix LCM

Offline Upgrade

Rolling Upgrade

One-click U pgrade

Nutanix Era can be upgraded using the Offline Upgrade and One-click Upgrade methods. The Offline Upgrade method involves manually downloading the software update and applying it to the Era instance. The One-click Upgrade method allows you to upgrade Era directly from the Era management console with a single click, provided that the Era instance has internet connectivity and can reach the Nutanix software update portal1.

NO.117 An administrator is managing a high availability (HA) NDB environment and has been tasked to configure custom SSL certificates. Which server instances must be updated?

All API server VMs

All HA Proxy VMs

The API and Repository VMs running on the primary cluster

The primary API, Repository and HA Proxy servers

In a high availability (HA) Nutanix Database Service (NDB) environment, custom SSL certificates are used to secure communication between clients (e.g., NDB GUI, API calls) and the NDB control plane. The HA Proxy VMs serve as the entry point for all external traffic, load balancing requests across the NDB API server VMs and providing secure SSL termination. When configuring custom SSL certificates, they must be updated on all HA Proxy VMs to ensure consistent and secure communication across the HA environment. Updating only a subset of servers or other components (like API or Repository VMs) would lead to inconsistencies or SSL handshake failures.
* Option A (All API server VMs) is incorrect because the API servers do not directly handle external SSL termination; this is managed by the HA Proxy layer.
* Option B (All HA Proxy VMs) is correct as these VMs are responsible for SSL termination and load balancing in an HA setup, requiring the custom certificates to be applied uniformly.
* Option C (The API and Repository VMs running on the primary cluster) is incorrect because Repository VMs do not handle client-facing traffic, and the API servers rely on HA Proxy for SSL handling.
* Option D (The primary API, Repository, and HA Proxy servers) is incorrect because it implies a single “primary” server focus, whereas in an HA setup, all HA Proxy VMs (not just a primary one) must be updated.
This aligns with NDB’s HA architecture, where HA Proxy VMs are the critical components for SSL certificate management.
References
* Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section:
Configuring High Availability and SSL Certificates
* Nutanix Support & Insights, Knowledge Base Article: “Configuring Custom SSL Certificates in NDB HA Environments”
* Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

Loading …

Guaranteed Success with Valid Nutanix NCP-DB Dumps: https://www.latestcram.com/NCP-DB-exam-cram-questions.html

Related Certifications

CInP (1)

Free Cram & Latest Exams Dumps

[Q99-Q117] Latest Nutanix NCP-DB First Attempt, Exam real Dumps Updated [Oct-2026]

leave a comment Cancel reply

Related Certifications

Recent Posts

Archives

Categories