Nutanix NCP-DB Exam With Confidence Using Practice Dumps

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.

NDB requires management and storage connectivity to a registered Nutanix cluster. TCP 9440 carries Prism REST API communication between NDB components and the Nutanix cluster. TCP 3205 and 3260 support iSCSI redirection/data and standard iSCSI control traffic used when NDB attaches Volume Group disks. Therefore, both option B and option D must be allowed through the segmented network. Port 443 is used for HTTPS communication in other NDB paths, but it is not the required Prism/CVM port represented by this question. Ports 1433 and 5432 are database listener ports for Microsoft SQL Server and PostgreSQL, respectively, rather than NDB-to-CVM infrastructure ports. The source answer “D” is incomplete; the verified answer is B and D. Nutanix port reference

================

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

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