A Network Profile is a collection of network settings that are used to provision database server VMs in NDB.
A Network Profile can include one or more VLANs, IP ranges, and DNS servers. To make new VLANs available when provisioning an Oracle cluster database, you need to update the Network Profile to include the new VLANs. You can do this by editing the existing Network Profile or creating a new one with the new VLANs. You do not need to create or update the VLANs in Prism Element, as NDB can discover the VLANs configured in AHV1. References:
* Nutanix Database Management & Automation (NDMA) course, Module 2, Lesson 2.4 - Network Profiles
* Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Network Profiles
* Nutanix Certified Professional - Database Automation (NCP-DB), Section 2 - Deploy and Configure an NDB Solution

According to the Nutanix Database Automation (NCP-DB) Learning documents12, to clone a source production database to an existing development server, the following actions must be taken:
A: The development server must be registered by Era in order to receive the clone1. This is because Nutanix Era is a database management tool that manages the lifecycle of databases and their copies. Registering the development server with Era allows it to manage the database on that server.
D: The development server must have the IP and credentials provided during cloning2. This is necessary for Era to access the development server and perform the cloning operation. The IP address and credentials are used to establish a connection to the development server. Without these details, Era would not be able to access the server and perform the cloning operation.

HA drivers are software components that enable high availability features for database VMs, such as failover, fencing, and heartbeat. HA drivers can be upgraded using the Life Cycle Management (LCM) feature of Nutanix Prism. LCM can detect the available updates for HA drivers and apply them to the database VMs in a non-disruptive manner. LCM can also perform health checks and pre-upgrade validations to ensure the successful completion of the upgrade process. One-click software upgrade is a feature of Nutanix Era that allows you to upgrade the Era software itself, not the HA drivers. Database VM OS patching is a feature of Nutanix Era that allows you to patch the operating system of the database VMs, not the HA drivers. Database software patching is a feature of Nutanix Era that allows you to patch the database software of the database VMs, not the HA drivers. References:
* Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 3: Configuring NDB High Availability, Slide 9: HA Driver Upgrade
* Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.4: Upgrade databases

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.
References:
* 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.

When provisioning a PostgreSQL HA Instance using NDB, the minimum and maximum number of DB server VMs that can be deployed in a cluster are 2 and 4, respectively. A PostgreSQL HA Instance is a database instance that provides high availability and fault tolerance for PostgreSQL databases using the Patroni framework. Patroni is a Python-based tool that manages PostgreSQL configuration and performs automatic failover and switchover operations. Patroni relies on a distributed consensus store, such as etcd, Consul, or ZooKeeper, to store and synchronize the cluster state and leader information. NDB supports etcd as the consensus store for PostgreSQL HA Instances. NDB allows the administrator to provision PostgreSQL HA Instances with different sizes and configurations, such as small, medium, large, or custom. The size of thePostgreSQL HA Instance determines the number of DB server VMs, the number of etcd nodes, the CPU, memory, and disk resources, and the replication factor of the database. The minimum number of DB server VMs for a PostgreSQL HA Instance is 2, which corresponds to a small size instance. This configuration provides one leader and one follower DB server VM, and one etcd node. The maximum number of DB server VMs for a PostgreSQL HA Instance is 4, which corresponds to a large size instance. This configuration provides one leader and three follower DB server VMs, and three etcd nodes. The other options are not valid for a PostgreSQL HA Instance, as they either do not provide enough redundancy or exceed the supported limit of DB server VMs. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.2: Configure an NDB Instance
* Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.2: Configuring NDB, Topic: Provisioning PostgreSQL HA Instances
* Nutanix Database Service (NDB) User Guide, Chapter 4: Provisioning Databases, Section: Provisioning PostgreSQL HA Instances
* [PostgreSQL High Availability: Under the Hood - Nutanix.dev], Section: PostgreSQL HA Architecture and Components