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

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.

To create an NDB Software Profile Version for PostgreSQL, it is required to have an installer package for the database software. This package forms the basis of the software profile, enabling the deployment and management of PostgreSQL instances.

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

If a database administrator is unable to provision a new MongoDB database using an existing software profile, the most likely cause is that the administrator lacks the proper permissions in Prism Element. NDB relies on Prism Element for cluster-level operations (e.g., storage and compute resource allocation). The database administrator needs appropriate Prism Element roles (e.g., Cluster Admin) to interact with the underlying infrastructure, even if the software profile is available in NDB. Without these permissions, the provisioning action will fail.

Other options are less likely:

A. A database clone operation is in progress: This might delay actions but wouldn’t prevent provisioning unless it locks resources indefinitely.

B. The software profile was created by another user: NDB allows profile reuse across users if published, so this is not a barrier.

D. The software profile is undergoing a patching operation: Patching affects the profile’s state but doesn’t block provisioning unless explicitly locked.

Thus, the verified answer is C, highlighting the need for Prism Element permissions.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Provisioning Databases.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Troubleshoot Provisioning Issues (applicable to v7.5).

Nutanix NDB Administration Guide: "Prerequisites for Database Provisioning" section, noting Prism Element roles.

This is because it allows the database to be refreshed at the exact time specified (9:30 PM) with the most recent data. The other options either perform the snapshot before the desired time or do not specify when the snapshot would occur. Please note that the exact answer might depend on the specific database system and its capabilities. Always refer to the database’s documentation for the most accurate information.

When an administrator is creating a Windows Domain profile in Era, the SQL Service Startup Account is an optional field that can be skipped and provided during the provisioning process. This account is used to start the SQL Server service when the server starts up. If this field is not provided during the creation of the Windows Domain profile, it can be provided later during the provisioning process1.

For a One-Click Upgrade of an NDB environment with internet access, the patch should be downloaded directly within the NDB interface. The "Administrator > Maintenance" section of NDB provides an option to connect to the Nutanix download repository (e.g., https://download.nutanix.com) and download the latest patch or upgrade bundle automatically. This streamlined process ensures compatibility and simplifies the upgrade workflow. The One-Click Upgrade feature then applies the downloaded patch to update NDB components efficiently.

Other options are incorrect:

A. Download the patch from the Nutanix Support Portal and upload via the NDB CLI: This is suitable for dark sites but unnecessary with internet access, as NDB can download directly.

C. Open Prism Central and deploy the current version of NDB from the Apps and Marketplace section: This is for initial deployment, not upgrading an existing NDB instance.

D. Open Prism Element and use LCM to update the software: Lifecycle Manager (LCM) is for Nutanix cluster updates, not NDB-specific upgrades.

Thus, the verified answer is B, leveraging NDB’s built-in maintenance capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Updating NDB with Internet Access.

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

Nutanix NDB Administration Guide: "One-Click Upgrade Process" section.

In an NDB HA (High Availability) setup, when planning an electrical maintenance window requiring the clusters hosting NDB to be powered off, the administrator must follow a controlled shutdown sequence to preserve data integrity and minimize disruption. After shutting down the load balancer server (HAProxy), the next step is to shut down the API standby node. In an NDB HA configuration, the API leader node handles active operations, while the standby node provides redundancy. Shutting down the standby node first ensures the leader remains operational, allowing ongoing management tasks to continue until the final shutdown of the leader node.

Option A (In the sudo systemctl stop patroni command) is incorrect because Patroni is used for PostgreSQL HA, not NDB HA node management.

Option B (Shutdown the API standby node) is correct as it follows the recommended HA shutdown order, preserving active services.

Option C (Run the high-availability list command) is incorrect because this is a diagnostic command, not a shutdown step.

Option D (Shutdown the API leader node) is incorrect because the leader should be the last node shut down to maintain service availability.

This sequence ensures a graceful shutdown of the NDB HA environment.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Managing HA Shutdown Procedures

Nutanix Support & Insights, Knowledge Base Article: "Shutting Down NDB HA During Maintenance"

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

In Nutanix Database Service (NDB), when an administrator deprecates a software profile version, it is marked as obsolete and restricted from certain operations. Specifically, a deprecated software profile version can no longer be used for provisioning new database instances or VMs. This ensures that only current, supported versions are utilized for new deployments, maintaining consistency and security. Existing database servers using the deprecated profile can continue to operate and may still be patched (if updates are compatible), but the profile itself is excluded from future provisioning tasks.

Option A is correct because deprecation explicitly prevents the profile version from being selected for new provisioning, aligning with NDB’s lifecycle management.

Option B (It can be used in provisioning) is incorrect as this contradicts the purpose of deprecation.

Option C (Any database server using that profile will be updated to the latest software profile) is incorrect because deprecation does not automatically update existing servers; it only affects new provisioning.

Option D (Any database server using that software profile can no longer be patched) is incorrect because patching existing servers is still possible if compatible updates exist, independent of the profile’s deprecated status.

Deprecation is a deliberate administrative action to phase out outdated profiles while preserving existing deployments.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Deprecating Software Profile Versions

Nutanix Support & Insights, Knowledge Base Article: "Software Profile Management in NDB"

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

 NDB supports two modes of log backup management for Microsoft SQL databases: NDB-managed and 3rd-party managed. In the NDB-managed mode, NDB takes full control of the log backups and stores them in the Cerebro log location. In the 3rd-party managed mode, NDB allows the use of external backup tools to backup the logs from the database log destination. However, NDB still needs to capture the logs for its own operations, such as point-in-time recovery, clone refresh, and log catch-up. Therefore, NDB will periodically scan the database log destination and copy the logs to the Cerebro log location. This process requires that the log catch-up begins before the logs get backed up by the 3rd-party tool, otherwise NDB will miss some logs and the operations will fail. If the 3rd-party tool grants exclusive access to the logs, then NDB will not be able to capture them at all, and the operations will not be supported. References:

Nutanix Database Management & Automation (NDMA) course, Module 5, Lesson 5.2 - Log Backup Management

Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Log Backup Management