NCP-DB Nutanix Certified Professional - Database Automation (NCP-DB v6.10) Questions and Answers

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.

References: Nutanix Support & Insights, section “NDB Data Access”

To capture database transaction logs in NDB, the Log Catch-up operation within the Time Machine is used. Log Catch-up retrieves and applies transaction logs (e.g., PostgreSQL WAL, SQL Server logs) to a snapshot, ensuring the database can be restored to a specific point in time. This operation bridges gaps between snapshots by incorporating log data, maintaining a continuous recovery chain.

Other options are incorrect:

A. Write-Ahead Logging: A database feature (e.g., in PostgreSQL), not an NDB Time Machine operation.

B. Log Flush: Refers to writing logs to disk, not capturing them for recovery.

D. Snapshots: Capture the database state but do not handle transaction logs specifically.

Thus, the verified answer is C, aligning with NDB’s log management.

Official Nutanix Database Automation References

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

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Time Machine Operations (applicable to v6.10).

Nutanix NDB Administration Guide: "Log Catch-up Operation" section.

Before registering a SQL Server VM with Nutanix Database Service (NDB), the administrator must ensure that the VM is configured to allow NDB to communicate with and manage it. For SQL Server VMs running on Windows, NDB relies on Windows Remote Management (WinRM) to facilitate remote administration, discovery, and management tasks. WinRM is a Microsoft protocol that enables secure communication between the NDB control plane and the Windows-based database server VM. It must be enabled and properly configured (e.g., with HTTP or HTTPS listeners and appropriate firewall rules) to allow NDB to register the VM and perform operations like provisioning, patching, or cloning.

Option A (Secure Shell - SSH) is incorrect because SSH is a protocol primarily used for Linux-based systems, not Windows-based SQL Server VMs. NDB uses WinRM for Windows environments.

Option B (Remote Management - WinRM) is correct as it aligns with NDB’s requirements for managing Windows VMs hosting SQL Server instances.

Option C (Remote Desktop - RDP) is incorrect because RDP is a protocol for interactive desktop access, not for the automated management and communication required by NDB.

Option D (Windows PowerShell) is incorrect as a standalone answer. While PowerShell can leverage WinRM for remote execution, NDB specifically requires WinRM to be enabled as the underlying service, not just PowerShell itself.

To verify WinRM is enabled, the administrator can run winrm quickconfig on the SQL Server VM or check the service status and firewall settings. NDB documentation emphasizes this prerequisite to ensure successful registration and management of SQL Server VMs.

References

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Registering Database Server VMs

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Configure an NDB Instance

Nutanix Support & Insights, Technical Note: "Preparing Windows VMs for NDB Registration"

 Nutanix Era can be upgraded using the Offline Upgrade and One-click Upgrade methods. The Offline Upgrade method involves manually downloading the software update and applying it to the Era instance. The One-click Upgrade method allows you to upgrade Era directly from the Era management console with a single click, provided that the Era instance has internet connectivity and can reach the Nutanix software update portal1.

The Time Machine Heal function in NDB is designed to address inconsistencies or gaps in the Time Machine’s restore point chain, ensuring a continuous and reliable recovery history. It identifies and repairs missing log backups or snapshots that may have been skipped due to failures (e.g., network issues or agent errors), thereby removing gaps in the restore capability. This function does not patch software, refresh clones, or restore from malware but focuses on maintaining the integrity of the Time Machine’s data protection timeline.

Other options are incorrect:

A. Patches a Time Machine to the latest NDB levels: This is a software update, not a heal function’s purpose.

C. Refreshes a database clone in Time Machine: Clone refresh is a separate operation, not related to healing.

D. Restores a Time Machine from snapshot in the event of malware: Restoration is a distinct action, while heal addresses data gaps.

Thus, the verified answer is B, reflecting the heal function’s role in restore continuity.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.4: Managing Time Machine Operations.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.4: Use Time Machine Features (applicable to v6.10).

Nutanix NDB Administration Guide: "Time Machine Heal Function" section.

A new web application with up to 200 concurrent connections to a PostgreSQL database requires a robust and scalable configuration. Provisioning a PostgreSQL HA (High Availability) instance in NDB is the most effective action to achieve this goal. An HA instance leverages replication (e.g., streaming replication) to distribute load and ensure availability, accommodating high concurrency by allowing multiple nodes to handle traffic. This approach simplifies configuration compared to manual scripting or parameter adjustments.

Option A (Use Post Create Command when provisioning the DB) is incorrect because post-create commands are for custom scripts, not optimal for handling concurrent connections.

Option B (Create a new Database Parameters profile) is incorrect because while it can tune settings, it’s less efficient than HA for scaling concurrency.

Option C (Edit the API equivalent shell script) is incorrect as it’s a manual and error-prone method compared to HA provisioning.

Option D is correct because a PostgreSQL HA instance natively supports high concurrency and availability.

Note: The typo "PostqreSQL" is assumed to mean "PostgreSQL."

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Provisioning HA Instances

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Engines

To configure a database with a Time Machine protection mode that includes the Log Catchup operation in NDB, the most essential component is a Service Level Agreement (SLA) that supports continuous log retention. The Log Catchup operation enables point-in-time recovery (PITR) by replaying transaction logs from a specified point, ensuring minimal data loss and meeting Recovery Point Objective (RPO) requirements. This functionality depends on the Time Machine being configured with an SLA that includes the "Continuous Log Retention" option, which ensures transaction logs are captured and retained continuously alongside snapshots.

Option A is incorrect because a daily snapshot alone is insufficient without log retention to enable Log Catchup.

Option B is incorrect because an SLA retention schedule for daily snapshots does not inherently include continuous log capture, which is required for Log Catchup.

Option C is correct as it specifies the Continuous Log Retention option, the critical feature for enabling Log Catchup in a Time Machine SLA.

Option D is incorrect because while frequency settings are important, they are secondary to selecting an SLA with continuous log retention as the foundational requirement.

This configuration ensures robust data protection and recovery capabilities tailored to the database’s needs.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Setting Up SLAs with Log Catchup

Nutanix Support & Insights, Knowledge Base Article: "Configuring Time Machine with Log Catchup in NDB"

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

To deploy Microsoft SQL Servers in an Active Directory (AD) environment and select a specific service account to start up the database, the administrator must configure a Windows domain profile in NDB. A Windows domain profile defines the AD integration settings, including the service account credentials (e.g., username and password) that NDB uses to authenticate and manage the SQL Server instances. This configuration ensures the database starts and runs under the specified AD service account, aligning with enterprise security policies.

Option A (Compute profile) is incorrect because a compute profile defines VM resources (CPU, memory), not AD or service account settings.

