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

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) v6.5 Blueprint, Section 3: Configure an NDB Environment

To view information about all roles and the number of users assigned to each in NDB, the user must belong to the Super Administrator role. This role provides full administrative privileges, including access to the "Users and Roles" section of the NDB GUI, where role assignments and user counts are visible. Lower-tier roles (e.g., Database Infrastructure Administrator, Database Administrator, Infrastructure Administrator) have limited scopes and cannot access this comprehensive role/user overview.

Other options are insufficient:

A. Database Infrastructure Administrator: Manages infrastructure but not role/user details.

B. Database Administrator: Focuses on database operations, not user management.

C. Infrastructure Administrator: Handles cluster resources, not role/user analytics.

Thus, the verified answer is D, requiring the highest privilege level.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.4: Managing Users and Roles.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.3: Manage User Permissions (applicable to v6.10).

Nutanix NDB Administration Guide: "Role-Based Access Control (RBAC)" section, detailing Super Administrator privileges.

According to the Nutanix Database Automation (NCP-DB) learning documents, Era provides out-of-band patching of databases to eliminate database configuration sprawl1. The two Oracle software components that Era patches are:

A. Grid home2 B. Oracle home2

These components are crucial for the operation of Oracle databases and keeping them updated ensures data security and efficient validation of critical database updates1. Please refer to the official Nutanix documentation and training materials for more detailed information2.

The correct answer is B because it allows the administrator to create a custom role with the specific privileges that the Jr DBA user needs, and then assign that role to the user. This way, the administrator can control the access level of the Jr DBA user without affecting the existing roles or users in NDB. Option A is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then adding more privileges, which is unnecessary and redundant. Option C is incorrect because it involves creating a user for the Jr DBA, but not assigning a role to the user, which means the user will not have any privileges in NDB. Option D is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then removing some of the privileges, which is inefficient and risky.

References: The following sources provide more information about the user roles and privileges in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 8: Administering an NDB Environment, Lesson 8.6: Managing Access Controls in NDB

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

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.6: Managing Access Controls in NDB

When creating a Network Profile for NDB HA VMs (e.g., NDB API and Repository VMs) spread across three Nutanix clusters, the required type is PostgreSQL HA instance managed outside NDB. NDB HA relies on a PostgreSQL database for its control plane, and in a multi-cluster HA setup, this PostgreSQL instance must be configured for high availability (e.g., using streaming replication) outside NDB’s management. The Network Profile must support this external HA instance’s networking requirements (e.g., VLANs, IP ranges) to ensure connectivity across clusters.

Other options are incorrect:

A. PostgreSQL HA instance managed in NDB: NDB manages database instances, not its own HA control plane database.

B. PostgreSQL single instance managed in NDB: A single instance lacks HA, unsuitable for multi-cluster.

D. PostgreSQL single instance managed outside NDB: Lacks HA, insufficient for NDB HA VMs.

Thus, the verified answer is C, aligning with NDB HA architecture.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.2: Configuring Multi-Cluster HA.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v6.10).

Nutanix NDB Administration Guide: "Network Profile Configuration for HA VMs" section.

 In the Nutanix Database Automation (NCP-DB) framework, the role that allows an administrator to work with databases and time machines, but not database parameter profiles, is the Database Administrator (DBA)123. This role provides the necessary permissions to manage databases and time machines, which are essential components of the Nutanix Era solution. However, it does not grant access to database parameter profiles, which are typically managed by other roles45.

The correct answer is C because a stretched VLAN is a VLAN that spans across multiple Nutanix clusters, which may cause network conflicts or latency issues when starting the database server. Option A is incorrect because a DHCP VLAN is a VLAN that uses dynamic IP address allocation, which does not affect the database server startup. Option B is incorrect because a static VLAN is a VLAN that uses fixed IP address allocation, which also does not affect the database server startup. Option D is incorrect because IPAM is not a type of VLAN, but a feature of NDB that allows managing IP addresses for database servers and databases.

References: The following sources provide more information about the VLAN and IPAM concepts and configuration in NDB:

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

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

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section 2.4: Configuring NDB High Availability

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.5: Managing Networks in NDB

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.6: Managing IP Addresses in NDB

 In the context of Nutanix Database Automation (NCP-DB), a Super Admin has the authority to apply patch profiles. However, if a patch is marked as deprecated, even if it’s published, it cannot be applied. This is because deprecation is a status that indicates the patch is outdated or has been superseded by a newer version, and thus should not be used1. This behavior ensures that only the most up-to-date and secure patches are applied to the system, maintaining the integrity and security of the database environment1.

 Nutanix Era can be upgraded using the Offline Upgrade and One-click Upgrade methods. The Offline Upgrade method involves manually downloading the software update and applying it to the Era instance. The One-click Upgrade method allows you to upgrade Era directly from the Era management console with a single click, provided that the Era instance has internet connectivity and can reach the Nutanix software update portal1.

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