To ensure the NDB server, NDB agent, and NDB database agent can communicate with the registered

cluster via REST API calls, port 2009 must be opened. This port is used by NDB components to

facilitate RESTful communication with the Nutanix cluster (e.g., Prism Element or Prism Central) for

operations such as provisioning, monitoring, and management. Proper firewall configuration to

allow traffic on this port is a prerequisite for NDB’s integration with the cluster.

Other options are incorrect:

B . 3205: Not a standard NDB port; used for other Nutanix services.

C . 3260: Associated with iSCSI, not REST API communication.

D . 9440: Used for Prism Element’s HTTPS management interface, not NDB-specific REST calls.

Thus, the verified answer is A, reflecting NDB’s REST API requirements.

Official Nutanix Database Automation Reference:

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring

an NDB Solution, Lesson 2.1: Network and Port Requirements.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section

2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v6.10).

Nutanix NDB Installation Guide: "Network Ports and Protocols" section, specifying port 2009.

There are two ways to upgrade an NDB Server: one-click upgrade and offline upgrade. One-click

upgrade is the recommended method, as it automatically downloads and installs the latest NDB

software version from the Nutanix portal. Offline upgrade is an alternative method, which requires

you to manually download the NDB software bundle and upload it to the NDB Server VM. Both

methods require you to have a valid Nutanix account and an internet connection. Reference::

Nutanix Certified Professional - Database Automation (NCP-DB), Section 6 - Administer an NDB

Environment

Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 10, Objective 6.2

Nutanix Database Management & Automation (NDMA) course, Module 6, Lesson 6.1 - NDB Software

Upgrade

NDB supports patching for PostgreSQL database instances. Patching for PostgreSQL is validated on

VMs provisioned by NDB (greenfield deployments). To patch PostgreSQL database server VMs, you

must create a software profile version by uploading the PostgreSQL update file in NDB. You can then

use the PostgreSQL update to patch other database server VMs or provision a new database server

VM with the updated software profile. The first step in the NDB patching workflow is to create a

software profile version with the desired PostgreSQL version.

Reference::

Nutanix Database Automation (NCP-DB) Course Details, Section 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.1: Perform Database

Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) User Guide, Section 4.4: Patch PostgreSQL Database

Software

In Nutanix Era, an administrator can modify the Alert Severity level by navigating to the Alerts

Policies from the dropdown menu. Once there, they can select the Policy that needs to be modified

and set the desired severity level1. This allows the administrator to customize the alerts according to

their requirements, ensuring that they are notified of the most critical events in their

environment21.

To add Time Machine data access to a Nutanix cluster, the first step is to register the cluster in NDB.

This will allow NDB to discover and manage the databases and snapshots on the cluster. You can

register multiple Nutanix clusters in NDB using the Add Cluster option in the NDB settings page. You

can also specify the cluster role, such as source, target, or both, depending on the data access and

replication needs. Enabling or disabling multi-cluster in NDB is not the first step, as this is a global

setting that affects the entire NDB instance. Deleting the TM data from the source database is not the

first step, as this will remove the data protection and availability of the database. Reference::

Nutanix Database Management & Automation Training Course, Module 6: Managing NDB Multi-

Cluster, Lesson 1: NDB Multi-Cluster Overview, Slide 5: Registering Nutanix Clusters

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 6: Administer an

NDB Environment, Objective 6.4: Apply procedural concepts to add Nutanix clusters to NDB

To increase storage for a MongoDB database provisioned using NDB, the administrator needs to use

the extend_storage parameter in the input file for the NDB CLI. This parameter specifies the amount

of additional storage to be added to the database server VM in GB. For example, if the current

storage size is 100 GB and the administrator wants to increase it to 150 GB, the input file should

contain the following line:

extend_storage: 50

The other parameters are not relevant for this operation. The update parameter is used to update

the database software version, the database parameter is used to specify the database name, and

the data_percent parameter is used to specify the percentage of data to be copied during a clone

operation. Reference:: 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].

Page files are temporary files that Windows uses to store data that does not fit in the physical

memory. Page files can interfere with the registration of a database server VM with NDB, as they can

cause errors or performance issues. Therefore, page files should be located in a separate drive or