Option B (Sysprep Windows image) is incorrect because Sysprep is for generalizing Windows images, not configuring AD service accounts.

Option C (Windows domain profile) is correct as it is the specific NDB feature for AD integration and service account management.

Option D (Database parameters) is incorrect because database parameters tune database settings, not AD authentication.

This configuration ensures secure and compliant SQL Server deployment.

References

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Configuring Windows Domain Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 2: Deploy and Configure an NDB Solution

The Global Service Level Agreement (SLA) feature of Era allows an administrator to create Time Machine policies in a Multi-Cluster configuration1. This feature provides a unified way to manage and enforce backup and replication policies across multiple clusters, ensuring consistent data protection and recovery across the entire environment1.

When downloading a list of alerts from NDB, the available file format is csv (Comma-Separated Values). NDB provides this format to export alert data (e.g., alert ID, timestamp, severity, description) in a structured, machine-readable way that can be easily imported into spreadsheet applications like Microsoft Excel or analyzed programmatically. This aligns with NDB’s focus on operational efficiency and data portability.

Other options are not supported:

A. xlsx: Excel’s native format is not offered by NDB for alert exports.

C. xml: Not a supported format for alert downloads in NDB.

D. pdf: Used for reports, not alert list exports.

Thus, the verified answer is B, reflecting NDB’s export capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.2: Managing Alerts.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.2: Manage Alerts (applicable to v6.10).

Nutanix NDB Administration Guide: "Exporting Alerts" section, specifying CSV format.

According to the Nutanix Database Automation (NCP-DB) course, the Pre-Post Commands section allows the administrator to specify custom scripts that can be executed before or after the clone operation1. The masking script can be created on any of the VMs that have access to the source database, such as the source DB VM, the Dev VM, or the SW Profile VM2. The script should contain the commands to mask the sensitive data in the Finance database, such as replacing the real values with dummy values or encrypting the data2. The administrator can then create the clone from the Time Machine and define the post-clone option with the full path and name of the masking script1. This will ensure that the script is executed after the clone is created, and the data is masked before it is available for the development team1. The other options are not correct, as they either use the wrong field (pre-clone instead of post-clone), or do not specify where to create or store the masking script. References:

1: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 5

2: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 7

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

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

HA drivers are software components that enable high availability features for database VMs, such as failover, fencing, and heartbeat. HA drivers can be upgraded using the Life Cycle Management (LCM) feature of Nutanix Prism. LCM can detect the available updates for HA drivers and apply them to the database VMs in a non-disruptive manner. LCM can also perform health checks and pre-upgrade validations to ensure the successful completion of the upgrade process. One-click software upgrade is a feature of Nutanix Era that allows you to upgrade the Era software itself, not the HA drivers. Database VM OS patching is a feature of Nutanix Era that allows you to patch the operating system of the database VMs, not the HA drivers. Database software patching is a feature of Nutanix Era that allows you to patch the database software of the database VMs, not the HA drivers. References:

Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 3: Configuring NDB High Availability, Slide 9: HA Driver Upgrade

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.4: Upgrade databases

A "dark site" refers to an environment with no internet connectivity, requiring manual processes for software updates. For Nutanix Database Service (NDB) in such a setup, updates cannot be downloaded automatically from the internet. The correct procedure is to:

Download the upgrade bundle: Access the Nutanix Support Portal from a system with internet access and download the NDB upgrade bundle specific to the version (e.g., v6.10 or later).

Manually upload it to the NDB server: Transfer the bundle to the NDB server (e.g., via SCP or USB) and upload it through the NDB interface under the "Software Updates" or "Maintenance" section.

Other options are incorrect in a dark site context:

B: The "Administrator > Maintenance" section allows initiating updates, but it cannot download files without internet access.

C: Changing the network to access https://download.nutanix.com defeats the dark site’s isolation and is impractical.

D: Uploading to Prism Element > Images is for VM images or other Prism-specific content, not NDB software updates.

Thus, the verified answer is A, aligning with Nutanix’s documented process for dark site updates.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Updating NDB in Dark Sites.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.3: Perform NDB Updates (applicable to v6.10).

Nutanix NDB Administration Guide: "Updating NDB in a Dark Site Environment" section.

When a database administrator creates a clone removal schedule in NDB, the system automates the cleanup of cloned databases based on the defined schedule (e.g., after a set retention period). The two default actions taken on the cloned database are:

A. NDB deletes the cloned database: The clone’s data is removed from storage to free up space.

B. NDB de-registers the cloned database: The clone is removed from NDB’s management inventory, ensuring it no longer appears in the GUI or is tracked.

Other options are not default actions:

C. NDB marks the cloned database as offline: This is a temporary state, not a removal action.

D. NDB deletes the cloned database VM: Deleting the VM is not automatic; it depends on the clone type (e.g., linked clones retain the VM).

Thus, the verified answers are A and B, aligning with NDB’s clone management.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "Clone Removal Schedule Actions" 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

In Nutanix Database Automation (NCP-DB), when an administrator logs into Era and sees a message “Update Available” on the Status of the Software Profile Version, it indicates that a newer version of the software profile is available1. The administrator should manually update the software profile to the latest version12. This process ensures that the database VM is running the most recent and compatible version of the software12.

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) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

NDB Multi-Cluster is a feature that allows multiple Nutanix clusters to share a common NDB service for database management and automation. NDB service consists of two components: NDB Server and NDB Agent. NDB Server is the central component that provides the web UI, REST API, and database orchestration logic. NDB Agent is the component that runs on each Nutanix cluster and communicates with the NDB Server to perform database operations.

When NDB Multi-Cluster is enabled on Cluster A, it becomes the primary cluster that hosts the NDB Server VM. Cluster B, which is registered with NDB, becomes a secondary cluster that hosts only the NDB Agent VM. Therefore, Cluster A has both NDB Server and NDB Agent, while Cluster B has only NDB Agent. This configuration allows Cluster B to leverage the NDB service running on Cluster A for database management and automation.

References:

Nutanix Database Automation (NCP-DB) Course Details, Section 3.1: NDB Multi-Cluster Overview

Nutanix Database Automation (NCP-DB) Certification Details, Objective 3.1: Configure NDB Multi-Cluster

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 3.1: NDB Multi-Cluster Overview

Nutanix Database Automation (NCP-DB) allows administrators to manage Service Level Agreements (SLAs) for databases. These SLAs define the data protection policies for databases. In this case, to minimize storage usage for a test database, the administrator should select the built-in NONE SLA. This SLA is configured for no snapshot or log backup, thus minimizing storage usage1.

