Nutanix NCP-DB - Nutanix Certified Professional - Database Automation (NCP-DB v7.5)

When restoring a PostgreSQL HA instance in NDB, if the standby node fails to restore but the primary node is successfully restored and ready to serve application traffic, NDB considers the database operational from the perspective of the primary node. In this scenario, NDB leaves the database in an "ONLINE" state, reflecting that the primary node is functional and capable of handling requests, even though the HA configuration is not fully intact due to the standby failure. The administrator would need to address the standby node separately (e.g., by re-provisioning or troubleshooting), but the database’s state is determined by the primary node’s readiness.

Option A (PAKFIAL.READY) appears to be a typo and is not a valid NDB state.

Option B (OFFLINE) is incorrect because the primary node is operational, so the database is not offline.

Option C (ONLINE) is correct as it reflects the primary node’s ability to serve traffic.

Option D (RECOVERY PENDING) is incorrect because the primary node has completed recovery and is active, not pending.

This behavior aligns with NDB’s focus on maintaining service availability where possible.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring HA Instances

Nutanix Support & Insights, Knowledge Base Article: "Handling Partial Restore Failures in PostgreSQL HA"

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

An NDB Software Profile contains an image of the database software and operating system generated from a registered database server VM. Therefore, the template or reference VM must first be registered with NDB before the administrator can use it as the source for creating the profile. NDB then captures the applicable software and OS artifacts so that the profile can be reused for standardized database-server provisioning. Running the prerequisites script is useful for validating required packages and configuration before registration, but it does not itself make the VM a Software Profile source. Uploading a QCOW2 image is associated with deploying the NDB appliance, not creating a database Software Profile. Configuring SELinux is engine- and OS-dependent and is not the universal first action. Therefore, A is correct. Nutanix software-profile workflow

================

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

To release PostgreSQL HA instances using a dedicated subnet in Nutanix Database Service (NDB), the administrator must create a network profile that defines the subnet and its associated VLAN. Before creating this network profile, it is mandatory to add a VLAN to the NDB Networks configuration. This VLAN ensures that the dedicated subnet is recognized and manageable within NDB, allowing the HA instances to be provisioned with isolated network connectivity. The VLAN must be configured in the NDB Networks page to be available for selection during network profile creation.

Option A (The subnet in Prism Element must be IPAM configured) is incorrect because IP Address Management (IPAM) configuration in Prism Element is optional and not a mandatory prerequisite for creating a network profile in NDB.

Option B (The DB VMs must be registered first) is incorrect because VM registration is a subsequent step, not a prerequisite for network profile creation.

Option C (A VLAN must be added to NDB networks) is correct as it is a required step to define the network infrastructure before creating the profile.

Option D (Configure Network Segmentation) is incorrect because network segmentation is an advanced feature and not mandatory for basic network profile setup.

This ensures the dedicated subnet is properly integrated into NDB for HA provisioning.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring Network Profiles

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

NDB High Availability distributes control-plane components across three Nutanix clusters so that a single cluster or site does not become the sole failure domain. For deployments spanning separate data centers or sites, the supported round-trip time between the selected clusters must be less than 25 milliseconds. A two-cluster topology is not supported because the cluster hosting two API servers and two repository servers would remain a single point of failure. Option C is also too restrictive: the three clusters may use AHV or ESXi; they are not required to be three AHV clusters. Consequently, option A is correct. The List B answer of D, which states less than 5 milliseconds, conflicts with Nutanix’s documented HA requirement and has been corrected. Nutanix NDB HA architecture

================

 According to the Nutanix Database Automation (NCP-DB) learning documents, to refresh an existing DB Clone, a developer with RBAC privileges in Era needs to navigate to Databases > Clones. From there, they select the appropriate clone from the table, click Refresh, select the desired Point In Time or Snapshot, and then click Refresh12. This process allows the developer to update the cloned database3.

NDB sends notifications when alerts are generated via email. The email notifications can be configured to send to one or more recipients, and can be customized to include the alert severity, category, description, and resolution steps. The email notifications help to inform the database administrator and other stakeholders about the status and issues of the NDB-managed databases and operations.

NDB does not send notifications via SNMP, APIs, or Pulse. SNMP is a protocol for collecting and organizing information about managed devices on a network. APIs are interfaces for communicating and exchanging data between different applications or systems. Pulse is a feature of the Nutanix cluster that collects and sends diagnostic and usage data to Nutanix for analysis and support.

Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment, Lesson 3.2: Nutanix Era Deployment, slide 11.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slide 6.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.2: Nutanix Era Alerts and Notifications, slides 5-7.

Comprehensive and Detailed 100 to 150 words of Explanation From Nutanix Database Management & Automation (NDMA) topics:

NDB cluster registration must account for storage containers associated with resources that need to be available during cross-cluster operations. Although the NDB control-plane VM and database provisioning operations use the same NDB container in this scenario, NutanixManagementShare is a separate Nutanix-managed service container. Its corresponding remote-container relationship must therefore be represented through storage mapping. Mapping the NDB container to default-container is unnecessary because the NDB server and provisioning storage are already consolidated. Removing SCSI disks from the NDB VM would damage the appliance configuration, while an attached CD-ROM does not justify altering the required storage mapping. This differs from the existing questions, which ask when mapping is required because the NDB server and provisioning containers are separate. Therefore, option A is correct. Nutanix cluster-registration documentation

In the context of Nutanix Database Automation (NCP-DB), when provisioning a new Oracle SIHA DB & VM, if only ASMFD is available in the ASM Driver drop-down, it indicates that ASMLIB is not included in the current software profile. To provision the requested SIHA DB and DB VM with ASMLIB, it’s essential to update the software profile to include the ASMLIB driver. This action will enable ASMLIB as an option in the ASM Driver drop-down during the provisioning workflow.

Nutanix Database Automation (NCP-DB) Course Details, Section 2.3: Provisioning Oracle Databases

Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.3: Provision Oracle Databases

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.3: Provisioning Oracle Databases

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