A database administrator wanting to be notified in advance before any database clones are removed using a removal schedule can configure this directly within the NDB interface. The "Update Removal Schedule" feature includes an option labeled "Create an Alert Before Removal," which is pre-selected as non-optional by default but can be customized. Selecting this option generates an alert (e.g., via email or the NDB dashboard) prior to the scheduled clone removal, allowing the administrator to take action if needed. This is the most efficient and built-in method, avoiding the complexity of custom scripts or reports.
Option A (Create a Playbook to create an alert based on the removal event) is incorrect because a Playbook is an advanced automation tool, not the simplest solution for this notification need.
Option B (Select the Create an Alert Before Removal option) is correct as it is a native NDB feature designed for this purpose.
Option C (Build a custom report in Prism to report on these events) is incorrect because Prism reports are for historical analysis, not real-time notifications.
Option D (Configure SMTP alerts for all actions in NDB) is incorrect because configuring SMTP for all actions is overly broad and less targeted than the specific alert option.
This ensures timely notifications with minimal configuration.
References
Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Clone Removal Schedules Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 5: Protect Databases Using Time Machine

When creating a Network Profile for NDB HA VMs (e.g., NDB API and Repository VMs) spread across three Nutanix clusters, the required type is PostgreSQL HA instance managed outside NDB. NDB HA relies on a PostgreSQL database for its control plane, and in a multi-cluster HA setup, this PostgreSQL instance must be configured for high availability (e.g., using streaming replication) outside NDB's management. The Network Profile must support this external HA instance's networking requirements (e.g., VLANs, IP ranges) to ensure connectivity across clusters.
Other options are incorrect:
A). PostgreSQL HA instance managed in NDB: NDB manages database instances, not its own HA control plane database.
B). PostgreSQL single instance managed in NDB: A single instance lacks HA, unsuitable for multi-cluster.
D). PostgreSQL single instance managed outside NDB: Lacks HA, insufficient for NDB HA VMs.
Thus, the verified answer is C, aligning with NDB HA architecture.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.2: Configuring Multi-Cluster HA.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 4:
Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v7.5).
Nutanix NDB Administration Guide: "Network Profile Configuration for HA VMs" section.

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

For deploying Nutanix Database Service (NDB), the required file type to download from the Nutanix Portal is an OVA (Open Virtual Appliance) file. The OVA format is a standardized package that includes a pre- configured virtual machine image, including the NDB software, which can be imported into supported hypervisors (e.g., VMware ESXi or Nutanix AHV). This simplifies the deployment process by providing a ready-to-use VM template with all necessary components.
Option A (ZIP) is incorrect as ZIP files are generic archives, not deployment-specific formats for NDB.
Option B (QCOW2) is incorrect because QCOW2 is a disk image format primarily used with KVM/QEMU, not the standard for NDB deployment.
Option C (OVA) is correct as it is the official file type provided by Nutanix for NDB deployment.
Option D (TAR) is incorrect as TAR files are used for archiving, not as a deployment package for NDB.
Administrators should download the OVA from the Nutanix Portal and follow the deployment guide.
References
Nutanix Database Service (NDB) User Guide, Chapter 1: Deploying NDB, Section: Downloading and Deploying the OVA Nutanix Support & Insights, Knowledge Base Article: "NDB Deployment Prerequisites" Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 1: Deploy NDB

According to the Nutanix Database Automation (NCP-DB) learning documents, to configure Era to send alert notifications to email recipients, you need to go to the Administration section, select Era Service, then go to the configure notification widget. From there, you can update the SMTP server configuration1. This allows Era to use the SMTP server to send alert notifications to the specified email recipients1.