The Removal schedule is a feature of Nutanix Era that allows you to specify when a database clone will be automatically deleted. You can modify the Removal schedule of an existing clone by selecting the clone from the Clones page, clicking on the Update button, and changing the Removal schedule option to the desired date. This way, you can extend or shorten the lifespan of a clone as per your requirements. You do not need to remove the existing Removal schedule and add a new one, as this would be an unnecessary step. You also do not need to update the Removal schedule to the end of the month, as this would not meet the request of keeping the clone for an additional 14 days. References:

Nutanix Database Management & Automation Training Course, Module 4: Protecting Databases Using Time Machine, Lesson 3: Cloning Databases, Slide 10: Clone Removal Schedule

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 5: Protect NDB-managed Databases Using Time Machine, Objective 5.3: Given business requirements, perform a database clone

After a new NDB deployment, the administrator can test the provisioning capabilities using a database instance that is fully supported and readily configurable out of the box. PostgreSQL is the most suitable option because it is one of the core database engines supported by NDB from the initial deployment, with built-in provisioning templates and HA capabilities. NDB provides a streamlined process to provision PostgreSQL instances, making it an ideal choice for testing provisioning workflows, including VM creation, storage allocation, and network configuration.

Other options may require additional setup or licensing:

B. Oracle DB: Requires specific licensing and additional configuration, not typically available for initial testing.

C. MSSQL Server: Supported but may need Microsoft licensing and setup, less immediate than PostgreSQL.

D. MongoDB: Supported but less commonly used for initial testing due to its NoSQL nature and additional configuration needs.

Thus, the verified answer is A, reflecting PostgreSQL’s accessibility for testing.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Provisioning Databases.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Provision Database Instances (applicable to v6.10).

Nutanix NDB Administration Guide: "Supported Databases for Provisioning" section, noting PostgreSQL availability.

 The correct answer is A because NDB handles the database restore operation by copying the specific database files from the snapshot volume to the source volume, without affecting the other databases that share the same source volume. NDB uses a copy-on-write mechanism to create snapshots and clones, which means that only the changes made to the database files are stored in the snapshot or clone volume, while the original files are kept in the source volume. Therefore, when restoring a source database from a snapshot, NDB only needs to copy the specific database files that have been modified since the snapshot was taken, and overwrite them on the source volume. The other options are not correct because they either cause data loss or unnecessary data transfer. Option B is not correct because replacing the source volume with specific db disks would erase the other databases that share the same source volume, which is not desirable. Option C is not correct because replacing the source volume with the snapshot volume would also erase the other databases that share the same source volume, as well as any changes made to the source database after the snapshot was taken, which is not desirable. Option D is not correct because copying all database files to the source volume would be inefficient and unnecessary, as only the modified files need to be copied, and the other files are already present on the source volume. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, [Nutanix Support & Insights]

When provisioning a PostgreSQL cluster instance with an external load balancer in NDB, the administrator creates a software profile from a reference VM. The reference VM typically includes software like Patroni (for HA management), HAProxy (for internal load balancing), keepalived (for high availability IP management), and etcd (for distributed configuration). Since an external load balancer is used, the internal HAProxy can be omitted from the reference VM. NDB will rely on the external load balancer to distribute traffic, eliminating the need for HAProxy in the software profile, while the other components remain essential for cluster management.

Option A (Patroni) is incorrect because Patroni is required for PostgreSQL HA management.

Option B (HAProxy) is correct as it can be omitted when an external load balancer is configured.

Option C (keepalived) is incorrect because keepalived is needed for HA IP failover.

Option D (etcd) is incorrect because etcd is necessary for distributed configuration in the cluster.

This adjustment streamlines the profile for external load balancer use.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Creating Software Profiles for HA Instances

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

When an administrator encounters an error provisioning a new Oracle database VM in NDB, the best action to provide Nutanix support with the most complete picture is to select the failed job in the Operations menu and choose Generate Bundle from the lower right. The "Generate Bundle" option creates a comprehensive diagnostic package, including logs, configuration details, and error traces specific to the failed operation. This bundle is ideal for troubleshooting and can be uploaded to Nutanix Support for analysis.

Other options are less comprehensive:

A. From the Administration section of NDB, go to the Diagnostics section and choose Generate Bundle: This generates a general diagnostic bundle, not specific to the failed job.

B. Copy the error message from the Operations menu: This provides limited context compared to a full bundle.

D. Take a screenshot of the error in the Operations menu: A screenshot lacks detailed logs and system data needed for support.

Thus, the verified answer is C, ensuring detailed support data.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.4: Troubleshooting and Support.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.4: Generate Support Bundles (applicable to v6.10).

Nutanix NDB Administration Guide: "Generating Support Bundles for Failed Operations" section.

For an NDB offline upgrade, you need to download the upgrade bundle from the Nutanix Support Portal and copy it to the NDB server. Then, you need to use the NDB CLI command upload upgrade_bundle with the path parameter to specify the location of the upgrade bundle file. This command will upload the upgrade bundle to the NDB server and verify its integrity. After uploading the upgrade bundle, you can use the upgrade command to perform the upgrade. References: Nutanix Support & Insights, Cisco Nexus Data Broker Deployment Guide, Release 3.10.x

 In the Nutanix Database Automation (NCP-DB) framework, the role that allows an administrator to work with databases and time machines, but not database parameter profiles, is the Database Administrator (DBA)123. This role provides the necessary permissions to manage databases and time machines, which are essential components of the Nutanix Era solution. However, it does not grant access to database parameter profiles, which are typically managed by other roles45.

According to the Nutanix Database Automation (NCP-DB) learning documents, metadata tags can be applied to various entities in Nutanix Era for better database inventory management1. Among the options provided, Databases and Clones are two entities that support metadata tags1. These tags can be used to categorize, search, and manage these entities more effectively1. Please note that the information might be available in the Nutanix Database Automation (NCP-DB) course materials or in the Nutanix Era documentation.

When an administrator enables NDB Multi-cluster functionality, certain components are deployed or reconfigured to support the distributed environment. HAProxy (High Availability Proxy) is a critical component that manages load balancing and secure communication across clusters. In a multi-cluster setup, HAProxy is deployed on a dedicated VM to ensure efficient traffic distribution and high availability for NDB services, such as API calls and GUI access, across the clusters. This dedicated deployment enhances scalability and resilience.

Option A (Agent VM) is incorrect because Agent VMs are typically deployed on managed database VMs, not as dedicated NDB service components in multi-cluster setups.

Option B (HAProxy) is correct as it is specifically deployed on a dedicated VM to handle load balancing in a multi-cluster NDB environment.

Option C (Repository DB) is incorrect because the Repository DB is part of the NDB control plane and not necessarily deployed on a separate VM for multi-cluster purposes.

