Pass the Nutanix Nutanix Certified Professional (NCP) NCP-DB Questions and answers with CertsForce

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.

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) v7.5Blueprint, Section 5: Protect Databases Using Time Machine

In the Nutanix Era management interface, an administrator should perform an upgrade under the Administration > Maintenance section1. As part of the upgrade process, the Era server is upgraded first, followed by all the Era cluster agents and database server agents in parallel1. The Dashboard displays the current version and an option to upgrade the Era server to a latest version when a new version is available for upgrade1. This ensures that the Nutanix Era environment is always up-to-date with the latest features and security updates1.

Every Nutanix cluster that will host NDB-provisioned databases must first be registered with the NDB control plane. Registration provides NDB with the Prism Element endpoint, credentials, storage-container information, and network context required to create and manage database server VMs on that target. A single NDB deployment can manage multiple registered Nutanix clusters; deploying another NDB appliance for every cluster is unnecessary. Database HA on the original cluster does not make an additional cluster available, and a protection domain is a data-protection construct rather than the NDB onboarding mechanism. Nutanix’s cluster-registration documentation explicitly requires registering the target cluster before databases can be provisioned there. Therefore, option C is the required preparatory action. Nutanix cluster-registration documentation

When registering a Nutanix cluster with NDB, a manual storage mapping between the remote container and the NDB provisioning container is required if the NDB Server container and NDB Provisioning container are separate. This separation occurs when the storage containers used by the NDB server (for its own operations) and the provisioning container (for database VMs) are distinct, either due to multi-cluster setups or custom configurations. Manual mapping ensures NDB can correctly allocate storage resources and manage database provisioning across these containers.

Other conditions do not necessitate manual mapping:

B. Disaster Recovery Network Segmentation is enabled on the cluster: This affects networking, not storage mapping.

C. Nutanix Database Service High Availability is enabled on the cluster: HA configurations handle replication, not container mapping.

D. DB VMs are stored in the NDB Server or NDB Provisioning container: This is a typical setup and does not require manual mapping unless containers differ.

Thus, the verified answer is A, addressing storage container separation.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster.

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

Nutanix NDB Administration Guide: "Storage Container Mapping" section.

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.

To enable multi-cluster setup for NDB High Availability (HA), the administrator must configure the NDB Agent with a Network Profile. A Network Profile defines the networking settings (e.g., VLANs, IP ranges) that the NDB Agent uses to communicate across clusters. This is critical for multi-cluster HA, as it ensures consistent network configuration for replication, failover, and data synchronization between clusters. The Network Profile must be properly configured to handle inter-cluster traffic and latency requirements (e.g., < 25ms RTT).

Other options are irrelevant:

A. Name Prefix: Used for naming conventions, not network configuration.

C. Static VLAN: A component of a Network Profile, but not the full configuration needed.

D. Compute Profile: Defines VM resources (CPU, memory), not networking for HA.

Thus, the verified answer is B, aligning with multi-cluster HA networking needs.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.2: Configuring Multi-Cluster HA.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v7.5).

Nutanix NDB Administration Guide: "Configuring Network Profiles for Multi-Cluster HA" section.

The Era One-Click Provisioning service in Nutanix Database Automation (NCP-DB) simplifies and automates database administration. It brings one-click simplicity to database provisioning and life-cycle management. This service enables database administrators to provision, clone, and refresh the database clones to any point in time1. Specifically, it enables the creation of space-efficient clones and zero-byte database clones1. This is part of Era’s copy data management service, which includes components like Time Machine, one-click cloning and refresh, and one-click backup21.

The correct answer is B because the Time Machine feature of NDB collects logs and snapshots from databases and stores them in a distributed file system. The Time Machine enables the administrator to protect, clone, and restore databases using the SLA policies and the NDB UI or API. The Time Machine also manages the replication of database snapshots in an NDB multicluster environment. The other options are not correct because they describe different features or functions of NDB. Option A is not correct because Database Restore is an operation that uses the Time Machine to restore a source database or a clone to a previous point in time. Option C is not correct because SLA is a policy that defines the frequency and retention of database snapshots and logs. Option D is not correct because One-click Patching is a feature that allows the administrator to test, publish, and apply database patches using the NDB UI or API. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Support & Insights

NDB creates database clones by using Nutanix space-efficient snapshots instead of copying every source database block into a new 2 TB allocation. The initial clone primarily consists of metadata and references to the source snapshot’s existing blocks. Consequently, it consumes near-zero additional storage when it is first created. The clone becomes an independent database environment, and new physical capacity is consumed only when blocks are changed or newly written. Because the question specifies that the clone remains read-only, there should be no meaningful database write growth after creation. Its storage consumption is therefore not equal to the source size and is not determined by fixed compression ratios such as 50 or 20 percent. Nutanix’s official Clone Management documentation states that NDB clones are highly space-efficient and initially consume near-zero additional bytes.