NCP-DB Exam Dumps - Nutanix Certified Professional - Database Automation (NCP-DB v6.10)

The correct answer is C because it follows the recommended procedure for applying a CU to a SQL Server Software Profile in NDB. By applying the patch to the profile VM, the administrator ensures that the CU is compatible with the existing Software Profile settings and configuration. By creating a new Software Profile version, the administrator preserves the previous version of the Software Profile for rollback purposes and allows the new version to be tested and published. Option A is incorrect because it deletes the existing Software Profile, which may cause data loss and prevent rollback. Option B is incorrect because it does not apply the patch to the profile VM, which may result in errors or inconsistencies in the Software Profile. Option D is incorrect because it creates a new Software Profile instead of a new version, which may cause confusion and duplication.

References: The following sources provide more information about the Software Profile management and patching in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 5: Patching Databases Using NDB, Lesson 5.2: Creating and Modifying Software Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 4 - Operate and Maintain an NDB Environment

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.2: Creating and Modifying Software Profiles

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.3: Testing and Publishing Database Patches

The Time Machine Heal function in NDB is designed to address inconsistencies or gaps in the Time Machine’s restore point chain, ensuring a continuous and reliable recovery history. It identifies and repairs missing log backups or snapshots that may have been skipped due to failures (e.g., network issues or agent errors), thereby removing gaps in the restore capability. This function does not patch software, refresh clones, or restore from malware but focuses on maintaining the integrity of the Time Machine’s data protection timeline.

Other options are incorrect:

A. Patches a Time Machine to the latest NDB levels: This is a software update, not a heal function’s purpose.

C. Refreshes a database clone in Time Machine: Clone refresh is a separate operation, not related to healing.

D. Restores a Time Machine from snapshot in the event of malware: Restoration is a distinct action, while heal addresses data gaps.

Thus, the verified answer is B, reflecting the heal function’s role in restore continuity.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.4: Managing Time Machine Operations.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.4: Use Time Machine Features (applicable to v6.10).

Nutanix NDB Administration Guide: "Time Machine Heal Function" section.

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 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) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v6.10).

Nutanix NDB Installation Guide: "Network Ports and Protocols" section, specifying port 2009.

The exhibit shows the NDB user management interface with a newly created user named "ndb_test" assigned the "Database Infrastructure Admin" role and sourced as a "Local User." In NDB, the "Database Infrastructure Admin" role grants specific permissions, allowing the user to manage database-related tasks such as creating, managing, and deleting clones, as well as performing configuration tasks within the NDB environment (e.g., updating settings or managing database servers). However, this role does not extend to higher-level administrative functions like Access Control or Network Profiles, which are reserved for roles with broader administrative privileges (e.g., System Administrator).

Option A (Access Control) is incorrect because managing user access and roles requires a higher privilege level, such as System Administrator, not Database Infrastructure Admin.

Option B (Network Profiles) is incorrect because configuring network profiles is an administrative task outside the Database Infrastructure Admin scope.

Option C (Clones) is correct as the Database Infrastructure Admin role includes permissions to create and manage clones using Time Machine.

Option D (NDB Configuration) is correct as this role allows configuration of database-related settings within NDB, such as registering VMs or adjusting database parameters.

Thus, the "ndb_test" user can perform clone management and NDB configuration tasks.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: User Roles and Permissions

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

According to the Nutanix Database Automation (NCP-DB) learning documents, metadata tags can be applied to various entities in Nutanix Era for better database inventory management1. Among the options provided, Databases and Clones are two entities that support metadata tags1. These tags can be used to categorize, search, and manage these entities more effectively1. Please note that the information might be available in the Nutanix Database Automation (NCP-DB) course materials or in the Nutanix Era documentation.

NDB supports PostgreSQL HA software profiles for provisioning PostgreSQL databases with high availability. PostgreSQL HA software profiles consist of three components: etcd, HAProxy, and Patroni.

etcd is a distributed key-value store that provides a reliable way to store configuration data across a cluster of machines. etcd is used by Patroni to store and synchronize the cluster state and configuration.

HAProxy is a load balancer that distributes incoming requests to the PostgreSQL nodes. HAProxy is used to expose a single endpoint for database connections even as the roles of the individual nodes change.

Patroni is a template for PostgreSQL high availability. Patroni is responsible for managing the state of the cluster and handling failover. Patroni uses etcd as the distributed configuration store and relies on HAProxy for load balancing.

Therefore, the software component that manages the state of the cluster and handles failover is Patroni.

References:

Nutanix Database Automation (NCP-DB) Course Details, Section 2.4: Provisioning PostgreSQL Databases

Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.4: Provision PostgreSQL Databases

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.4: Provisioning PostgreSQL Databases

[Nutanix Database Automation (NCP-DB) User Guide], Section 2.4: Provision PostgreSQL Databases

[PostgreSQL High Availability: Under the Hood – Nutanix.dev]

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.