Option D (APIVM) is incorrect because the API VM is part of the core NDB infrastructure but not specifically deployed as a dedicated VM for multi-cluster enablement.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Multi-Cluster Configuration

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

When registering a Nutanix cluster with NDB, a manual storage mapping between the remote container and the NDB provisioning container is required if the NDB Server container and NDB Provisioning container are separate. This separation occurs when the storage containers used by the NDB server (for its own operations) and the provisioning container (for database VMs) are distinct, either due to multi-cluster setups or custom configurations. Manual mapping ensures NDB can correctly allocate storage resources and manage database provisioning across these containers.

Other conditions do not necessitate manual mapping:

B. Disaster Recovery Network Segmentation is enabled on the cluster: This affects networking, not storage mapping.

C. Nutanix Database Service High Availability is enabled on the cluster: HA configurations handle replication, not container mapping.

D. DB VMs are stored in the NDB Server or NDB Provisioning container: This is a typical setup and does not require manual mapping unless containers differ.

Thus, the verified answer is A, addressing storage container separation.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix Cluster (applicable to v6.10).

Nutanix NDB Administration Guide: "Storage Container Mapping" section.

The command era-server > era server set ip=ip_address gateway=gateway_address netmask=ip_netmask nameserver=ns1 ntp_server=ntp1 is used to assign a static IP address to the NDB VM via the era-server CLI. This command requires core network parameters (ip, gateway, and netmask) to configure the VM’s network interface correctly. However, optional parameters like nameserver (DNS server) and ntp_server (Network Time Protocol server) can be omitted if the administrator relies on default or externally configured DNS and NTP settings (e.g., via DHCP or another management system). These optional parameters enhance functionality but are not mandatory for the basic static IP configuration.

Option A (ntp_server) is correct as it is optional and can be configured separately or omitted if NTP is managed externally.

Option B (netmask) is incorrect because the netmask is a required parameter to define the subnet for the IP address.

Option C (gateway) is incorrect because the gateway is a required parameter to specify the network route.

Option D (nameserver) is correct as it is optional and can be omitted if DNS is handled outside NDB.

Note: The typos in the question (gatevay_address, ip_J2etmas^c, narnesetver, ntpl) are assumed to be gateway_address, ip_netmask, nameserver, and ntp1 based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Configuring Network Settings via CLI

Nutanix Support & Insights, Knowledge Base Article: "Configuring Static IP for NDB VM"

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

Before updating Oracle Database software, you need to download the Patch Set Update (PSU) from Oracle support. A PSU is a collection of critical and security patches for Oracle products. You need to have a valid Oracle account and access to the My Oracle Support portal to download the PSU. You also need to check the compatibility and prerequisites of the PSU before applying it to your Oracle Database software. NDB uses out-of-place patching for Oracle, which means you need to create a new software profile version with the patched Oracle software and use it to update your existing databases. References:

Patch Oracle Database Software, Nutanix Support & Insights

Nutanix Certified Professional - Database Automation (NCP-DB), Section 4 - Operate and Maintain an NDB Environment

Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.4 - Patching Databases

The correct answer is B because setting VM-Host affinity ensures that the DB Server VMs are not migrated to another host during the LCM upgrade process. This way, the DB Server VMs can continue to serve the database requests without interruption. Option A is incorrect because updating the Nutanix cluster does not prevent the DB Server VMs from being moved to another host. Option C is incorrect because removing the Nutanix cluster from NDB will make the DB Server VMs unmanaged by NDB and lose the benefits of NDB features. Option D is incorrect because unsetting VM-Host affinity will allow the DB Server VMs to be migrated to another host during the LCM upgrade process, which may cause downtime or performance degradation.

References: The following sources provide more information about the LCM upgrades and VM-Host affinity in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 6: Administering an NDB Environment, Lesson 6.3: Performing NDB Software Upgrades

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 6 - Administer an NDB Environment

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.3: Performing NDB Software Upgrades

Nutanix Support & Insights, Your guide to the Upgrades, LCM Design

Nutanix Life Cycle Manager Guide, Chapter 3: Upgrading Software and Firmware, Section 3.2: Preparing for an Upgrade, VM-Host Affinity

To release PostgreSQL HA instances using a dedicated subnet in Nutanix Database Service (NDB), the administrator must create a network profile that defines the subnet and its associated VLAN. Before creating this network profile, it is mandatory to add a VLAN to the NDB Networks configuration. This VLAN ensures that the dedicated subnet is recognized and manageable within NDB, allowing the HA instances to be provisioned with isolated network connectivity. The VLAN must be configured in the NDB Networks page to be available for selection during network profile creation.

Option A (The subnet in Prism Element must be IPAM configured) is incorrect because IP Address Management (IPAM) configuration in Prism Element is optional and not a mandatory prerequisite for creating a network profile in NDB.

Option B (The DB VMs must be registered first) is incorrect because VM registration is a subsequent step, not a prerequisite for network profile creation.

Option C (A VLAN must be added to NDB networks) is correct as it is a required step to define the network infrastructure before creating the profile.

Option D (Configure Network Segmentation) is incorrect because network segmentation is an advanced feature and not mandatory for basic network profile setup.

This ensures the dedicated subnet is properly integrated into NDB for HA provisioning.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring Network Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

In NDB, publishing a software profile update for Microsoft SQL Server makes it available for broader use within the NDB environment. When an administrator creates and publishes an updated software profile (e.g., with a new SQL Server patch or version), this action allows all authorized NDB users to leverage that profile to patch or update the database software on their managed VMs. This is a key feature of NDB’s software profile management, enabling centralized control and distribution of standardized database configurations.

Option A is correct because publishing a profile democratizes access, allowing all users to apply the update to their database VMs, aligning with NDB’s collaborative administration model.

Option B is incorrect because it suggests the profile patches itself, which is not the intent; publishing enables usage, not self-application.

Option C is incorrect because publishing does not automatically deprecate older profiles; deprecation is a separate administrative decision.

Option D is incorrect because publishing facilitates patching, not stalls it.

This process enhances efficiency and consistency in managing SQL Server updates across an organization.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Creating and Publishing Software Profiles

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

The correct answer is D. When setting up a 3-node MSSQL Server AG with two database server VMs on a local site and a third database server VM on a remote site, the network at each site will require the following IP addresses:

1 Cluster VIP and 1 Listener IP on the local site123.

1 Cluster VIP and 1 Listener IP on the remote site123.

2 IPs in the local site and 1 on the remote site for the database server nodes123.

This configuration ensures that each node in the cluster has a unique IP address, and each cluster and listener also has a unique IP address. This is necessary for the proper functioning of the cluster and to ensure that all nodes can communicate with each other and with clients123.

