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

To reset the NDB GUI password in Nutanix Database Service (NDB), an administrator must access the system through an SSH session and use the appropriate command-line interface (CLI) tools provided by NDB. The correct process involves entering the era-server CLI, which is the specific CLI environment for managing NDB-related configurations, including security settings like password resets. Once in the era-server CLI, the administrator executes the security password reset command to initiate the password reset process for the NDB GUI. This method ensures that the reset is performed within the NDB-managed environment securely and aligns with Nutanix’s recommended administrative procedures.

Option A is correct because it specifies the era-server CLI and the exact command security password reset, which are consistent with NDB’s administrative tools for managing GUI access credentials.

Option B (sudo passwd era) is incorrect because era is not a system user account in the context of NDB’s Linux-based control plane; this command pertains to standard Linux user management, not NDB-specific GUI password resets.

Option C (sudo passwd admin) is also incorrect as admin refers to a generic user that may not correspond to the NDB GUI account, and this approach bypasses NDB’s internal security mechanisms.

Option D is incorrect due to a typo (era CLI instead of era-server CLI), which renders it imprecise despite the intent being similar to Option A.

This process assumes the administrator has SSH access to the NDB control plane VM and the necessary privileges to execute these commands.

References

Nutanix Database Service (NDB) User Guide, Section: Administering an NDB Environment, Subsection: Managing Access Controls and Password Resets

Nutanix Support & Insights, Knowledge Base Article: "Resetting NDB GUI Password via CLI"

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

When a quality assurance (QA) team notices a significant change between a cloned database currently in use and one used a week ago, and they have an SQL script to verify differences, the NDB administrator needs to provide a clone reflecting the database state from a week ago. The task "Clone database selecting Point in Time data" allows the administrator to select a specific point-in-time snapshot (e.g., from a week ago) using the Time Machine feature. This creates a new clone with the exact data state at that time, enabling the QA team to compare it with the current clone.

Option A (Replicate a selected snapshot) is incorrect because replication is for HA, not creating a usable clone for QA.

Option B (Create a clone database from a snapshot) is incorrect because it does not specify point-in-time selection, limiting flexibility to the latest snapshot.

Option C (Clone database selecting Point in Time data) is correct as it allows precise selection of the week-old data state.

Option D (Perform a Log Catch Up operation) is incorrect because Log Catch Up applies recent logs, not reverting to a past state.

This approach meets the QA team’s need for historical data comparison.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Cloning with Point-in-Time Data

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 5: Protect Databases Using Time Machine

According to the Nutanix Database Automation (NCP-DB) course, the Pre-Post Commands section allows the administrator to specify custom scripts that can be executed before or after the clone operation1. The masking script can be created on any of the VMs that have access to the source database, such as the source DB VM, the Dev VM, or the SW Profile VM2. The script should contain the commands to mask the sensitive data in the Finance database, such as replacing the real values with dummy values or encrypting the data2. The administrator can then create the clone from the Time Machine and define the post-clone option with the full path and name of the masking script1. This will ensure that the script is executed after the clone is created, and the data is masked before it is available for the development team1. The other options are not correct, as they either use the wrong field (pre-clone instead of post-clone), or do not specify where to create or store the masking script. References:

1: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 5

2: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 7

 Nutanix Database Service (NDB) supports automated minor version upgrades for PostgreSQL1. Before applying the patch, the administrator should create a new software profile2. This is because the software profile contains the database engine binaries and other software required to run the database engine2. Therefore, to apply a minor version upgrade, a new software profile with the updated binaries needs to be created2. Once the new software profile is created, it can be used to patch the PostgreSQL database2.

For an existing PostgreSQL database server managed by NDB, additional databases are added by updating the applicable database server parameters through the NDB graphical interface. The Database Parameters Profile represents PostgreSQL instance-level configuration and allows NDB to apply the supported database definition and configuration consistently. Creating additional Time Machines would protect separate database entities but would not create the databases themselves. A Software Profile contains the operating-system and PostgreSQL binaries used for provisioning database server VMs; replacing it is unnecessary for adding databases to an existing instance. A post-provisioning script is also not the standard managed workflow because it would bypass the profile-based configuration maintained by NDB. Therefore, option B is correct: the administrator should modify the Database Parameters Profile for the existing PostgreSQL server. Nutanix PostgreSQL Database Parameters Profile documentation

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.

When an administrator cannot proceed with the first step of the wizard to provision a new Oracle single instance database in NDB, the most likely reason is that a software profile for Oracle is missing. NDB requires a software profile (which defines the database version, patches, and configuration) to provision a database instance. Without a profile created from a reference VM or uploaded manually, the wizard cannot proceed, as it relies on this profile to configure the instance correctly.

Option A (Time Machine is not configured) is incorrect because Time Machine is optional for backups and not required for initial provisioning.

Option B (Software profile is missing) is correct as it is a mandatory prerequisite for provisioning any database instance.

Option C (No remote clusters are configured) is incorrect because remote clusters are relevant for multi-cluster setups, not single instance provisioning.

Option D (A snapshot must be taken on the original DB) is incorrect because snapshots are for protection, not a prerequisite for provisioning.

The administrator must create or import a software profile to resolve this issue.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Provisioning Databases

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Provisioning Failures in NDB"

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

The recovery plans policy defines the Time Machine data availability across multiple registered clusters in NDB. The recovery plans policy allows the database administrator to specify the source and target clusters, the frequency and retention of the cross-cluster snapshots, and the network and compute profiles for the recovery operations. The recovery plans policy helps to ensure the disaster recovery and business continuity of the NDB-managed databases in case of a cluster failure or outage.

The data access management policy defines the access permissions and roles for the NDB users and groups. The data access management policy allows the database administrator to grant or revoke access to the NDB instance, the database server VMs, the databases, and the database operations. The data access management policy helps to ensure the security and compliance of the NDB-managed databases and users.

The data protection policy defines the backup and restore settings for the NDB-managed databases. The data protection policy allows the database administrator to specify the frequency, retention, and compression of the database snapshots, and the backup location and encryption for the database backups. The data protection policy helps to ensure the backup and recovery of the NDB-managed databases within the same cluster.

The service level agreements policy defines the performance and availability metrics for the NDB-managed databases. The service level agreements policy allows the database administrator to monitor and enforce the database uptime, latency, throughput, and IOPS. The service level agreements policy helps to ensure the quality of service and performance of the NDB-managed databases.

Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slide 9.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 8, 12, 16, 20.

Nutanix Database Management & Automation Training Course, Module 6: Nutanix Era Disaster Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 5-7.

The NDB control-plane appliance is deployed as a VM on a Nutanix AHV cluster, so an operational Nutanix cluster managed through Prism Element must exist first. The deployment workflow connects to Prism Element, selects the required cluster networking and storage resources, and creates the NDB VM. Nutanix’s installation prerequisites also require suitable Prism Element credentials, such as an account with the documented cluster-level administrative access. Prism Central can support additional services and integrations, but it is not a universal prerequisite for the initial NDB appliance deployment. Nutanix Objects is optional and is used for capabilities such as database log-backup storage. Flow Virtual Networking is likewise not required for the base installation. Therefore, option B identifies the component that must be available before deployment. Nutanix NDB installation documentation

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.