Nutanix NCP-DB Dumps Questions Answers

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

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

NDB supports communication between a VPC containing the NDB control plane and a different VPC containing database server VMs. For this east-west communication, NDB requires No-NAT routing so that the original IP addresses remain visible and directly routable between the two VPCs. Required ports, DNS resolution, and bidirectional reachability must also be configured between NDB and the managed database server VMs. NAT-based routing is not supported for this communication path because address translation can interfere with NDB’s management connections and database lifecycle workflows. The database server VMs use Flow overlay networking rather than being restricted to an underlay network, and the control plane and database workloads do not have to reside in the same VPC. Nutanix confirms this requirement in its official NDB with Flow Virtual Networking documentation.