The administrator can add a stretched VLAN in NDB using either static or dynamic VLANs. A stretched VLAN is a VLAN that spans across multiple Nutanix clusters, and allows the NDB-managed databases to communicate and migrate between different clusters. A static VLAN is a VLAN that is manually configured and assigned to the database server VMs and the databases by the administrator. A dynamic VLAN is a VLAN that is automatically configured and assigned to the database server VMs and the databases by the NDB instance, using the Nutanix Calm orchestration service. Both static and dynamic VLANs can be used to create a stretched VLAN in NDB, as long as they have the same VLAN ID and network configuration across the clusters.
The administrator cannot add a stretched VLAN in NDB using only VLANs that are not managed in NDB. A VLAN that is not managed in NDB is a VLAN that is configured and assigned to the database server VMs and the databases outside of the NDB instance, using the Nutanix Prism web console or other tools. A VLAN that is not managed in NDB cannot be used to create a stretched VLAN in NDB, as it is not recognized or controlled by the NDB instance.
Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slide 8.
Nutanix Database Management & Automation Training Course, Module 6: Nutanix Era Disaster Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 6-7.

NDB High Availability (HA) is a feature that ensures the availability and reliability of the NDB management plane components, such as the API Server, the Repository VMs, and the NDB Agents. To enable NDB HA, you need to deploy at least three HA Proxy VMs on the same L2 network as the NDB Server VM. The HA Proxy VMs act as load balancers and health monitors for the NDB management plane components, and they also provide a single endpoint for accessing the NDB APIs and UI. References:
Nutanix Certified Professional - Database Automation (NCP-DB), Section 2 - Deploy and Configure an NDB Solution Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 7, Objective 2.3 Nutanix Database Management & Automation (NDMA) course, Module 2, Lesson 2.3 - NDB High Availability

If a database administrator is unable to provision a new MongoDB database using an existing software profile, the most likely cause is that the administrator lacks the proper permissions in Prism Element.
NDB relies on Prism Element for cluster-level operations (e.g., storage and compute resource allocation). The database administrator needs appropriate Prism Element roles (e.g., Cluster Admin) to interact with the underlying infrastructure, even if the software profile is available in NDB. Without these permissions, the provisioning action will fail.
Other options are less likely:
* A. A database clone operation is in progress: This might delay actions but wouldn't prevent provisioning unless it locks resources indefinitely.
* B. The software profile was created by another user: NDB allows profile reuse across users if published, so this is not a barrier.
* D. The software profile is undergoing a patching operation: Patching affects the profile's state but doesn't block provisioning unless explicitly locked.
Thus, the verified answer is C, highlighting the need for Prism Element permissions.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Provisioning Databases.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
3: Manage NDB Solutions, Objective 3.1: Troubleshoot Provisioning Issues (applicable to v6.10).
* Nutanix NDB Administration Guide: "Prerequisites for Database Provisioning" section, noting Prism Element roles.

The exhibit shows the configuration of unencrypted Active Directory (AD) access in NDB, with the "Primary URL" set to ldap:// (indicating LDAP rather than LDAPS). Unencrypted LDAP communication uses port 389 by default. For NDB to communicate with Active Directory, this port must be allowed through the firewall to enable the NDB server to perform authentication and directory lookups using the specified service account (e.
g., administrator).
Other options are incorrect in this context:
B). 636: This is the default port for LDAPS (LDAP over SSL/TLS), which is encrypted and not applicable since the configuration uses unencrypted LDAP.
C). 2009: This is not a standard port for LDAP or AD communication and is unrelated to NDB's AD integration.
D). 9440: This is associated with Prism Element's HTTPS management interface, not AD access.
Thus, the verified answer is A. 389, ensuring unencrypted LDAP communication between NDB and Active Directory.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.5: Configuring Active Directory Integration.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2:
Deploy and Configure an NDB Solution, Objective 2.4: Configure AD Access (applicable to v7.5).
Nutanix NDB Administration Guide: "Active Directory Integration" section, detailing LDAP port requirements.

When an administrator changes the NDB language settings from English to Spanish, but the language reverts to English when accessing NDB from a different workstation, it indicates that the language settings are tied to the web browser on the original workstation rather than being globally applied. NDB's language settings are typically stored locally in the browser's cache or preferences (e.g., via cookies or browser locale settings), meaning they do not persist across different devices or browsers unless explicitly synchronized (e.g., via user profile settings, which NDB does not universally enforce).
Other options are incorrect:
B). The language settings match workstation regional settings: This would depend on the OS locale, not the observed behavior of reverting to English.
C). The language settings revert to English after logoff: NDB does not reset language settings upon logoff; the issue is device-specific.
D). The language settings are bound to NDB users: If this were true, the language would persist across workstations for the same user, which is not the case here.
Thus, the verified answer is A, reflecting browser-local language management.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.3:
User Interface Customization.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 1:
Understand NDB Basics, Objective 1.2: Navigate the NDB UI (applicable to v7.5).
Nutanix NDB User Guide: "Customizing Language Settings" section, noting browser dependency.