The provided exhibit shows the "Enable Multi-Cluster" configuration wizard in NDB, where the VLAN dropdown is empty with a "Nothing found" message, indicating that no VLANs are available for selection. This issue arises because NDB requires a network profile to be created before provisioning the NDB Agent VM and enabling multi-cluster support. A network profile defines the static VLANs managed by NDB, which are essential for network configuration during multi-cluster setup. The warning in the exhibit ("An NDB managed static vLAN is required to provision the NDB Agent VM. Add an NDB managed static vLAN using the Networks page to continue.") reinforces that the administrator must create a network profile via the Networks page to populate the VLAN dropdown.

Option A (A network profile must be created first) is correct as it addresses the root cause by ensuring VLANs are defined in a network profile.

Option B (Verify if subnet leverages advanced network control) is incorrect because advanced network control is not a prerequisite for VLAN selection in this context.

Option C (IP address pool must be managed in NDB) is incorrect because IP address pools are managed separately and not required for VLAN selection at this stage.

Option D (VLAN subnet must use IP address management) is incorrect because IP address management is not a direct requirement for enabling VLAN selection in the wizard.

After creating the network profile, the administrator can proceed with the multi-cluster enablement.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring Network Profiles for Multi-Cluster

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting VLAN Issues in NDB Multi-Cluster Setup"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

To add multiple databases to an existing PostgreSQL instance managed by NDB, the administrator should use the NDB graphical user interface (GUI). The GUI provides a user-friendly way to modify the parameter profile associated with the PostgreSQL instance, allowing the addition of new databases by adjusting settings such as database names, sizes, or configurations. This process typically involves navigating to the "Databases" or "Instances" section, selecting the PostgreSQL instance, and editing the parameter profile to include additional databases.

Other options are less appropriate:

A. Modify parameter profile using ncli: The ncli (Nutanix Command Line Interface) is used for cluster-level management in Prism, not for NDB database configuration.

C. Modify parameter profile using post script: Post-scripts are used for custom actions post-provisioning, not for modifying parameter profiles to add databases.

D. Modify parameter profile using NDB CLI: While NDB has a CLI, the GUI is the recommended and supported method for such configuration changes, offering a guided workflow and validation.

Thus, the verified answer is B, leveraging the NDB GUI for ease and compliance with best practices.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.4: Modifying Database Configurations.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.3: Modify Parameter Profiles (applicable to v6.10).

Nutanix NDB Administration Guide: "Managing PostgreSQL Instances" section, detailing GUI-based modifications.

According to the Nutanix Database Automation (NCP-DB) learning documents, to create a network profile in Era, the network must be added to Era1. This is because Era needs to have control over the network in order to manage the databases effectively1. Once the network is added to Era, it can be used for various operations such as provisioning new databases, managing existing databases, and more1.

 NDB SLAs are service level agreements that define the data protection and recovery objectives for NDB-managed databases. NDB SLAs consist of data retention policies that specify how long the snapshots and log backups of a database are kept in the Time Machine. Data retention policies can be customized to meet different business and compliance requirements, such as daily, weekly, monthly, or yearly retention periods. NDB SLAs also determine the frequency and schedule of the snapshots and log backups, as well as the storage location and replication options. An administrator who is tasked with auditing NDB SLAs will be reviewing the data retention policies of each database and Time Machine, as well as the snapshot and log backup history and status. The administrator will also be able to monitor the storage usage and performance of the NDB SLAs, and modify or delete the SLAs as needed. The other options are not part of the NDB SLAs, but rather separate features or concepts of NDB. Snapshot schedules are the intervals at which NDB takes snapshots of the databases, which are determined by the SLAs. Clone management is the process of creating, refreshing, or deleting database clones from the Time Machine. Recovery time objective (RTO) is the maximum acceptable time for restoring a database after a failure, which is influenced by the SLAs, but not defined by them. References:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 5 - Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies

Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: SLA Concepts

Nutanix Database Service (NDB) User Guide, Chapter 6: SLAs, Section: SLA Overview

In an NDB environment, the repository VM stores metadata and configuration data but is not a critical runtime component for service availability. If the team powers off the repository VM during maintenance, and it is neither the primary nor a synchronized copy node, the NDB service will continue to operate without interruption. NDB’s high availability (HA) architecture, managed by HAProxy and other components, ensures redundancy and failover capabilities, allowing the system to rely on the primary and synchronized nodes. The repository VM’s downtime only affects metadata access, which can be restored post-maintenance without impacting ongoing database operations.

Option A (The HAProxy VMs will failover instead) is incorrect because HAProxy failover is triggered by primary service node failures, not repository VM power-off.

Option B (There will be no service interruption) is correct as the HA design tolerates a non-primary, non-synchronized repository VM being offline.

Option C (Manual interaction will be required to restore service) is incorrect because no service restoration is needed during this scenario.

Option D (NDB services will fail over immediately) is incorrect because failover is not triggered by a non-critical repository VM power-off.

This reflects NDB’s robust HA implementation.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: High Availability Architecture

Nutanix Support & Insights, Knowledge Base Article: "Impact of Repository VM Maintenance in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

NDB Agents handle log backups for database instances, but storing these backups locally can lead to bottlenecks (e.g., disk I/O, storage capacity). To alleviate this, integrating NDB with Nutanix Objects is the recommended solution. Nutanix Objects is an S3-compatible object storage service within the Nutanix ecosystem, ideal for offloading log backups from NDB Agents to a scalable, centralized storage platform. This reduces local storage pressure, improves performance, and ensures strict SLAs for database recovery by leveraging efficient backup retrieval.

Other options are less effective:

A: Integrating with AWS S3 or Azure Blob is possible but requires external connectivity and introduces latency, complexity, and cost compared to Nutanix Objects.

B: Adding NDB Agent VMs increases management overhead and doesn’t address the root storage bottleneck.

D: Increasing RAM/CPU on NDB Agents may help processing but doesn’t solve storage capacity or I/O issues for log backups.

Thus, C is the verified answer, aligning with Nutanix’s integrated ecosystem approach.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.3: Configuring Log Backup Storage.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.3: Configure Backup Storage Options (applicable to v6.10).

Nutanix NDB Administration Guide: "Integrating NDB with Nutanix Objects for Log Backups" section.

Nutanix Era is a database management solution that automates and simplifies database administration tasks such as provisioning, patching, cloning, and backup. In the event of a database crash, the most effective way to minimize data loss and reduce restore time is to perform a restore of the source database by selecting the most recent point in time and including the Tail log Backup12.

The Tail log Backup includes all the transactions that have occurred since the last transaction log backup, which helps to minimize data loss. By selecting the most recent point in time for the restore, the administrator ensures that the database is restored to the state it was in just before the crash, thereby reducing the amount of data that needs to be reprocessed or reentered12. This approach aligns with the Nutanix Era’s capabilities and best practices for database recovery12.

