To replicate database snapshots to remote Nutanix clusters, the administrator needs to add Data Access to each Nutanix cluster and assign a Data Availability Management (DAM) policy. Data Access is a feature of NDB that enables cross-cluster data mobility and protection. A DAM policy defines the replication frequency, retention period, and priority of the database snapshots across the clusters. By adding Data Access to each Nutanix cluster and assigning a DAM policy, the administrator can manage the Time Machine data availability across all registered Nutanix clusters in NDB.

 Nutanix Support & Insights, section “NDB Data Access”

The size of a database Time Machine in Nutanix Era is defined by the size of all snapshots and/or transaction logs maintained by Era1. The Time Machine leverages Nutanix’s efficient snapshot technology to capture the state of the database at different points in time1. These snapshots, along with transaction logs that record changes between snapshots, constitute the data maintained by the Time Machine1. Therefore, the size of the Time Machine is determined by the total size of these snapshots and transaction logs1.

NDB allows creating and refreshing clones to a point in time using two primary methods:

B. Snapshots: NDB uses storage snapshots (e.g., via Nutanix Volumes or AHV) to capture the database state at a specific point. These snapshots can be used to create or refresh clones, providing a consistent recovery point.

D. Transaction logs: Transaction logs (e.g., PostgreSQL WAL, SQL Server logs) enable point-in-time recovery (PITR) by applying logs to a snapshot, allowing clones to be refreshed to a precise moment.

Other options are not supported for this purpose:

A. Full backups: Full backups are used for complete restores but are not optimized for frequent clone refreshes.

C. VM snapshots: VM-level snapshots (e.g., AHV snapshots) are not managed by NDB for database cloning, as they lack database consistency.

Thus, the verified answers are B and D, reflecting NDB’s clone refresh capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Time Machines and Clones.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Clones (applicable to v7.5).

Nutanix NDB Administration Guide: "Clone Creation and Refresh" section.

To migrate an existing Microsoft SQL Server (MSSQL) database to NDB, the recommended approach is to:

Provision a new database server VM and database: Use the NDB interface to provision a new VM and configure an MSSQL database instance on the Nutanix platform. This leverages NDB’s automated provisioning capabilities to ensure compatibility with Nutanix infrastructure.

Migrate the data: Transfer the data from the existing MSSQL database to the newly provisioned database. This can be achieved using native MSSQL tools (e.g., backup/restore, log shipping, or replication) or NDB’s data migration features, such as cloning or restoring from a backup, depending on the source environment.

Other options are incorrect or incomplete:

A. Use Nutanix Move to migrate the database server VM: Nutanix Move is designed for VM migration between platforms, not for database-specific migrations within NDB, which requires data migration to a new instance.

C. Create a new database server VM and database then register it with NDB: Registering an existing VM with NDB does not handle data migration from the source MSSQL database.

D. Backup your database VM and import it into Nutanix: Backing up the entire VM and importing it does not integrate the database with NDB’s management framework, and data migration would still be required separately.

Thus, the verified answer is B, providing a structured migration process tailored to NDB’s capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.5: Migrating Databases to NDB.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.4: Migrate Databases (applicable to v7.5).

Nutanix NDB Administration Guide: "Migrating MSSQL Databases to NDB" section, outlining provisioning and data migration steps.

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

In Nutanix Database Automation (NCP-DB), the Time Machine feature is used for protecting databases and creating database clones. To create a database clone using the Era Interface, an administrator should select Time Machines, select a source database, and then choose Create Clone12. This process allows the administrator to create a copy of the source database at a specific point in time1.

 In the Nutanix Database Automation (NCP-DB) process, when a database administrator is tasked with creating a new clone of a running SQL database and there are no authorized servers available, the administrator should click the Action icon to authorize one or more database server VMs1. This is because the Nutanix Database Service (NDB) requires authorized servers to perform operations such as cloning1. The authorization process allows the NDB to manage and perform operations on the database server VMs1.

NDB uses a registered Nutanix Object Store as durable storage for database log backups. When a database is registered and the administrator does not select a particular Object Store for its log drive, NDB does not fail the registration or ignore object storage. It evaluates the registered stores and assigns the first one reachable from the NDB control plane. This selection applies to the newly registered database, and subsequent log backups are written to that chosen store. The Nutanix registration procedure and knowledge-base guidance explicitly describe this first-reachable behavior when no store is specified. Therefore, option A is correct; ignoring the store, selecting it according to an unspecified priority, or failing the operation contradicts the documented workflow. Nutanix documentation

To enable multi-cluster setup for NDB High Availability (HA), the administrator must configure the NDB Agent with a Network Profile. A Network Profile defines the networking settings (e.g., VLANs, IP ranges) that the NDB Agent uses to communicate across clusters. This is critical for multi-cluster HA, as it ensures consistent network configuration for replication, failover, and data synchronization between clusters. The Network Profile must be properly configured to handle inter-cluster traffic and latency requirements (e.g., < 25ms RTT).

Other options are irrelevant:

A. Name Prefix: Used for naming conventions, not network configuration.

C. Static VLAN: A component of a Network Profile, but not the full configuration needed.

D. Compute Profile: Defines VM resources (CPU, memory), not networking for HA.

Thus, the verified answer is B, aligning with multi-cluster HA networking needs.

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: "Configuring Network Profiles for Multi-Cluster HA" section.

 Nutanix Database Service (NDB) supports automated minor version upgrades for PostgreSQL1. Before applying the patch, the administrator should create a new software profile2. This is because the software profile contains the database engine binaries and other software required to run the database engine2. Therefore, to apply a minor version upgrade, a new software profile with the updated binaries needs to be created2. Once the new software profile is created, it can be used to patch the PostgreSQL database2.