Nutanix NCP-DB - Nutanix Certified Professional - Database Automation (NCP-DB v7.5)

When using the "Patch OS now" feature in NDB to apply updates to a Red Hat-based operating system, the administrator can limit updates to security patches only by leveraging the Advanced Options. Under the "Custom commands" section of the operating system patching command window, entering yum update --security instructs the package manager to install only security-related updates. This ensures the system remains secure without applying all available updates, which could introduce instability.

Other options are incorrect or incomplete:

A. Point the database VM to a custom patch repository and enter yum update --security command: This requires manual intervention outside NDB’s patching framework.

B. Check Advanced Options and under Pre-post commands, enter yum update security in the pre-operating system patching command window: Pre-post commands are for pre/post actions, not the main patching process, and the syntax lacks the --security flag.

C. Point the database VM to a custom patch repository before using the Patch OS now feature: This sets up a repository but doesn’t specify security-only updates within NDB’s interface.

Thus, the verified answer is D, aligning with NDB’s patching customization.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.3: Creating Maintenance Plans.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v7.5).

Nutanix NDB Administration Guide: "Patch OS Now with Custom Commands" section.

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 log frequency in the Era IJI for log catchup operation can be configured to as low as 5 minutes. This allows the system to capture changes to the database at a high frequency, enabling more precise point-in-time recovery options. However, it’s important to note that a higher frequency of log catchup operations can lead to increased system load. Therefore, the optimal frequency may vary depending on the specific requirements and capabilities of your system12. Please refer to the Nutanix Database Automation (NCP-DB) Learning documents for more detailed information.

Nutanix Database Service provides REST APIs for automating database lifecycle operations, including provisioning, cloning, registration, patching, refreshing, and deprovisioning. A CI/CD pipeline can call these APIs programmatically to request a database, monitor the resulting operation, and retrieve its status without requiring an administrator to use the NDB console. Maintenance Windows schedule maintenance activities, while Time Machine provides snapshot and transaction-log-based data protection. A Network Profile supplies networking configuration but does not provide an automation interface. Therefore, the REST API is the appropriate capability for integrating database provisioning with tools such as Jenkins, GitHub Actions, GitLab CI, or other orchestration platforms. The official NDB API reference documents the endpoints and request structures available for this programmatic integration.

NDB profiles are scoped by database engine and deployment type. A Network Profile identifies the VLAN and related network settings that NDB can use when creating a database server VM. Merely registering the Nutanix cluster does not create a usable engine-specific Network Profile. If the provisioning wizard for a particular engine displays no networks, the most likely missing object is the Network Profile created under that database engine. DHCP or static addressing is a configuration choice inside the profile; neither is universally required, so the absence of one addressing mode does not explain an empty list by itself. A database HA component profile would be relevant only to the corresponding HA topology, not ordinary engine provisioning. Therefore, the administrator must create or make available a Network Profile for the specific database engine. Nutanix documents this engine-specific workflow under NDB Profiles.

The error message in the exhibit indicates that the operation failed during the “Create and Register Database Server VMs” step because “Provisioning of all the observers simultaneously took more than two hours.” This type of error is associated with MySQL, as it involves observers which are a part of MySQL Group Replication, used for ensuring high availability1. The other options are not related to the error message, as they do not use observers or Group Replication for clustering. References:

1: Nutanix Database Automation (NCP-DB) course, Module 5: Database High Availability, Lesson 5.2: MySQL Group Replication, slide 7

To install NDB on a Nutanix AHV cluster, you need to download the QCOW2 image file of NDB from the Nutanix Support Portal and upload it to Prism Element. This image file contains the NDB software and the CentOS operating system. After uploading the image, you need to create a VM from the image and configure the network settings. Then, you need to register the NDB VM with Prism Central and enable the NDB service in the settings menu. References: Nutanix Support & Insights, Professional Services: NDB Database Cloning

The Global Service Level Agreement (SLA) feature of Era allows an administrator to create Time Machine policies in a Multi-Cluster configuration1. This feature provides a unified way to manage and enforce backup and replication policies across multiple clusters, ensuring consistent data protection and recovery across the entire environment1.

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.

Nutanix Era allows custom metadata to be assigned to entities (clones, time machines, databases, and database servers) by using Tags. Tags are a component of Nutanix Era that allows users to assign custom metadata to various entities, enhancing the ability to organize, search, and manage these entities within the Era platform1.