For supported Linux-based database VMs managed by NDB, keeping software profiles updated for provisioning new database VMs requires a structured process. The administrator must first apply the necessary patches (e.g., OS updates and database engine patches) to an existing database VM for each supported database engine (e.g., PostgreSQL, Oracle). Then, a new software profile version must be created using the updated VM as the source. This new version captures the patched configuration and can be used to provision new VMs, ensuring they are deployed with the latest updates.

Option A (Create a Maintenance window under the policy menu, then under Database VM, add the database VMs to that maintenance window and check both Database and Operating system updates) is incorrect because a Maintenance Window schedules updates for existing VMs, not for updating software profiles for new provisions.

Option B (Apply patches to a database VM for each supported database engine, then create a new software profile version for each supported database VM for each one using the updated database VM as the source) is correct as it follows the standard NDB process for profile updates.

Option C (Associate the newly provisioned database VMs with a maintenance window so they are kept updated) is incorrect because this applies to ongoing maintenance, not initial profile updates for provisioning.

Option D (In the Administrator menu drop down, go the Maintenance tab and choose Download Upgrade) is incorrect because downloading upgrades is part of the patch process, not the profile creation step.

This method ensures new VMs are provisioned with the latest software configurations.

References

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

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

When an administrator needs to restore databases provisioned with a shared disk configuration on Windows Storage Spaces in Nutanix Database Service (NDB), the restore operation focuses on the disks associated with the database. Windows Storage Spaces provides a virtualized storage layer, and NDB manages the restoration by reverting or recovering the specific disks that host the database files and logs. This ensures that the database is restored to its previous state using the snapshot or backup data, while preserving the shared disk configuration integrity. NDB does not replace the source volume or perform additional operations like tail log backups unless explicitly configured.

Option A (NDB restores the disk that are associated with the database) is correct as it accurately describes NDB’s restore behavior for shared disk setups.

Option B (NDB copies the DB files to be restored to the source volume) is incorrect because NDB restores the entire disk state, not just copying files to the source.

Option C (NDB replaces the source volume with the snapshot volume) is incorrect because NDB restores data to the existing volume, not replacing it entirely.

Option D (NDB performs Tail Log backup to backup any remaining logs) is incorrect because tail log backups are not automatically part of the restore process unless specified for point-in-time recovery.

This approach ensures compatibility with Windows Storage Spaces configurations.

References

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

Nutanix Support & Insights, Knowledge Base Article: "Restoring Windows Storage Spaces in NDB"

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

Nutanix Era offers Role-Based Access Control capabilities by organically embedding them in the product. It provides the ability to add and remove users from Era, create and assign roles to users, and associate various privileges with a role1. The default roles available within Era for Role-Based Access Control are:

prism Admin

Era Super Admin

Era Database Admin

Era Infrastructure Admin1 These roles allow for the management of both physical resources like IP addresses and VLANs along with database entities like databases, time-machines, clones, and so on1.

 An Infrastructure Administrator is a role in NDB that has the permission to manage network and storage resources, such as VLANs, IP Pools, and Storage Containers. This role is suitable for the engineer who needs to add new VLANs or IP Pools in NDB. The other roles have either more or less privileges than required for this task. A Database Administrator can manage databases and database server VMs, but not network and storage resources. A Super Administrator can manage all aspects of NDB, but this is more than the least-privilege access needed. A Database Infrastructure Administrator can manage both databases and network and storage resources, but this is also more than the least-privilege access needed.

References: Nutanix Support & Insights, section “NDB Roles and Permissions”

The correct answer is D because it meets the requirements of maintaining five days of time-travel capability to any second and an additional seven days of discrete recovery at a daily interval. Continuous log retention allows the administrator to restore the database to any point in time within the specified number of days, while snapshot retention allows the administrator to restore the database to a specific point in time at a fixed interval. Therefore, by setting the daily snapshot retention to 7 days, the administrator can ensure that there is a discrete recovery point for each day of the week. By setting the continuous log retention to 5 days, the administrator can ensure that there is a time-travel capability to any second within the last five days. The other options do not meet the requirements because they either have less than five days of continuous log retention or less than seven days of snapshot retention. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Certified Professional - Database Automation (NCP-DB) datasheet

The correct answer is C because a stretched VLAN is a VLAN that spans across multiple Nutanix clusters, which may cause network conflicts or latency issues when starting the database server. Option A is incorrect because a DHCP VLAN is a VLAN that uses dynamic IP address allocation, which does not affect the database server startup. Option B is incorrect because a static VLAN is a VLAN that uses fixed IP address allocation, which also does not affect the database server startup. Option D is incorrect because IPAM is not a type of VLAN, but a feature of NDB that allows managing IP addresses for database servers and databases.

References: The following sources provide more information about the VLAN and IPAM concepts and configuration in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Configuring NDB High Availability

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 2 - Deploy and Configure an NDB Solution

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section 2.4: Configuring NDB High Availability

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.5: Managing Networks in NDB

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.6: Managing IP Addresses in NDB

In an NDB high availability (HA) environment spanning multiple Nutanix clusters, with two clusters running VMware ESXi and one running Nutanix AHV, cross-hypervisor compatibility becomes essential to manage the heterogeneous environment effectively. Nutanix Prism Central is the centralized management platform that provides a unified interface and orchestration capabilities across multiple clusters, regardless of the underlying hypervisor (ESXi or AHV). For NDB HA to function seamlessly across these clusters, Prism Central is required to coordinate cluster operations, manage resources, and ensure consistent policy enforcement, including VM placement, failover, and database management tasks. It abstracts the differences between hypervisors, enabling NDB to operate in a mixed environment.

Option A (Stretched VLANs for all nodes) is incorrect because stretched VLANs address network connectivity, not hypervisor compatibility or NDB HA management.

Option B (NGT - Nutanix Guest Tools) is incorrect as NGT enhances guest VM functionality (e.g., drivers, backups) but does not facilitate cross-hypervisor orchestration for NDB HA.

Option C (Nutanix Prism Central) is correct because it provides the necessary multi-cluster management and compatibility layer for NDB HA across ESXi and AHV.

Option D (VirtlO) is incorrect as VirtIO refers to paravirtualized drivers for VMs, not a component for NDB HA or cross-hypervisor support.

Prism Central’s role ensures that NDB can manage database workloads across diverse hypervisor platforms efficiently.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Multi-Cluster and Multi-Hypervisor Support

Nutanix Prism Central Administration Guide, Section: Managing Mixed Hypervisor Environments

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

