NCP-DB Exam Dumps - Nutanix Certified Professional (NCP) Questions and Answers

To create a Microsoft SQL Server software profile for each of the three Nutanix clusters in an NDB environment, a key requirement is that each cluster must host at least one VM with the Microsoft SQL Server database engine installed. NDB uses these VMs to discover, validate, and generate software profiles tailored to the specific SQL Server versions and configurations present on each cluster. This ensures that the profiles are compatible with the cluster’s environment and can be used for provisioning or patching.

Option A (Compute profile must be created first on every cluster) is incorrect because compute profiles are optional and not a prerequisite for creating software profiles.

Option B (Enable Multi-cluster capabilities for NDB) is incorrect as multi-cluster support is already implied by the deployment across three clusters, but it’s not a specific requirement for profile creation.

Option C (Enable High Availability for the current NDB Service) is incorrect because HA is a separate configuration and not required to create software profiles.

Option D (Each cluster must host a VM with the DB engine) is correct as it aligns with NDB’s requirement to have a reference VM for profile generation.

This setup ensures accurate and cluster-specific software profile creation.

References

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

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

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) v7.5Blueprint, Section 2: Deploy and Configure an NDB Solution

NDB supports patching for PostgreSQL database instances. Patching for PostgreSQL is validated on VMs provisioned by NDB (greenfield deployments). To patch PostgreSQL database server VMs, you must create a software profile version by uploading the PostgreSQL update file in NDB. You can then use the PostgreSQL update to patch other database server VMs or provision a new database server VM with the updated software profile. The first step in the NDB patching workflow is to create a software profile version with the desired PostgreSQL version.

Nutanix Database Automation (NCP-DB) Course Details, Section 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.1: Perform Database Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) User Guide, Section 4.4: Patch PostgreSQL Database Software

When provisioning a PostgreSQL cluster instance with an external load balancer in NDB, the administrator creates a software profile from a reference VM. The reference VM typically includes software like Patroni (for HA management), HAProxy (for internal load balancing), keepalived (for high availability IP management), and etcd (for distributed configuration). Since an external load balancer is used, the internal HAProxy can be omitted from the reference VM. NDB will rely on the external load balancer to distribute traffic, eliminating the need for HAProxy in the software profile, while the other components remain essential for cluster management.

Option A (Patroni) is incorrect because Patroni is required for PostgreSQL HA management.

Option B (HAProxy) is correct as it can be omitted when an external load balancer is configured.

Option C (keepalived) is incorrect because keepalived is needed for HA IP failover.

Option D (etcd) is incorrect because etcd is necessary for distributed configuration in the cluster.

This adjustment streamlines the profile for external load balancer use.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Creating Software Profiles for HA Instances

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

The Database Agent is used to temporarily store the transaction logs of the source database before they are copied to the log. This is a critical component for ensuring data consistency and recovery in database operations.

The "Savings over traditional cloning" metric in the Data Usage widget on the NDB dashboard reflects the efficiency of NDB’s cloning technology compared to traditional full-copy cloning methods. NDB leverages Nutanix’s near-zero byte cloning capability, which creates lightweight clones by sharing base data and only storing changes (deltas). This metric specifically quantifies the disk space saved by using these efficient clones instead of duplicating entire datasets, as would occur in traditional cloning. It highlights NDB’s storage optimization for database provisioning and management.

Option A is correct as it directly ties to NDB’s near-zero byte cloning technology, a core feature for space efficiency.

Option B (Compression) is incorrect because compression is a separate storage optimization technique not specifically tied to cloning savings.

Option C (Shadow clones) is incorrect because shadow clones are a Nutanix feature for caching, not the cloning mechanism used by NDB Time Machines.

Option D (Deduplication) is incorrect as deduplication, while related to storage savings, is not the primary mechanism reflected in this cloning-specific metric.

This metric helps administrators quantify the benefits of NDB’s cloning approach in terms of storage utilization.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Introduction to NDB, Section: Understanding Cloning and Storage Efficiency

Nutanix Support & Insights, Technical Note: "Interpreting NDB Dashboard Metrics"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 1: NDB Concepts and Architecture

Nutanix Database Service (NDB) supports high availability (HA) instances for certain relational database management systems (RDBMS). Among the listed options, NDB natively supports Oracle and PostgreSQL for HA configurations, enabling features like replication and failover. These databases are well-integrated with NDB’s Time Machine and HA frameworks.

Option A (MongoDB) is incorrect because MongoDB is a NoSQL database, not an RDBMS, and is not supported for HA instances in NDB.

Option B (MariaDB) is incorrect because, while MariaDB is an RDBMS, it is not currently supported for HA instances in NDB v7.5.

Option C (Oracle) is correct as NDB supports Oracle in HA mode with features like Data Guard integration.

Option D (PostgreSQL) is correct as NDB supports PostgreSQL HA with streaming replication.

Note: The typo "PostgreSGL" in the question is assumed to mean "PostgreSQL" based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Supported RDBMS for HA

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

If an SQL database clone deletion fails immediately in NDB, the most likely cause is that the clone has been marked as Immutable. An immutable clone is protected from deletion to prevent accidental data loss, often set for critical development or testing environments. This protection must be explicitly removed by the administrator (e.g., via the NDB GUI or CLI) before the deletion can proceed.

Option A (A refresh operation is in progress) is incorrect because a refresh operation would delay but not immediately fail the deletion.

Option B (The clone has been marked as Immutable) is correct as immutability blocks deletion until changed.

Option C (The database was not marked as Offline before the operation) is incorrect because the offline state is not a prerequisite for clone deletion.

Option D (The database data drives are shared with other applications) is incorrect because shared drives might cause issues, but immutability is a more direct cause of immediate failure.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Clones and Deletion

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

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

The command era-server > era server set ip=ip_address gateway=gateway_address netmask=ip_netmask nameserver=ns1 ntp_server=ntp1 is used to assign a static IP address to the NDB VM via the era-server CLI. This command requires core network parameters (ip, gateway, and netmask) to configure the VM’s network interface correctly. However, optional parameters like nameserver (DNS server) and ntp_server (Network Time Protocol server) can be omitted if the administrator relies on default or externally configured DNS and NTP settings (e.g., via DHCP or another management system). These optional parameters enhance functionality but are not mandatory for the basic static IP configuration.

Option A (ntp_server) is correct as it is optional and can be configured separately or omitted if NTP is managed externally.

Option B (netmask) is incorrect because the netmask is a required parameter to define the subnet for the IP address.

Option C (gateway) is incorrect because the gateway is a required parameter to specify the network route.

Option D (nameserver) is correct as it is optional and can be omitted if DNS is handled outside NDB.

Note: The typos in the question (gatevay_address, ip_J2etmas^c, narnesetver, ntpl) are assumed to be gateway_address, ip_netmask, nameserver, and ntp1 based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Configuring Network Settings via CLI

Nutanix Support & Insights, Knowledge Base Article: "Configuring Static IP for NDB VM"

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

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) v7.5Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.3: Modify Parameter Profiles (applicable to v7.5).

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