Online NCP-DB Questions Video

Current NDB support for MongoDB sharded clusters requires MongoDB Ops Manager for Time Machine functionality. The administrator must install and configure a supported Ops Manager instance, register it with NDB, and associate it with the provisioned sharded cluster. Time Machine must then be enabled for that cluster. Without this association, NDB reports that Time Machine capabilities are unavailable because the required sharded-cluster backup and transaction-management integration has not been established. Nutanix Guest Tools are not the prerequisite that activates MongoDB Time Machine. Option A reflects an older limitation and is incorrect for the NDB release aligned with the NCP-DB 7.5 objectives, because sharded-cluster Time Machine protection is now supported. Nutanix explicitly identifies the Ops Manager requirement in its official MongoDB Ops Manager registration documentation.

To change the static IP address on the NDB VM, an administrator would need to enter the NDB command line using the cerebro_cli command. The cerebro_cli command is used to access the Cerebro service, which is responsible for managing the NDB instance and its components. The cerebro_cli command can be run from the NDB VM or from any other VM that has network connectivity to the NDB VM. The cerebro_cli command has various subcommands and options to perform different tasks, such as changing the IP address, hostname, password, or certificate of the NDB VM. To change the static IP address, the administrator would need to use the cerebro_cli network update subcommand with the appropriate parameters, such as the new IP address, netmask, gateway, and DNS servers. The cerebro_cli network update subcommand also requires the administrator to provide the current password of the NDB VM for authentication. After changing the IP address, the administrator would need to restart the NDB VM for the changes to take effect. 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: Changing the IP Address of the NDB VM

Nutanix Database Service (NDB) Command Line Interface Guide, Chapter 2: Cerebro CLI, Section: cerebro_cli network update

NDB supports PostgreSQL HA software profiles for provisioning PostgreSQL databases with high availability. PostgreSQL HA software profiles consist of three components: etcd, HAProxy, and Patroni.

etcd is a distributed key-value store that provides a reliable way to store configuration data across a cluster of machines. etcd is used by Patroni to store and synchronize the cluster state and configuration.

HAProxy is a load balancer that distributes incoming requests to the PostgreSQL nodes. HAProxy is used to expose a single endpoint for database connections even as the roles of the individual nodes change.

Patroni is a template for PostgreSQL high availability. Patroni is responsible for managing the state of the cluster and handling failover. Patroni uses etcd as the distributed configuration store and relies on HAProxy for load balancing.

Therefore, the software component that manages the state of the cluster and handles failover is Patroni.

Nutanix Database Automation (NCP-DB) Course Details, Section 2.4: Provisioning PostgreSQL Databases

Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.4: Provision PostgreSQL Databases

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.4: Provisioning PostgreSQL Databases

[Nutanix Database Automation (NCP-DB) User Guide], Section 2.4: Provision PostgreSQL Databases

[PostgreSQL High Availability: Under the Hood – Nutanix.dev]

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.