To create a Microsoft SQL Server software profile for each of the three Nutanix clusters in an NDB environment, a key requirement is that each cluster must host at least one VM with the Microsoft SQL Server database engine installed. NDB uses these VMs to discover, validate, and generate software profiles tailored to the specific SQL Server versions and configurations present on each cluster. This ensures that the profiles are compatible with the cluster’s environment and can be used for provisioning or patching.

Option A (Compute profile must be created first on every cluster) is incorrect because compute profiles are optional and not a prerequisite for creating software profiles.

Option B (Enable Multi-cluster capabilities for NDB) is incorrect as multi-cluster support is already implied by the deployment across three clusters, but it’s not a specific requirement for profile creation.

Option C (Enable High Availability for the current NDB Service) is incorrect because HA is a separate configuration and not required to create software profiles.

Option D (Each cluster must host a VM with the DB engine) is correct as it aligns with NDB’s requirement to have a reference VM for profile generation.

This setup ensures accurate and cluster-specific software profile creation.

References

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

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

When performing a SQL Server Restore Source Database operation in Nutanix Database Automation (NCP-DB), an administrator might choose the Restore Location as New Location if they want to restore to a new location and have Era apply Nutanix best practices1. This is because Nutanix Era automates and simplifies database management, allowing the administrator to manage databases at scale, and it applies Nutanix best practices during the restore process1. This ensures optimal performance and reliability of the restored database1.

When an administrator changes the NDB language settings from English to Spanish, but the language reverts to English when accessing NDB from a different workstation, it indicates that the language settings are tied to the web browser on the original workstation rather than being globally applied. NDB’s language settings are typically stored locally in the browser’s cache or preferences (e.g., via cookies or browser locale settings), meaning they do not persist across different devices or browsers unless explicitly synchronized (e.g., via user profile settings, which NDB does not universally enforce).

Other options are incorrect:

B. The language settings match workstation regional settings: This would depend on the OS locale, not the observed behavior of reverting to English.

C. The language settings revert to English after logoff: NDB does not reset language settings upon logoff; the issue is device-specific.

D. The language settings are bound to NDB users: If this were true, the language would persist across workstations for the same user, which is not the case here.

Thus, the verified answer is A, reflecting browser-local language management.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.3: User Interface Customization.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.2: Navigate the NDB UI (applicable to v6.10).

Nutanix NDB User Guide: "Customizing Language Settings" section, noting browser dependency.

In the context of Nutanix Era, the term “Brownfield Database” is used to refer to an existing database that is registered with Era1. This process allows Era to bring Database as a Service (DBaaS) capabilities to your existing database2. It’s important to note that before you register a database with Era, certain prerequisites must be met3.

Nutanix Era enables you to clone your source databases and refresh the database clones by using snapshots or transaction logs1. For an online retail application that requires data to be synchronized between multiple SQL Server databases, having all the databases present in the same Database Virtual Machine (DBVM) and registering them in Era with Multiple Databases as a Group with one Time Machine would be the most efficient way to fulfill this requirement1. This approach allows for clearer reporting from multiple databases at the same time for consistency at the end of each business day1.

To free up space in the NDB-managed container, the administrator needs to identify storage consumption sources. Two key locations in NDB provide actionable insights:

C. Clone Database table: This displays all clone databases, including their Size (current storage usage) and Last Refresh (indicating age or staleness). Clones often consume significant space, and older or unused ones can be deleted to reclaim storage.

D. Snapshot table in Time Machine: This shows snapshots with details like Reclaimable Space (space recoverable by deletion) and Age (how long snapshots have existed). Old or unnecessary snapshots are prime candidates for reclamation.

Why not the other options?

A. NDB Dashboard (Clone Data Age): While it provides a high-level view, it lacks granular details (e.g., size per clone) needed for targeted reclamation.

B. Source Database grid: This shows registered databases’ size and status but doesn’t focus on derivative objects (clones/snapshots) that typically consume more space.

Thus, C and D are the best locations for detailed storage analysis and reclamation research.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Storage and Resource Management, Lesson 6.2: Monitoring and Reclaiming Storage.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.1: Manage Storage Consumption (applicable to v6.10).

Nutanix NDB Administration Guide: "Clone Database Table" and "Time Machine Snapshot Table" sections.

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

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

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.

 The database parameters profile is used to define the initialization variables for different types of database engines and workloads, such as OLTP and DW. The database parameters profile allows the database administrator to customize the configuration settings for each database engine, such as Oracle, SQL Server, PostgreSQL, and MySQL. The database parameters profile can also be applied to different database operations, such as provisioning, cloning, and patching. The database parameters profile helps to optimize the performance and functionality of the databases according to the specific requirements and best practices of each database engine and workload.

The software profile version is used to define the software version and edition for each database engine, such as Oracle 19c Enterprise Edition or SQL Server 2019 Standard Edition. The software profile version is required for provisioning new databases and patching existing databases. The software profile version helps to ensure the compatibility and compliance of the databases with the supported software versions and editions.

The network profile is used to define the network configuration and security settings for the database server VMs and the databases, such as the IP address, subnet mask, gateway, DNS, firewall rules, and SSL certificates. The network profile is required for registering new database server VMs and provisioning new databases. The network profile helps to ensure the connectivity and protection of the database server VMs and the databases within the network environment.

The compute profile is used to define the compute resources and storage policies for the database server VMs and the databases, such as the CPU, memory, disk size, disk type, compression, deduplication, and replication factor. The compute profile is required for provisioning new databases and cloning existing databases. The compute profile helps to ensure the availability and efficiency of the database server VMs and the databases within the Nutanix cluster.

References:

Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slides 6-9.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 5-8, 11-12, 15-16.

Option A: On the Era Dashboard Database Summary Table under Source Database. The dashboard provides a summary of the databases, including their sizes1.

Option B: Under the Capacity widget on the Database Server VMS > List database summary page. While this might provide information about the capacity, it does not specifically provide the size of a Source Database.

Option C: On the Databases > Sources table. This table provides detailed information about the databases, including their sizes1.

Option D: On the Profiles > Database Parameters list for the assigned DB Parameter Profile. This list provides parameters for the database but does not provide the size of a Source Database.

Nutanix Era leverages the Nutanix time-efficient snapshots to create the clones1. These database clones are highly space-efficient, consuming near-zero bytes by having only the further writes constituting to its size1. Therefore, an administrator would find the total space being used by all Era clones for a specific database under the Cloning widget on the Databases > Clones database summary page. The other options do not specifically provide information about the total space used by all Era clones for a specific database. Therefore, the correct answer is A. Under the Cloning widget on the Databases > Clones database summary page.

 Nutanix Database Automation (NCP-DB) introduces the concept of MS SQL Server database groups, which allows multiple databases running in the same database instance to be grouped as one Time Machine entity1. This applies to both single DB Server VM setups, standalone databases, as well as to Availability Group databases1. However, it does not support Point In Time Recovery (PITR)-based Service Level Agreements (SLAs) for database groups containing mixed Recovery Models. This means that if the databases within the group have different recovery models, PITR-based SLAs cannot be applied to the group as a whole.

