Nutanix Updated NCP-DB Exam Questions and Answers by emre

In Nutanix Database Service (NDB), alert policies are configured to notify administrators of significant events affecting database operations. The default severity level for NDB alert policies is set to Error. This level indicates issues that require attention, such as failed operations (e.g., provisioning failures, as shown in the exhibit), connectivity issues, or other critical operational problems. Other severity levels like Info, Critical, and Warning may be used for different scenarios, but the base configuration for NDB alert policies starts at Error to ensure administrators are alerted to actionable issues without being overwhelmed by less severe notifications.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.1: Configuring Alert Policies.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.2: Manage Alerts (applicable to v7.5).

Nutanix NDB Administration Guide: "Alert Policies and Severity Levels" section.

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 register a PostgreSQL database server VM with a database on NDB, the database data and log files must be located on a separate mount point from the operating system and the binary installation. This is because NDB uses the mount point as the identifier for the database server VM and the database. If the data and log files are on the same mount point as the operating system or the binary installation, NDB will not be able to recognize them as a valid database server VM or database. Therefore, the administrator should create a separate mount point for the data and log files and specify it during the registration process. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [How to Allow Remote Access to PostgreSQL database], [5 Ways to Host PostgreSQL Databases] , [Starting the Database Server].

NDB deployments on NC2 use overlay networking created with Nutanix Flow Virtual Networking. Consequently, an appropriate Flow overlay subnet must be created for NDB and the database server VMs that it will manage. A floating IP address must also be created or assigned to the NDB VM so that the NDB interface and services are reachable through the cloud networking environment. A Flow underlay subnet is not the supported network type for this deployment. Although an NC2 environment ultimately operates within AWS networking infrastructure, creating a native AWS VPC is not the NDB-specific deployment step requested by the question. Nutanix’s NC2 networking documentation identifies Flow-created overlay networks, while the Flow integration guidance describes assigning a floating IP address to the NDB VM.