The NDB GUI allows an administrator to set the schedule interval for a database log catch up, which is the process of collecting transaction logs periodically from the source databases and storing them in the time machine. The shortest possible value for this interval is 15 minutes, as per the NDB documentation1. This means that the NDB time machine will capture the database logs every 15 minutes and use them for backup, restore, clone, and refresh operations. References: Nutanix Database Management & Automation (NDMA), page 29; Nutanix Support & Insights, section “Log Catch-up”

A Time Machine frozen status indicates that the database that was associated with the Time Machine has been de-registered from NDB, but the Time Machine itself has not been deleted. This means that the Time Machine still contains the snapshots and logs of the de-registered database, but it cannot perform any further operations on it. To resume the normal functioning of the Time Machine, the administrator can either re-register the database with NDB, or delete the Time Machine and free up the storage space.

 Nutanix Support & Insights, section “Resolving All Alerts for a Time Machine”

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.

NDB sends alert notifications using configurations auto-populated from the cluster during the initial setup, typically relying on default SMTP settings. If a dedicated SMTP server is required (e.g., for security or compliance), the administrator must change the SMTP Server configuration in NDB Service. This is configured under the NDB Admin Center, where the administrator can specify the dedicated SMTP server’s details (e.g., hostname, port, credentials, and security settings like TLS/SSL).

Other options are incorrect:

A. IDP configuration in Admin Center IAM page: Identity Provider (IDP) settings are for authentication, not email alerts.

B. Alert Email configuration in Prism Element: Prism Element manages cluster alerts, not NDB-specific email settings.

D. SNMP configuration in Prism Central: SNMP is for network monitoring, not email notifications.

Thus, the verified answer is C, reflecting NDB’s alert notification setup.

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.

NDB supports centralized drive-letter customization for SQL Server through the NDB server CLI global configuration. Nutanix documents this as the supported method for setting the database, log, backup, and TempDB drive letters used by NDB-managed provisioning and clone workflows. After the administrator changes the global values, NDB applies those assignments when it prepares eligible SQL Server database server VMs. The drive letters are not supplied interactively during each provisioning operation, stored in a Windows Domain Profile, or introduced merely by adding disks to a Software Profile. Therefore, option A is correct. The candidate file’s supplied answer B conflicts with the documented NDB configuration method and has been corrected. Nutanix SQL Server limitations

 According to the Nutanix Database Automation (NCP-DB) learning documents, when provisioning a new database, there are two options available for the target12:

Provision database to an existing registered: This option allows you to provision a database to an existing registered database server. This is useful when you want to add a database to a server that is already being managed by Nutanix Era1.

Provision databases to a new container: This option allows you to provision a database to a new container. This is useful when you want to create a new isolated environment for your database1.

The Era One-Click Provisioning service in Nutanix Database Automation (NCP-DB) simplifies and automates database administration. It brings one-click simplicity to database provisioning and life-cycle management. This service enables database administrators to provision, clone, and refresh the database clones to any point in time1. Specifically, it enables the creation of space-efficient clones and zero-byte database clones1. This is part of Era’s copy data management service, which includes components like Time Machine, one-click cloning and refresh, and one-click backup21.

NDB diagnostic collection gathers relevant logs from the NDB control plane and the database server VMs participating in the failed operation. For a Linux database server, the NDB agent collects applicable operating-system information, database-engine logs, work-driver output, and operation-specific diagnostic data. These files are packaged into a downloadable compressed bundle associated with the failed operation, allowing administrators or Nutanix Support to examine the complete execution context. NDB does not copy the active database data directory, create a runtime memory dump, or use a hypervisor snapshot of the log directory. Time Machine protects database data through snapshots and transaction logs; it is not the mechanism used to assemble support bundles. The official Nutanix instructions for viewing operation logs and downloading diagnostic bundles describe the collected and compressed diagnostic information.

When an administrator experiences issues with NDB and Nutanix Support requests a diagnostics bundle, it can be generated from two valid locations. The NDB GUI provides an option under the administration or support section to create and download the bundle, offering a user-friendly interface. Alternatively, the NDB CLI allows generation via specific commands (e.g., era diagnostics collect), providing a scriptable approach. Both methods are supported for troubleshooting and support purposes.

Option A (Prism Central GUI) is incorrect because diagnostics for NDB are managed within NDB interfaces, not Prism Central.

Option B (Prism Element GUI) is incorrect as Prism Element focuses on cluster management, not NDB-specific diagnostics.

Option C (NDB GUI) is correct as it supports bundle generation via the UI.

Option D (NDB CLI) is correct as it supports bundle generation via command-line tools.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Generating Diagnostics Bundle

Nutanix Support & Insights, Knowledge Base Article: "Collecting NDB Diagnostics for Support"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 6: Administer an NDB Environment

To change the NDB GUI password via the CLI, the administrator should use the command era-server > security password reset. This command interacts with the NDB server (referred to as era-server in the CLI context) to reset the password for the GUI admin user. The process typically prompts for the new password and confirmation, ensuring secure password management. This is the supported method for CLI-based password changes in NDB.

Other options are incorrect:

A. sudo passwd era: The passwd command is for Linux user accounts, not NDB-specific GUI credentials.

B. sudo user name admin password: This is not a valid command syntax for NDB CLI.

C. era-server > username admin password: This lacks the correct subcommand (security password reset) and syntax.

Thus, the verified answer is D, aligning with NDB’s CLI security management.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.6: Managing NDB via CLI.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.5: Manage NDB Security (applicable to v7.5).

Nutanix NDB Administration Guide: "Changing GUI Password via CLI" section, detailing era-server commands.