Nutanix NCP-DB - Nutanix Certified Professional - Database Automation (NCP-DB v7.5)

According to the Nutanix Database Automation (NCP-DB) learning documents, when doing an Era software upgrade for a Multi-Cluster enabled installation, the Era Cluster Agent is upgraded first1. This is the first component in a Nutanix Environment Upgrade cycle2. The Era Cluster Agent is crucial for managing and monitoring the health of the Nutanix clusters1. Please refer to the official Nutanix documentation and training materials for more detailed information1.

 Before patching a Linux OS on a database server VM provisioned using NDB, you must configure the repository for the OS updates. This can be done by creating a Repository Profile in NDB and specifying the URL, username, and password for the repository. The Repository Profile can be applied to one or more database server VMs during the provisioning process or later. By configuring the repository, you ensure that NDB can access and download the latest OS patches from a trusted source. References: 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.

To leverage the Oracle restore feature within Nutanix Database Service (NDB) for a Real Application Clusters (RAC) database, the administrator must ensure that the database is registered with NDB prior to initiating the restoration operation. Registration allows NDB to recognize the RAC database, manage its metadata, and perform operations like restore using Time Machine snapshots or backups. Without registration, NDB cannot access the necessary configuration details or protection data, rendering the restore feature unavailable.

Option A (Ensure the database is in a Down state) is incorrect because the database state (Up or Down) is not a prerequisite for initiating a restore; the process handles state transitions.

Option B (Ensure the database is registered with NDB) is correct as registration is the foundational requirement for NDB to manage and restore the RAC database.

Option C (Ensure the database is in an Up state) is incorrect because an Up state is not required; restore can proceed regardless of the current state.

Option D (Ensure more than one node of the RAC is reachable) is incorrect because while RAC node availability is important for HA, it is not a mandatory prerequisite for the restore operation itself.

This ensures the restore process can proceed with the necessary NDB oversight.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring RAC Databases

Nutanix Support & Insights, Knowledge Base Article: "Preparing Oracle RAC for Restore in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 5: Protect Databases Using Time Machine

 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. References: 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].

Nutanix Database Service (NDB) uses software profiles for database patching to keep your databases secure and optimized1. When a new database is provisioned, it will be on your current environment’s database version to maintain consistency and stop version sprawl1. Therefore, after an administrator has applied an Oracle security patch to a database server VM registered in Era, the change can be made available to other existing database instances by creating a new software profile in Era from the patched VM1.

 The optimal path to restore the table back with minimum data loss is to use the point in time restore feature of NDB, which allows the administrator to restore the database to a specific point in time based on the available snapshots and logs1. By restoring using point in time till 10:42pm, the administrator can recover the table just before it was dropped by the user, and minimize the data loss to the least possible amount1. The other options are not optimal, as they either involve restoring an older snapshot, which may result in more data loss, or restoring a non-existent snapshot, which is not possible. References:

1: Nutanix Database Automation (NCP-DB) course, Module 6: Database Recovery, Lesson 6.2: Point in Time Restore, slide 5

NDB patches MongoDB replica sets through a rolling workflow designed to minimize database unavailability. It first applies the selected patch to available secondary members one at a time. After the secondary members are successfully patched and validated, NDB performs the required replica-set role transitions and patches the primary member last. This order preserves service availability and avoids simultaneously taking every voting member offline. Nutanix explicitly documents rolling upgrades for MongoDB replica sets; NDB does not patch all members in parallel, and the primary is not the first member patched. Current NDB documentation also lists patching and upgrading MongoDB sharded clusters as unsupported. Therefore, the verified positive statement about the supported patching workflow is that rolling patching is available for replica sets. Nutanix MongoDB cluster-patching documentation

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

In Nutanix Database Service (NDB), patching Oracle database engines requires the "Update" button to be available on the database server VM’s management interface. If this button is missing, it typically indicates a configuration issue preventing NDB from performing the patching operation. The most common and critical reason is that the operating system (OS) credentials for the database server VM have not been set or registered with NDB. These credentials are necessary for NDB to authenticate and execute patching tasks on the VM, such as accessing the Oracle software and applying updates via a software profile.

Option A is correct because missing OS credentials prevent NDB from establishing the required connection to the VM, disabling the Update button.

Option B (Database parameters are missing) is incorrect because while database parameters are important for configuration, they do not directly control the visibility of the Update button for patching.

Option C (Oracle DB engines cannot be patched) is incorrect as NDB explicitly supports patching Oracle databases when properly configured.

Option D (Software profile is not published) is incorrect because an unpublished software profile might limit availability to users, but the Update button’s presence relies on VM connectivity, not profile publication status.

To resolve this, the administrator must register valid OS credentials for the VM in NDB, enabling the patching functionality.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Patching Database Engines

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Missing Update Button in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Software Profiles

When configuring an SMTP server for sending alert notifications via email in NDB, the two security options available are SSL and TLS. These protocols encrypt the email communication between NDB and the SMTP server, ensuring the confidentiality and integrity of alert notifications. NDB supports both options to accommodate different SMTP server configurations, with TLS being the more modern standard and SSL as a legacy option.

Other options are not applicable:

B. S/MIME: This is used for email content encryption, not SMTP server configuration.

C. DKIM: This is a domain authentication method, not a security protocol for SMTP.

Thus, the verified answers are A and D, reflecting NDB’s SMTP security features.

Official Nutanix Database Automation References

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

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: "Configuring SMTP for Alerts" section, listing SSL and TLS options.