In Nutanix Database Service (NDB), a Network Profile is used to define networking configurations for database VMs, including VLAN assignments and IP address ranges. The correct procedure to create a Network Profile that assigns a VLAN and provides IP addresses to a database VM is as follows:
Create Network Profile: Start by initiating the creation of a new Network Profile within NDB. This is done from the NDB interface under the "Network" or "Profiles" section.
Select the VLAN: During the Network Profile creation process, you specify the VLAN that the database VM will use. This involves selecting an existing VLAN configured in the Nutanix cluster (e.g., via Prism Element) or defining a new VLAN ID if applicable.
Define IP Range: Finally, you define the IP address range (e.g., a subnet or specific IPs) that will be assigned to the database VM(s) within the selected VLAN. This ensures the VM receives a valid IP address for communication.
The sequence in option B aligns with the NDB workflow, where the Network Profile is created first, followed by associating it with a VLAN and then defining the IP allocation. Other options are incorrect:
A: "Add the VLAN" is vague and does not specify where the VLAN is added, disrupting the logical flow.
C: Adding a VLAN before creating the profile is not the standard NDB process, as VLANs are associated during profile creation.
D: Defining an IP range before creating the profile is out of sequence, as the profile must exist to hold the configuration.
Thus, the verified answer is B. Create Network Profile, Select the VLAN, Define IP Range.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.2: Configuring Network Profiles.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 3:
Manage NDB Solutions, Objective 3.1: Configure Network Profiles (applicable to v7.5).
Nutanix NDB Administration Guide: "Network Profiles" section, detailing VLAN and IP configuration steps.

To deploy Nutanix Database Service (NDB) in Prism Element, the minimum account access level required is Cluster Administrator. This role provides the necessary permissions to manage cluster resources (e.g., storage, networking, and VMs) required for NDB deployment, including registering the cluster with NDB, configuring storage containers, and deploying NDB components. Lower roles like Viewer or Backup Administrator lack the scope to perform these tasks, and User Administrator is focused on user management, not deployment.
Other options are insufficient:
* A. User Administrator: Manages users and roles, not cluster operations.
* C. Viewer: Read-only access, inadequate for deployment.
* D. Backup Administrator: Limited to backup tasks, not deployment.
Thus, the verified answer is B, aligning with NDB deployment prerequisites.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix Cluster (applicable to v6.
10).
* Nutanix NDB Installation Guide: "Prism Element Role Requirements" section.

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

For enabling Multi-Cluster management on an Era installation, the hypervisor version must be supported and port 9440 must be open between the Era VM and clusters. This ensures that the Era VM can communicate with the clusters for management tasks1.

Based on the exhibit, the administrator is logged in with the Database Admin account ([email protected]), which does not have the permission to create local users on NDB. Only the Super Admin account (bsmith) has this permission, as indicated by the User type column. Therefore, the administrator needs to log out and log in again with the Super Admin account to add a new database admin as a local user to NDB. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, Nutanix Database Automation User Guide.