NCP-DB Exam Dumps - Nutanix Certified Professional (NCP) Questions and Answers

NDB requires Prism Element credentials when a Nutanix cluster is registered. These credentials authorize NDB to communicate with the cluster and perform the infrastructure operations required for database lifecycle management. Depending on the workflow, those operations can include discovering resources, creating database server VMs, attaching or mapping storage, taking snapshots, and managing networking-related configuration. Active Directory credentials may be required for a Windows domain or database-specific authentication workflow, but they are not the fundamental credentials used to register the Nutanix cluster. Similarly, a syslog server identity and Nutanix Objects store information are not required for basic cluster registration. Nutanix’s official NDB cluster-registration documentation requires the cluster address and appropriate Prism Element administrator username and password so that NDB can access and manage the target cluster.

NDB provisions MongoDB by using standardized profiles that define the database software, network, compute, and database parameters. For MongoDB, Oracle, and SQL Server, Nutanix requires a Software Profile before a new database can be provisioned. The profile supplies the validated MongoDB binaries and configuration baseline that NDB uses to construct the database server VM and install the database engine. Database Parameter Profiles can refine runtime settings, but they do not replace the required software source. A Time Machine policy becomes relevant after provisioning when protection is configured, while database patches are incorporated through Software Profile versions rather than uploaded as the first provisioning step. Therefore, creating the Software Profile is the required first task. Nutanix NDB Profiles documentation

When consolidating Microsoft SQL Server instances on database server VMs managed by NDB using a medium compute profile, concerns about DB storage capacity can arise due to increased demand. In NDB, the appropriate task to address this is to "Update the Database Server VMs," which allows the administrator to adjust resource allocations, including storage capacity, for the VMs hosting the databases. This task can be performed within the NDB interface to expand disk space or reconfigure storage settings without altering the compute profile or requiring external tools.

Option A (Update the Database server VMs) is correct as it provides a direct method in NDB to modify VM resources, including storage.

Option B (Expand vDisk in Prism Element) is incorrect because NDB manages database VMs holistically, and storage expansion should be handled through NDB’s Update task rather than Prism Element directly.

Option C (Update the compute profile) is incorrect because compute profiles define CPU and memory, not storage capacity.

Option D (Scale the source database) is incorrect as scaling typically refers to database-level adjustments (e.g., adding nodes), not VM storage expansion.

This approach ensures seamless integration with NDB’s management framework.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Updating Database Server VMs

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Servers

NDB diagnostic collection gathers relevant logs from the NDB control plane and the database server VMs participating in the failed operation. For a Linux database server, the NDB agent collects applicable operating-system information, database-engine logs, work-driver output, and operation-specific diagnostic data. These files are packaged into a downloadable compressed bundle associated with the failed operation, allowing administrators or Nutanix Support to examine the complete execution context. NDB does not copy the active database data directory, create a runtime memory dump, or use a hypervisor snapshot of the log directory. Time Machine protects database data through snapshots and transaction logs; it is not the mechanism used to assemble support bundles. The official Nutanix instructions for viewing operation logs and downloading diagnostic bundles describe the collected and compressed diagnostic information.

MySQL HA uses MySQL Router as the application-facing routing layer. When NDB provisions an HA instance, the Create MySQL Router option can be enabled so clients connect through router VMs instead of targeting individual database nodes. The router uses cluster topology information to direct traffic to the appropriate active member and maintain connectivity when failover changes the primary. HAProxy is the component NDB commonly uses for PostgreSQL HA and for the NDB control plane; it is not the native routing choice for a MySQL InnoDB HA deployment. An external load balancer can be used in a custom design, but it is not the requested NDB-managed option. A multi-host connection string shifts failover handling to the application rather than enabling automated routing in NDB. Nutanix exposes this setting in the MySQL HA provisioning workflow.

 An Infrastructure Administrator is a role in NDB that has the permission to manage network and storage resources, such as VLANs, IP Pools, and Storage Containers. This role is suitable for the engineer who needs to add new VLANs or IP Pools in NDB. The other roles have either more or less privileges than required for this task. A Database Administrator can manage databases and database server VMs, but not network and storage resources. A Super Administrator can manage all aspects of NDB, but this is more than the least-privilege access needed. A Database Infrastructure Administrator can manage both databases and network and storage resources, but this is also more than the least-privilege access needed.

 Nutanix Support & Insights, section “NDB Roles and Permissions”

