NCP-DB Dumps With Exact Questions and Answers

A stretched VLAN is a virtual network that spans across multiple Nutanix clusters and allows the communication between VMs on different clusters using the same subnet. A stretched VLAN can be used to provide high availability and load balancing for NDB components, such as HAProxy VMs, that require a virtual IP address (VIP) to be accessible from any cluster. To add a stretched VLAN across two clusters in NDB, the administrator needs to meet two prerequisites: the VLAN must be static and both clusters must be registered in NDB. A static VLAN is a VLAN that is manually created and configured by the administrator, as opposed to an IPAM VLAN that is automatically created and managed by NDB. A static VLAN can be added to a stretched VLAN in NDB, while an IPAM VLAN cannot. Both clusters must be registered in NDB before adding a stretched VLAN, as NDB needs to have the information and access to the clusters and their networks. The administrator can register the clusters in NDB using the Prism Element details, agent network configuration, and storage container information. The other option, Nutanix Cluster Management, is not a prerequisite for adding a stretched VLAN in NDB. Nutanix Cluster Management is a feature that allows the administrator to manage multiple Nutanix clusters from a single NDB UI, such as creating or deleting clusters, adding or removing nodes, or performing cluster operations. Nutanix Cluster Management is not required for adding a stretched VLAN, as the VLANs are created and configured in Prism Element, not in NDB.  References :

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

Nutanix Database Management & Automation (NDMA) Course , Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.3: Configuring NDB High Availability, Topic: NDB HA Architecture and Components

Nutanix Database Service High Availability Deployment Overview , Section: HAProxy VMs and Stretched VLANs

[Configuring a Virtual NIC to Operate in Access or Trunk Mode - Nutanix], Section: Creating a vNIC in Access or Trunk Mode

In a multi-cluster NDB instance with HA enabled, the NDB architecture includes multiple API server VMs to ensure availability. If more than one API server VM is down after a failure, the administrator should ensure at least one API server VM is online . NDB’s HA design tolerates multiple API server failures as long as one remains operational, and the remaining VMs will recover automatically through the HA failover mechanism. This leverages Nutanix’s distributed architecture and self-healing capabilities to restore full functionality without manual intervention beyond ensuring one VM is running.

Other options are incorrect:

A. Restart all database server VMs as NDB HA only tolerates single API server failure : NDB HA can handle multiple API server failures, and restarting database VMs is unnecessary.

B. Manually distribute connections across remaining clusters : This is not required, as HA manages connections automatically.

C. Call Nutanix support to reset all API server connections : Support is not needed for this scenario; recovery is automated.

Thus, the verified answer is D , reflecting NDB’s HA resilience.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.3: Recovering from Failures.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.4: Recover NDB HA (applicable to v6.10).

Nutanix NDB Administration Guide: " High Availability Recovery Procedures " section.

When an administrator wants to manage an additional database on an existing database server VM in NDB, the first step is to identify if the database is already recognized by NDB. The " Unregistered Databases " field or section within the NDB interface lists databases that are present on a registered database server VM but have not yet been registered with NDB. This allows the administrator to discover and register the new database, enabling full management capabilities (e.g., provisioning, cloning, or patching). Once registered, the database will move to the " Registered Databases " section.

Option A (Unregistered Databases) is correct as it is the initial field to check for new, unmanaged databases on the VM.

Option B (Database Server VM) is incorrect because this refers to the VM itself, not the databases it hosts.

Option C (Registered Databases) is incorrect because this lists only databases already managed by NDB, not new ones.

Option D (Database Name in NDB) is incorrect as it is not a specific field but a general reference, lacking a defined location.

The administrator should use the Unregistered Databases section to proceed with registration.

References

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Registering Additional Databases

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