To register an Oracle Database Server VM to Era in Nutanix Database Automation (NCP-DB), certain dependencies must be met. One of these is that SUDO NOPASS access is required1. This allows the Era service to perform necessary operations on the Oracle Database Server VM. As for assigning a static IP address to the Era VM on ESXi, you can use the vSphere Client to configure static IP settings2. However, this is not directly related to the registration of an Oracle Database Server VM to Era. Please note that these answers are based on the information available as of my last update in 2021 and may need to be verified with the most recent Nutanix Database Automation (NCP-DB) documentation or resources.

The Nutanix Era Time Machine provides various capabilities depending on the Service Level Agreement (SLA) selected during database registration1. For a database with a Bronze SLA, the Time Machine supports both “Log Catch up” and "Snapshots"2. “Log Catch up” allows the Time Machine to keep up with the latest changes in the database by capturing log data2. “Snapshots” are point-in-time copies of the database that can be used for recovery or cloning2.

To allow a non-administrative NDB user to provision an Oracle database using a Software Profile created by an administrator, the administrator must promote the Software Profile to Published. In NDB, Software Profiles define the database software version and configuration (e.g., Oracle binaries). By default, a newly created profile is in a draft or private state. Promoting it to "Published" makes it available for use by other NDB users, including non-administrative ones, within the access control framework. This ensures the profile is validated and accessible without requiring individual user assignments.

Other options are incorrect:

A. Ensure that specified users have access to the Software Profile using Access Control: Access Control manages user permissions but does not make the profile available unless it is published.

B. Replicate the Software Profile to other Nutanix clusters: Replication is for HA or disaster recovery, not user access.

C. Ensure that the Software Profile has been properly versioned to the latest release of Oracle: Versioning ensures compatibility but does not grant user access.

Thus, the verified answer is D, aligning with NDB’s profile management workflow.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Managing Software Profiles.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Configure Software Profiles (applicable to v6.10).

Nutanix NDB Administration Guide: "Publishing Software Profiles" section.

According to the Nutanix Database Automation (NCP-DB) learning documents, Era provides out-of-band patching of databases to eliminate database configuration sprawl1. The two Oracle software components that Era patches are:

A. Grid home2 B. Oracle home2

These components are crucial for the operation of Oracle databases and keeping them updated ensures data security and efficient validation of critical database updates1. Please refer to the official Nutanix documentation and training materials for more detailed information2.

When a database is de-registered from NDB without removing the associated Time Machine, the Time Machine enters a "Frozen" state. In this state, the Time Machine retains all existing snapshots and protection data but ceases to perform new snapshot captures or log catch-up operations. This allows the administrator to preserve the historical data for potential future use (e.g., auditing or recovery) while halting active management. The Frozen state prevents further modifications until the database is re-registered or the Time Machine is explicitly deleted.

Option A (Ready) is incorrect because "Ready" implies the Time Machine is active and prepared for new operations, which is not the case post-de-registration.

Option B (Frozen) is correct as it reflects the paused protection state after de-registration without removal.

Option C (Paused) is incorrect because "Paused" is not a formal Time Machine state in NDB; "Frozen" is the specific term.

Option D (Active) is incorrect because the Time Machine cannot remain active without an associated registered database.

This state provides flexibility for data retention without ongoing resource use.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Time Machine States

Nutanix Support & Insights, Knowledge Base Article: "Understanding Time Machine States After De-registration"

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

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 NDB, a Time Machine manages snapshots and log catch-up operations for database protection and recovery. The scenario describes a Time Machine where automatic snapshot and log catch-up activities (both automatic and manual) are halted, and manual snapshots cannot be created. This indicates the Time Machine is in a PAUSED state.

In NDB, the Time Machine states are:

FROZEN: A temporary state during specific operations (e.g., cloning), but it doesn’t halt all activities permanently.

OFFLINE: Indicates the Time Machine is unavailable or not operational, often due to connectivity or configuration issues, but this typically prevents access rather than just halting operations.

PAUSED: Explicitly stops all scheduled and manual snapshot/log activities, often manually triggered by an administrator or due to an error condition (e.g., resource constraints). Operations resume when unpaused.

READY: The normal operational state where snapshots and log catch-ups occur as scheduled.

Given the inability to create manual snapshots alongside halted automatic operations, PAUSED is the most fitting status, as it reflects an intentional or enforced suspension of activities.

Official Nutanix Database Automation References

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

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Time Machine States (applicable to v6.10).

Nutanix NDB Administration Guide: "Time Machine Statuses and Operations" section.

To register a PostgreSQL database server VM with a database on NDB, the database data and log files must be located on a separate mount point from the operating system and the binary installation. This is because NDB uses the mount point as the identifier for the database server VM and the database. If the data and log files are on the same mount point as the operating system or the binary installation, NDB will not be able to recognize them as a valid database server VM or database. Therefore, the administrator should create a separate mount point for the data and log files and specify it during the registration process. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [How to Allow Remote Access to PostgreSQL database], [5 Ways to Host PostgreSQL Databases], [Starting the Database Server].

The Database Agent is used to temporarily store the transaction logs of the source database before they are copied to the log. This is a critical component for ensuring data consistency and recovery in database operations.References: Nutanix Database Automation documentation, focusing on database agents and their roles in transaction log management.

A Log Catchup gap in Nutanix Database Service (NDB) occurs when transaction logs are missing or corrupted, disrupting point-in-time restore (PITR) operations for cloning or database restoration via Time Machine. The NDB Time Machine Heal Snapshot feature addresses this by repairing snapshots to resolve such gaps.

Option A (By default the time machine auto-heal feature is enabled) is incorrect because the auto-heal feature is not enabled by default; it requires explicit configuration or manual invocation.

Option B (Manual Heal is only used when gaps in Log Catchup are detected once the operation has begun failing) is incorrect because manual heal can be initiated proactively or reactively, not solely after failure detection.

Option C is correct because a successful Time Machine Heal process restores the snapshot integrity, allowing PITR to span the previously gapped period.

Option D is correct as the auto-heal process, when enabled, runs every 5 minutes to detect and address healable conditions, aligning with NDB’s automated maintenance schedule.

Together, C and D reflect the operational mechanics of the Heal Snapshot feature.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Healing Snapshot Gaps

Nutanix Support & Insights, Knowledge Base Article: "Resolving Log Catchup Gaps with Time Machine Heal"

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