To release PostgreSQL HA instances using a dedicated subnet in Nutanix Database Service (NDB), the administrator must create a network profile that defines the subnet and its associated VLAN. Before creating this network profile, it is mandatory to add a VLAN to the NDB Networks configuration. This VLAN ensures that the dedicated subnet is recognized and manageable within NDB, allowing the HA instances to be provisioned with isolated network connectivity. The VLAN must be configured in the NDB Networks page to be available for selection during network profile creation.

Option A (The subnet in Prism Element must be IPAM configured) is incorrect because IP Address Management (IPAM) configuration in Prism Element is optional and not a mandatory prerequisite for creating a network profile in NDB.

Option B (The DB VMs must be registered first) is incorrect because VM registration is a subsequent step, not a prerequisite for network profile creation.

Option C (A VLAN must be added to NDB networks) is correct as it is a required step to define the network infrastructure before creating the profile.

Option D (Configure Network Segmentation) is incorrect because network segmentation is an advanced feature and not mandatory for basic network profile setup.

This ensures the dedicated subnet is properly integrated into NDB for HA provisioning.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring Network Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 3: Configure an NDB Environment

NDB allows creating and refreshing clones to a point in time using two primary methods:

B. Snapshots: NDB uses storage snapshots (e.g., via Nutanix Volumes or AHV) to capture the database state at a specific point. These snapshots can be used to create or refresh clones, providing a consistent recovery point.

D. Transaction logs: Transaction logs (e.g., PostgreSQL WAL, SQL Server logs) enable point-in-time recovery (PITR) by applying logs to a snapshot, allowing clones to be refreshed to a precise moment.

Other options are not supported for this purpose:

A. Full backups: Full backups are used for complete restores but are not optimized for frequent clone refreshes.

C. VM snapshots: VM-level snapshots (e.g., AHV snapshots) are not managed by NDB for database cloning, as they lack database consistency.

Thus, the verified answers are B and D, reflecting NDB’s clone refresh capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Time Machines and Clones.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Clones (applicable to v7.5).

Nutanix NDB Administration Guide: "Clone Creation and Refresh" section.

NDB supports communication between a VPC containing the NDB control plane and a different VPC containing database server VMs. For this east-west communication, NDB requires No-NAT routing so that the original IP addresses remain visible and directly routable between the two VPCs. Required ports, DNS resolution, and bidirectional reachability must also be configured between NDB and the managed database server VMs. NAT-based routing is not supported for this communication path because address translation can interfere with NDB’s management connections and database lifecycle workflows. The database server VMs use Flow overlay networking rather than being restricted to an underlay network, and the control plane and database workloads do not have to reside in the same VPC. Nutanix confirms this requirement in its official NDB with Flow Virtual Networking documentation.

The exhibit shows an error during the provisioning of NDB from the Prism Central Marketplace, with a failure reason stating "IP not found" in the "EraService - Substrate Create" step. This indicates that the provisioning process could not assign or detect an IP address for the NDB instance, likely due to an unconfigured or missing IP address during deployment. To prevent this issue, the administrator should configure an IP address when deploying the application. This involves specifying a static IP or ensuring IP Address Management (IPAM) is properly set up to allocate an IP during the Prism Central Marketplace deployment wizard.

Other options are less directly relevant:

B. Import the proper image in the Prism Central: This ensures the correct NDB image is available but does not address the IP assignment issue.

C. Provide a subnet with IP Address Management: While useful, this is a broader configuration step and not the specific action needed during deployment.

D. Register NDB using the correct IP address: Registration occurs after deployment and does not prevent the initial IP assignment failure.

Thus, the verified answer is A, as configuring the IP address during deployment directly addresses the "IP not found" error.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.2: Deploying NDB from Prism Central.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Deploy NDB (applicable to v7.5).

Nutanix NDB Installation Guide: "Deploying NDB via Prism Central Marketplace" section, emphasizing IP configuration.