Selected NCP-DB Nutanix Certified Professional (NCP) Questions Answers

During MySQL HA provisioning, NDB creates the database or schema identified by the Database Name supplied in the provisioning workflow. In MySQL terminology, CREATE DATABASE and CREATE SCHEMA are equivalent, so using the intended default schema as the database name gives developers the required schema as part of the managed deployment. A post-create script could create additional objects, but it is unnecessary for the initial default schema and adds avoidable custom automation. The provisioning workflow does not require uploading a SQL file, and a software profile packages database software and operating-system binaries rather than application schemas. Therefore, the default schema should be defined as the database name. This keeps schema creation within NDB’s declarative provisioning workflow and makes the resulting database manageable as part of the MySQL HA instance. Nutanix uses the Database Name field for this purpose.

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) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v7.5).

Nutanix NDB Installation Guide: "Network Ports and Protocols" section, specifying port 2009.

 According to the Nutanix Database Automation (NCP-DB) learning documents, when provisioning a new database, there are two options available for the target12:

Provision database to an existing registered: This option allows you to provision a database to an existing registered database server. This is useful when you want to add a database to a server that is already being managed by Nutanix Era1.

Provision databases to a new container: This option allows you to provision a database to a new container. This is useful when you want to create a new isolated environment for your database1.

Nutanix Database Service (NDB) supports high availability (HA) instances for certain relational database management systems (RDBMS). Among the listed options, NDB natively supports Oracle and PostgreSQL for HA configurations, enabling features like replication and failover. These databases are well-integrated with NDB’s Time Machine and HA frameworks.

Option A (MongoDB) is incorrect because MongoDB is a NoSQL database, not an RDBMS, and is not supported for HA instances in NDB.

Option B (MariaDB) is incorrect because, while MariaDB is an RDBMS, it is not currently supported for HA instances in NDB v7.5.

Option C (Oracle) is correct as NDB supports Oracle in HA mode with features like Data Guard integration.

Option D (PostgreSQL) is correct as NDB supports PostgreSQL HA with streaming replication.

Note: The typo "PostgreSGL" in the question is assumed to mean "PostgreSQL" based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Supported RDBMS for HA

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