Last Attempt NCP-DB Questions

According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era supports x509 certificates in Base-64 encoded PEM format1. This format is used when an administrator needs to replace the default Nutanix self-signed certificates in Era1.

A stretched VLAN is a virtual network that spans across multiple Nutanix clusters and allows the communication between VMs on different clusters using the same subnet. A stretched VLAN can be used to provide high availability and load balancing for NDB components, such as HAProxy VMs, that require a virtual IP address (VIP) to be accessible from any cluster. To add a stretched VLAN across two clusters in NDB, the administrator needs to meet two prerequisites: the VLAN must be static and both clusters must be registered in NDB. A static VLAN is a VLAN that is manually created and configured by the administrator, as opposed to an IPAM VLAN that is automatically created and managed by NDB. A static VLAN can be added to a stretched VLAN in NDB, while an IPAM VLAN cannot. Both clusters must be registered in NDB before adding a stretched VLAN, as NDB needs to have the information and access to the clusters and their networks. The administrator can register the clusters in NDB using the Prism Element details, agent network configuration, and storage container information. The other option, Nutanix Cluster Management, is not a prerequisite for adding a stretched VLAN in NDB. Nutanix Cluster Management is a feature that allows the administrator to manage multiple Nutanix clusters from a single NDB UI, such as creating or deleting clusters, adding or removing nodes, or performing cluster operations. Nutanix Cluster Management is not required for adding a stretched VLAN, as the VLANs are created and configured in Prism Element, not in NDB. References:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.3: Configure NDB High Availability

Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.3: Configuring NDB High Availability, Topic: NDB HA Architecture and Components

Nutanix Database Service High Availability Deployment Overview, Section: HAProxy VMs and Stretched VLANs

[Configuring a Virtual NIC to Operate in Access or Trunk Mode - Nutanix], Section: Creating a vNIC in Access or Trunk Mode

NDB requires the administrator to verify the Active Directory configuration before enabling the Save action. After entering the directory server, domain, service-account credentials, and related configuration information, the administrator must click Verify. NDB then tests whether it can connect to the Active Directory server and authenticate using the supplied service account. The Save button becomes available only after this verification succeeds. This prevents an unreachable server, invalid credential, incorrect domain, or connectivity problem from being stored as the active authentication configuration. SMTP alerting is a separate notification feature and has no dependency on Active Directory configuration. A secondary URL is not a mandatory field, and providing a domain IP address alone does not replace the connectivity-verification step. Nutanix documents this sequence explicitly in its official procedure for configuring Active Directory access.

The Alerts dashboard in Nutanix displays alert messages with three severity levels: Critical, Warning, and Info1. These severity levels help users understand the importance and urgency of each alert, allowing them to prioritize their responses accordingly1.