partition from the C:\ drive, where the NDB agent and other files are installed. System, database, and

backup files do not prevent the registration of a database server VM with NDB, as long as they are

not corrupted or incompatible with the NDB requirements. Reference::

Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring

an NDB Solution, Lesson 2: Configuring an NDB Instance, Slide 13: Registering Database Server VMs

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and

Maintain an NDB Environment, Objective 4.1: Apply procedural concepts to register database server

VMs and databases

The default continuous recovery for the Gold SLA in Era Time Machine is 30 days1. This means that

the system keeps a continuous recovery point for the last 30 days, allowing you to restore your

database to any point within this period1.

When an Oracle database is upgraded using Era, the type of upgrade category is an “In-place

upgrade”. This method involves upgrading the database software within the same Oracle home as

the existing database. The AutoUpgrade utility is used to automate the upgrade process, both before

starting upgrades, during upgrade deployments, and during post-upgrade checks and configuration

migration1. This method is preferred due to its simplicity and efficiency1.

The administrator should perform a rolling upgrade, applying the patch to the secondary members

first, followed by the primary member, to accomplish the task of patching a MongoDB server cluster

within an NDB environment. A rolling upgrade is a method of applying patches or updates to a

cluster without downtime or interruption of service. The administrator can use the NDB patching

feature to perform a rolling upgrade on a MongoDB server cluster, which consists of a primary

member and one or more secondary members that form a replica set. The NDB patching feature

allows the administrator to select the software profile version, the database parameters profile, and

the network profile for the patching operation. The NDB patching feature also automates the steps of

the rolling upgrade, such as:

Step 1: The administrator initiates the patching operation on the NDB instance, and selects the

MongoDB server cluster to be patched.

Step 2: The NDB instance verifies the prerequisites and compatibility of the patching operation, and

creates a pre-patch snapshot of the MongoDB server cluster.

Step 3: The NDB instance applies the patch to the first secondary member of the MongoDB server

cluster, and waits for the patching to complete successfully.

Step 4: The NDB instance verifies the status and functionality of the patched secondary member, and

repeats the patching process for the remaining secondary members of the MongoDB server cluster,

one at a time.

Step 5: The NDB instance performs a failover of the primary member to one of the patched

secondary members, and applies the patch to the original primary member.

Step 6: The NDB instance verifies the status and functionality of the patched primary member, and

performs a failback of the primary member to the original primary member, if desired.

Step 7: The NDB instance creates a post-patch snapshot of the MongoDB server cluster, and

completes the patching operation.

Performing a rolling upgrade, applying the patch to the secondary members first, followed by the

primary member, is the recommended and best practice method of patching a MongoDB server

cluster within an NDB environment, as it ensures the high availability, consistency, and performance

of the MongoDB server cluster and the databases.

Performing a rolling upgrade, applying the patch to the primary member first, followed by the

secondary members, is not a valid or feasible method of patching a MongoDB server cluster within

an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB

server cluster and the databases. Applying the patch to the primary member first would disrupt the

replication and synchronization of the MongoDB server cluster, and would require manual

intervention and recovery steps to restore the MongoDB server cluster to a functional state.

Applying the patch to all nodes at once is not a valid or feasible method of patching a MongoDB

server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency

of the MongoDB server cluster and the databases. Applying the patch to all nodes at once would

require shutting down the entire MongoDB server cluster, and would expose the MongoDB server

cluster and the databases to potential errors, failures, and corruption during the patching process.

Disabling the replica set while patching is not a valid or feasible method of patching a MongoDB

server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency

of the MongoDB server cluster and the databases. Disabling the replica set while patching would

break the replication and synchronization of the MongoDB server cluster, and would require manual

intervention and recovery steps to re-enable the replica set and restore the MongoDB server cluster

to a functional state.

Reference::

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations,

Lesson 5.1: Nutanix Era Operations, slides 11-12, 15-16.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations,

Lesson 5.3: Nutanix Era Patching, slides 5-9.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations,

Lesson 5.4: Nutanix Era Patching Lab, slides 5-10.

Nutanix Database Management & Automation Training Course, Module 7: Nutanix Era

Troubleshooting, Lesson 7.1: Nutanix Era Troubleshooting, slide 6.