Free Practice Questions for Nutanix NCP-DB Exam

For deploying Nutanix Database Service (NDB), the required file type to download from the Nutanix Portal is an OVA (Open Virtual Appliance) file. The OVA format is a standardized package that includes a pre-configured virtual machine image, including the NDB software, which can be imported into supported hypervisors (e.g., VMware ESXi or Nutanix AHV). This simplifies the deployment process by providing a ready-to-use VM template with all necessary components.

Option A (ZIP) is incorrect as ZIP files are generic archives, not deployment-specific formats for NDB.

Option B (QCOW2) is incorrect because QCOW2 is a disk image format primarily used with KVM/QEMU, not the standard for NDB deployment.

Option C (OVA) is correct as it is the official file type provided by Nutanix for NDB deployment.

Option D (TAR) is incorrect as TAR files are used for archiving, not as a deployment package for NDB.

Administrators should download the OVA from the Nutanix Portal and follow the deployment guide.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Deploying NDB, Section: Downloading and Deploying the OVA

Nutanix Support & Insights, Knowledge Base Article: "NDB Deployment Prerequisites"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 1: Deploy NDB

According to the Nutanix Database Automation (NCP-DB) learning documents, the Schedule feature of the Time Machine allows developers to automate the data refresh for their clones1. This feature eliminates the time-consuming, complex process of database clone/refresh, allowing admins to create database clones/refresh to any point in time in just a few minutes1. Please refer to the official Nutanix documentation and training materials for more detailed information2.

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.

To add multiple databases to an existing PostgreSQL instance managed by NDB, the administrator should use the NDB graphical user interface (GUI). The GUI provides a user-friendly way to modify the parameter profile associated with the PostgreSQL instance, allowing the addition of new databases by adjusting settings such as database names, sizes, or configurations. This process typically involves navigating to the "Databases" or "Instances" section, selecting the PostgreSQL instance, and editing the parameter profile to include additional databases.

Other options are less appropriate:

A. Modify parameter profile using ncli: The ncli (Nutanix Command Line Interface) is used for cluster-level management in Prism, not for NDB database configuration.

C. Modify parameter profile using post script: Post-scripts are used for custom actions post-provisioning, not for modifying parameter profiles to add databases.

D. Modify parameter profile using NDB CLI: While NDB has a CLI, the GUI is the recommended and supported method for such configuration changes, offering a guided workflow and validation.

Thus, the verified answer is B, leveraging the NDB GUI for ease and compliance with best practices.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.4: Modifying Database Configurations.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.3: Modify Parameter Profiles (applicable to v6.10).

Nutanix NDB Administration Guide: "Managing PostgreSQL Instances" section, detailing GUI-based modifications.

NDB can leverage snapshots and transaction logs to refresh a database clone to the latest state of the source database. Snapshots are point-in-time copies of the database that are stored on the Nutanix cluster. Transaction logs are records of the changes made to the database after the snapshot was taken. NDB can use either snapshots or transaction logs, or a combination of both, to refresh a database clone. Cerebro logs and templates are not used for refreshing database clones. Cerebro logs are used for log catch-up operations, which are different from refresh operations. Templates are used for provisioning new databases, not for refreshing existing ones. References:

Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.3 - Refreshing Clones

Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Clone Database Management

During an NDB upgrade, the upgrade process follows a specific order to maintain stability and HA. The Leader NDB API Server is upgraded first. This server coordinates API requests and ensures the control plane remains operational. Upgrading the leader first minimizes disruption, as subsequent components (e.g., other API servers, HAProxy) rely on its leadership role. Once the leader is upgraded, the remaining NDB HA control plane VMs (e.g., follower API servers, HAProxy) are updated in sequence.

Other options are incorrect:

A. NDB Server: Refers to the main NDB instance, not upgraded first.

C. Leader HAProxy: Upgraded after API servers to maintain load balancing.

D. NDB Agent VMs: Upgraded last, as they are client-side components.

Thus, the verified answer is B, reflecting the upgrade sequence.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "NDB Upgrade Process" section.

When an administrator wants to manage an additional database on an existing database server VM in NDB, the first step is to identify if the database is already recognized by NDB. The "Unregistered Databases" field or section within the NDB interface lists databases that are present on a registered database server VM but have not yet been registered with NDB. This allows the administrator to discover and register the new database, enabling full management capabilities (e.g., provisioning, cloning, or patching). Once registered, the database will move to the "Registered Databases" section.

Option A (Unregistered Databases) is correct as it is the initial field to check for new, unmanaged databases on the VM.

Option B (Database Server VM) is incorrect because this refers to the VM itself, not the databases it hosts.

Option C (Registered Databases) is incorrect because this lists only databases already managed by NDB, not new ones.

Option D (Database Name in NDB) is incorrect as it is not a specific field but a general reference, lacking a defined location.

The administrator should use the Unregistered Databases section to proceed with registration.

References

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Registering Additional Databases

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 2: Deploy and Configure an NDB Solution

To replicate database snapshots to remote Nutanix clusters, the administrator needs to add Data Access to each Nutanix cluster and assign a Data Availability Management (DAM) policy. Data Access is a feature of NDB that enables cross-cluster data mobility and protection. A DAM policy defines the replication frequency, retention period, and priority of the database snapshots across the clusters. By adding Data Access to each Nutanix cluster and assigning a DAM policy, the administrator can manage the Time Machine data availability across all registered Nutanix clusters in NDB.

References: Nutanix Support & Insights, section “NDB Data Access”

To deploy Microsoft SQL Servers in an Active Directory (AD) environment and select a specific service account to start up the database, the administrator must configure a Windows domain profile in NDB. A Windows domain profile defines the AD integration settings, including the service account credentials (e.g., username and password) that NDB uses to authenticate and manage the SQL Server instances. This configuration ensures the database starts and runs under the specified AD service account, aligning with enterprise security policies.

Option A (Compute profile) is incorrect because a compute profile defines VM resources (CPU, memory), not AD or service account settings.

Option B (Sysprep Windows image) is incorrect because Sysprep is for generalizing Windows images, not configuring AD service accounts.

Option C (Windows domain profile) is correct as it is the specific NDB feature for AD integration and service account management.

Option D (Database parameters) is incorrect because database parameters tune database settings, not AD authentication.

This configuration ensures secure and compliant SQL Server deployment.

References

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Configuring Windows Domain Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 2: Deploy and Configure an NDB Solution

When upgrading NDB and the upgrade includes updates to out-of-the-box (OOB) software profiles (e.g., predefined profiles for database software like PostgreSQL, SQL Server, etc.), NDB manages older versions of these profiles based on their usage. If the older OOB software profiles are not actively in use by any database VMs, NDB automatically deletes all versions of those profiles from its metadata and associated protection domains during the upgrade process. This cleanup mechanism helps maintain a lean and efficient system by removing obsolete profiles that are no longer relevant or required.

Option A is incorrect because the condition about Time Machines and snapshots in the last 24 hours is not a documented criterion for profile deletion during an NDB upgrade.

Option B is correct as it reflects NDB’s behavior of removing unused OOB software profiles during upgrades to optimize resource usage and metadata.

Option C is incorrect because shutting down database VMs does not trigger automatic deletion of software profiles; the key factor is whether the profiles are in use.

Option D is incorrect because the concept of a "base version" is not relevant here; deletion depends solely on whether the profiles are unused, not on versioning specifics.

This behavior ensures that only active and necessary profiles persist post-upgrade, streamlining administration.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Upgrading NDB, Section: Handling Software Profile Updates

Nutanix Support & Insights, Technical Note: "NDB Upgrade Process and Software Profile Management"

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