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

 In Nutanix Era, a  Volume Group  is the recommended storage provisioning method for a large I/O-intensive database that doesn’t support a multi-disk layout 1 .  A Volume Group in Nutanix Era is a collection of disks that can be managed as a single entity, providing a way to aggregate the storage capacity of multiple disks into a larger storage unit 1 .  This allows for better performance optimization as it enables the database to leverage the combined I/O capabilities of all the disks in the group 1 .  It’s important to note that while other options like Load Balancing, Storage Spaces, and vDisk based provisioning can also be used in certain scenarios, a Volume Group is specifically designed for situations where a single, high-performance storage unit is required 1 .

For restoring a database provisioned on Storage Spaces, especially when virtual disks are shared among multiple databases, the supported method is a copy-based restore via the NDB GUI. This method allows for a precise and controlled restoration process suitable for shared storage environments. References: Nutanix Database Automation documentation, specifically in the section on database restoration methods and storage spaces.

Option A : Nutanix Era requires network prerequisites like NTP, DNS servers, gateway, and subnet mask to be available and visible.  These are essential for the proper functioning of the Era instance 1 .

Option B : One static IP address must be available and can be changed using CLI after VM deployment.  This is necessary for the Era VM to communicate with other components in the network 1 .

Option C : While a storage container is necessary for Nutanix infrastructure, it is not a network prerequisite specifically for deploying an Era instance.

Option D : An SMTP server and details are typically used for sending notifications, but they are not a network prerequisite for deploying an Era instance. They are more related to the operational aspect post-deployment.

According to the Nutanix Database Automation (NCP-DB) course, the ports 3205 and 3260 are required for iSCSI connections between the NDB server and the Controller VMs 1 .  Port 3205 is used for the NDB iSCSI initiator service, which initiates the iSCSI sessions and sends SCSI commands to the Controller VMs 1 .  Port 3260 is used for the iSCSI target service, which listens for incoming iSCSI requests and provides access to the storage devices on the Controller VMs 1 . The other options are not related to iSCSI connections.  Port 22 is used for SSH, port 9440 is used for Prism Central, port 80 is used for HTTP, port 443 is used for HTTPS, port 5985 is used for WinRM HTTP, and port 5986 is used for WinRM HTTPS 2 .  References :

1 : Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.2: Database Engine Installation, slide 13

2 : Nutanix NCP-DB Certification Exam Sample Questions, Question 18,  Answer

Time Machine data access is a feature of Nutanix Database Service (NDB) that allows you to access a point-in-time snapshot of a database without restoring it. To use this feature, you need to create a Data Access Management (DAM) policy that defines the access mode, the source database, the destination cluster, and the storage container mapping. The storage container mapping is needed when the source database and the NDB Server containers are different, because NDB needs to know where to store the metadata and the clone of the source database. If the source database and the NDB Server containers are the same, then NDB will use the same container for both the metadata and the clone.  References :

Nutanix Certified Professional - Database Automation (NCP-DB) , Section 5 - Protect NDB-managed Databases Using Time Machine

Database (NCP-DB) Exam Blueprint Guide - Nutanix , Page 9, Objective 5.6

Nutanix Database Management & Automation (NDMA) course , Module 4, Lesson 4.2 - Data Access Management

When registering a new Nutanix Cluster with Era, the Era Agent is installed on the target Nutanix cluster via the Register Nutanix Cluster workflow 1 .  This agent is crucial for the functioning of the Nutanix Database Service (NDB) as it helps in managing and optimizing database workloads 2 .  It also enables the application of procedural concepts to add Nutanix clusters to NDB 2 .

According to the Nutanix Database Automation (NCP-DB) course, a Software Profile is a template that defines the configuration of the database engine, such as the version, edition, features, and parameters 1 .  It also specifies the disk layout for the database installation, such as the size, type, and mount point of each disk 1 .  However, the System Page File disk is omitted from the Software Profile, as it is automatically created by the NDB service based on the memory size of the database server VM 1 .  The other options are included in the Software Profile, as they are essential for the database operation and performance 1 .  References :

1 : Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.3: Software Profiles, slide 5

To create an NDB Software Profile Version for PostgreSQL, it is required to have an installer package for the database software. This package forms the basis of the software profile, enabling the deployment and management of PostgreSQL instances. References: Nutanix Database Automation documentation, particularly in the area of software profile creation and management for PostgreSQL.

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

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

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

Nutanix Era allows custom metadata to be assigned to entities (clones, time machines, databases, and database servers) by using  Tags .  Tags are a component of Nutanix Era that allows users to assign custom metadata to various entities, enhancing the ability to organize, search, and manage these entities within the Era platform 1 .

To create a software profile version for a newly-released Oracle ISc patch, an administrator should follow these steps:

Download the required patch from MyOracle Support 1 . This is because Oracle patches are typically available from MyOracle Support, not Microsoft Support.

Apply the patch to the Oracle Home/Grid Home on a cloned VM of the gold image using OPatchAuto 1 . OPatchAuto is a utility provided by Oracle that automates the process of applying patches to a database.

Ensure success of patch application 1 . It’s important to verify that the patch has been applied successfully to avoid any issues down the line.

Create a new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era GUI 1 . This step is necessary to ensure that the new patch is included in the software profile.

Mark the original patch profile as hidden 1 . This step is optional but can be useful for keeping the software profile clean and organized.

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.

When completing the NDB (Nutanix Database Service) Wizard for initial setup or configuration, certain steps are mandatory to ensure the environment is properly configured, while others are optional based on specific needs. Network Segmentation is an optional step that allows for advanced network isolation and configuration, but it is not required for basic NDB deployment. Mandatory steps include specifying the NDB Cluster Name, selecting a Storage Container, and configuring Services (e.g., database services), as these are essential for NDB to function and manage databases.

Option A (Network Segmentation) is correct as it is an optional feature for advanced networking, not a required step in the wizard.

Option B (NDB Cluster Name) is incorrect because assigning a cluster name is a mandatory step to identify the NDB instance.

Option C (Storage Container) is incorrect because selecting a storage container is required for data storage and protection.

Option D (Services) is incorrect because configuring services (e.g., database engines) is a core requirement for NDB operation.

Note: The question mentions " NDE Wizard, " which is assumed to be a typo for " NDB Wizard " based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Deploying NDB, Section: Completing the NDB Wizard

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 1: Deploy NDB

 Nutanix Era enables you to clone your source databases (running on Nutanix clusters) and refresh the database clones by using snapshots or transaction logs 1 .  Era uses storage-efficient and time-efficient Nutanix snapshots, thus lowering the cost of managing multiple copies of your databases 1 .  In this case, the administrator should create a clone from the July 31st snapshot in Time Machine to provide the legal team with the specific banking transaction event data they need for their audit 1 .

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) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.4: Migrate Databases (applicable to v6.10).

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

In Nutanix Database Service (NDB), a Network Profile is used to define networking configurations for database VMs, including VLAN assignments and IP address ranges. The correct procedure to create a Network Profile that assigns a VLAN and provides IP addresses to a database VM is as follows:

Create Network Profile : Start by initiating the creation of a new Network Profile within NDB. This is done from the NDB interface under the " Network " or " Profiles " section.

Select the VLAN : During the Network Profile creation process, you specify the VLAN that the database VM will use. This involves selecting an existing VLAN configured in the Nutanix cluster (e.g., via Prism Element) or defining a new VLAN ID if applicable.

Define IP Range : Finally, you define the IP address range (e.g., a subnet or specific IPs) that will be assigned to the database VM(s) within the selected VLAN. This ensures the VM receives a valid IP address for communication.

The sequence in option B aligns with the NDB workflow, where the Network Profile is created first, followed by associating it with a VLAN and then defining the IP allocation. Other options are incorrect:

A : " Add the VLAN " is vague and does not specify where the VLAN is added, disrupting the logical flow.

C : Adding a VLAN before creating the profile is not the standard NDB process, as VLANs are associated during profile creation.

D : Defining an IP range before creating the profile is out of sequence, as the profile must exist to hold the configuration.

Thus, the verified answer is B. Create Network Profile, Select the VLAN, Define IP Range .

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.2: Configuring Network Profiles.

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

Nutanix NDB Administration Guide: " Network Profiles " section, detailing VLAN and IP configuration steps.

 NDB supports two modes of log backup management for Microsoft SQL databases: NDB-managed and 3rd-party managed. In the NDB-managed mode, NDB takes full control of the log backups and stores them in the Cerebro log location. In the 3rd-party managed mode, NDB allows the use of external backup tools to backup the logs from the database log destination. However, NDB still needs to capture the logs for its own operations, such as point-in-time recovery, clone refresh, and log catch-up. Therefore, NDB will periodically scan the database log destination and copy the logs to the Cerebro log location. This process requires that the log catch-up begins before the logs get backed up by the 3rd-party tool, otherwise NDB will miss some logs and the operations will fail. If the 3rd-party tool grants exclusive access to the logs, then NDB will not be able to capture them at all, and the operations will not be supported.  References :

Nutanix Database Management & Automation (NDMA) course , Module 5, Lesson 5.2 - Log Backup Management

Nutanix Support & Insights , Nutanix NDB User Guide v2.5, Log Backup Management

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 role 1 . The default roles available within Era for Role-Based Access Control are:

prism Admin

Era Super Admin

Era Database Admin

Era Infrastructure Admin 1  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 on 1 .

When an administrator creates a new SQL Server software profile version to apply the latest cumulative update, they should update the software profile version and set the status to Published 1 . This makes the new profile version available to all users.  NDB will show available updates for any database server using the software profile as soon as the new profile version is published 1 .

 The correct answer is D because it matches the requirement of taking multiple snapshots per day and retaining them for one week. Option A is incorrect because it only takes one snapshot per day, which is not enough for the administrator’s need. Option B is incorrect because it only retains the snapshots for one week, which means the older snapshots will be deleted after seven days. Option C is incorrect because it only takes two snapshots per week, which is not frequent enough for the administrator’s need.

References : The following sources provide more information about the SLA retention policies and how to create and modify them in NDB:

Nutanix Database Management & Automation (NDMA) course , Module 4: Protecting Databases Using Time Machine, Lesson 4.1: Creating and Modifying SLA Retention Policies

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 , Knowledge Objectives, Section 5 - Protect NDB-managed Databases Using Time Machine

Nutanix Database Service (NDB) User Guide , Chapter 6: Protecting Databases Using Time Machine, Section 6.1: Creating and Modifying SLA Retention Policies

 The correct answer is B and D because they are the two restore options that can be used to restore an Oracle database to the prior day’s state using Nutanix Era. A snapshot is a point-in-time copy of a database that is stored in the Era Time Machine, which is a distributed file system that collects logs and snapshots from databases. A point in time is a specific moment in time within the retention period of the SLA policy that is applied to the database. By using either of these options, the administrator can select the snapshot or the point in time that corresponds to the prior day’s state and restore the database from it. The other options are not correct because they are not restore options that are available in Nutanix Era. Option A is not correct because Most Recent Time Available is not a restore option, but a clone option that creates a clone of the database from the most recent snapshot or log backup. Option C is not correct because Tail Logs Backup is not a restore option, but a backup option that captures the transaction logs of the database that have not been backed up by the SLA policy.  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 Database Services: Database modernization with Era - Now available]

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

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 practices 1 .  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 process 1 .  This ensures optimal performance and reliability of the restored database 1 .

The exhibit shows an error during the provisioning of NDB from the Prism Central Marketplace, with a failure reason stating " IP not found " in the " EraService - Substrate Create " step. This indicates that the provisioning process could not assign or detect an IP address for the NDB instance, likely due to an unconfigured or missing IP address during deployment. To prevent this issue, the administrator should configure an IP address when deploying the application . This involves specifying a static IP or ensuring IP Address Management (IPAM) is properly set up to allocate an IP during the Prism Central Marketplace deployment wizard.

Other options are less directly relevant:

B. Import the proper image in the Prism Central : This ensures the correct NDB image is available but does not address the IP assignment issue.

C. Provide a subnet with IP Address Management : While useful, this is a broader configuration step and not the specific action needed during deployment.

D. Register NDB using the correct IP address : Registration occurs after deployment and does not prevent the initial IP assignment failure.

Thus, the verified answer is A , as configuring the IP address during deployment directly addresses the " IP not found " error.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.2: Deploying NDB from Prism Central.

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

Nutanix NDB Installation Guide: " Deploying NDB via Prism Central Marketplace " section, emphasizing IP configuration.

A Network Profile is a collection of network settings that are used to provision database server VMs in NDB. A Network Profile can include one or more VLANs, IP ranges, and DNS servers. To make new VLANs available when provisioning an Oracle cluster database, you need to update the Network Profile to include the new VLANs. You can do this by editing the existing Network Profile or creating a new one with the new VLANs.  You do not need to create or update the VLANs in Prism Element, as NDB can discover the VLANs configured in AHV 1 .  References :

Nutanix Database Management & Automation (NDMA) course , Module 2, Lesson 2.4 - Network Profiles

Nutanix Support & Insights , Nutanix NDB User Guide v2.5, Network Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) , Section 2 - Deploy and Configure an NDB Solution

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

Other options are incorrect:

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

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

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

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

Official Nutanix Database Automation References

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

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

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

In the Nutanix Era management interface, an administrator should perform an upgrade under the  Administration > Maintenance  section 1 .  As part of the upgrade process, the Era server is upgraded first, followed by all the Era cluster agents and database server agents in parallel 1 .  The Dashboard displays the current version and an option to upgrade the Era server to a latest version when a new version is available for upgrade 1 .  This ensures that the Nutanix Era environment is always up-to-date with the latest features and security updates 1 .

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 Clone 1 2 .  This process allows the administrator to create a copy of the source database at a specific point in time 1 .

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) v6.5 Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v6.10).

Nutanix NDB Administration Guide: " Configuring Network Profiles for Multi-Cluster HA " section.

 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

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.

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.

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

The administrator should perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, to accomplish the task of patching a MongoDB server cluster within an NDB environment. A rolling upgrade is a method of applying patches or updates to a cluster without downtime or interruption of service. The administrator can use the NDB patching feature to perform a rolling upgrade on a MongoDB server cluster, which consists of a primary member and one or more secondary members that form a replica set. The NDB patching feature allows the administrator to select the software profile version, the database parameters profile, and the network profile for the patching operation. The NDB patching feature also automates the steps of the rolling upgrade, such as:

Step 1: The administrator initiates the patching operation on the NDB instance, and selects the MongoDB server cluster to be patched.

Step 2: The NDB instance verifies the prerequisites and compatibility of the patching operation, and creates a pre-patch snapshot of the MongoDB server cluster.

Step 3: The NDB instance applies the patch to the first secondary member of the MongoDB server cluster, and waits for the patching to complete successfully.

Step 4: The NDB instance verifies the status and functionality of the patched secondary member, and repeats the patching process for the remaining secondary members of the MongoDB server cluster, one at a time.

Step 5: The NDB instance performs a failover of the primary member to one of the patched secondary members, and applies the patch to the original primary member.

Step 6: The NDB instance verifies the status and functionality of the patched primary member, and performs a failback of the primary member to the original primary member, if desired.

Step 7: The NDB instance creates a post-patch snapshot of the MongoDB server cluster, and completes the patching operation.

Performing a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, is the recommended and best practice method of patching a MongoDB server cluster within an NDB environment, as it ensures the high availability, consistency, and performance of the MongoDB server cluster and the databases.

Performing a rolling upgrade, applying the patch to the primary member first, followed by the secondary members, is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to the primary member first would disrupt the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to restore the MongoDB server cluster to a functional state.

Applying the patch to all nodes at once is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to all nodes at once would require shutting down the entire MongoDB server cluster, and would expose the MongoDB server cluster and the databases to potential errors, failures, and corruption during the patching process.

Disabling the replica set while patching is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Disabling the replica set while patching would break the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to re-enable the replica set and restore the MongoDB server cluster to a functional state.

References :

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

Nutanix Database Management & Automation Training Course , Module 5: Nutanix Era Operations, Lesson 5.3: Nutanix Era Patching, slides 5-9.

Nutanix Database Management & Automation Training Course , Module 5: Nutanix Era Operations, Lesson 5.4: Nutanix Era Patching Lab, slides 5-10.

Nutanix Database Management & Automation Training Course , Module 7: Nutanix Era Troubleshooting, Lesson 7.1: Nutanix Era Troubleshooting, slide 6.

This is because it allows the database to be refreshed at the exact time specified (9:30 PM) with the most recent data. The other options either perform the snapshot before the desired time or do not specify when the snapshot would occur. Please note that the exact answer might depend on the specific database system and its capabilities. Always refer to the database’s documentation for the most accurate information.

To apply patches to Microsoft SQL Server databases in an NDB environment, the administrator should follow a structured process:

Create a new software profile version : Download the latest cumulative update (CU) or patch from Microsoft and use it to create a new version of the existing SQL Server Software Profile in NDB. This ensures the patch is integrated into NDB’s management framework.

Publish the updated software profile : Promote the new version to " Published " status, making it available for use across the environment.

Apply the update : Navigate to the " Database VM Menu " for each database server, select the updated software profile, and apply the patch. This automates the patching process while maintaining database consistency and allowing rollback if needed.

Other options are incorrect or incomplete:

A. Create a Maintenance window schedule and associate the SQL server with that maintenance window in the Database VM Menu : Maintenance windows manage downtime, not patch application for databases.

B. Apply the patch to the database VM then create a new software profile using that updated VM as the source : This manual approach bypasses NDB’s structured patching and lacks version control.

C. Apply the patch to the database VM, then create a new software profile version using that updated database VM as the source, publish the updated software profile then apply that patch under the database VM Menu for each database server : This is overly complex and risky, as manually patching a VM first can lead to inconsistencies.

Thus, the verified answer is D , aligning with NDB’s best practices for database patching.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.2: Patching SQL Server Databases.

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

Nutanix NDB Administration Guide: " Patching Microsoft SQL Server " section.

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

To provision a PostgreSQL HA instance from a software profile created from a VM with services like etcd, HAProxy, Patroni, and keepalived installed, the administrator must ensure the instance aligns with NDB’s HA framework. These services (e.g., Patroni for PostgreSQL HA management, HAProxy for load balancing) may conflict with NDB’s built-in HA mechanisms. Provisioning an HA instance with these services disabled allows NDB to manage HA using its native replication and failover capabilities (e.g., streaming replication), avoiding duplication or interference from the VM’s pre-installed services.

Option A (Provision an HA instance with the services enabled) is incorrect because enabling these services may cause conflicts with NDB’s HA management.

Option B (Disable the services, create a software profile version, and provision an HA instance) is incorrect because disabling services and recreating a profile is unnecessary; the provisioning step can handle service configuration.

Option C (Provision an HA instance with the services disabled) is correct as it ensures NDB’s HA features take precedence without interference.

Option D (Enable the services, create a software profile version, and provision an HA instance) is incorrect due to potential conflicts with NDB’s HA implementation.

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

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

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

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

When an administrator needs to scale the size of an Oracle database running on Nutanix NDB and originally configured using ASMLib (Automatic Storage Management Library), the most efficient approach is to use NDB’s built-in scaling ability to resize existing vDisks. NDB supports dynamic resizing of virtual disks (vDisks) associated with database VMs, allowing the administrator to increase storage capacity without disrupting the database or requiring complex migrations. This method leverages Nutanix’s storage integration, resizing the underlying vDisks and updating the ASMLib configuration to reflect the new size, ensuring seamless operation.

Option A (Leverage the scaling ability built into NDB to resize existing vDisks) is correct as it is the most efficient, native NDB feature for scaling storage.

Option B (Extend the size by adding new vDisks) is incorrect because adding new vDisks requires additional configuration (e.g., ASM disk group adjustments), making it less efficient than resizing.

Option C (Create a new, larger database and migrate) is incorrect because migration is time-consuming and unnecessary when resizing is supported.

Option D (Mount an iSCSI LUN and extend the database onto the new LUN) is incorrect because iSCSI LUNs are not the preferred method in NDB, and resizing vDisks is more integrated.

This approach minimizes downtime and complexity.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Scaling Storage for Databases

Nutanix Support & Insights, Knowledge Base Article: " Resizing vDisks for Oracle Databases in NDB "

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

The provided exhibit shows the NDB Time Machine restore interface for October 31, 2024, with a Point-in-Time (PIT) restore option selected at 21:50. However, the restore option is unavailable, as indicated by the question. The exhibit includes a warning: " Logs to Backup: The database may contain additional logs. Backup any remaining logs before restore or they will be lost. " This suggests that PIT restore requires continuous log retention, and if logs since the last snapshot (at 01:10:00) are not backed up, the restore to 21:50 cannot proceed. Running the " Logs to Backup " operation ensures all transaction logs are captured, enabling PIT restore by allowing NDB to replay logs to the desired point.

Option A (Point in time must be within the most recent range) is incorrect because the selected 21:50 is within the log retention period shown (up to the current time), but logs need to be backed up.

Option B (Selected Restore time is not available) is incorrect because 21:50 is a valid time within the log range, but log backup is the issue.

Option C (Change to snapshot option) is incorrect because switching to a snapshot limits the restore to the snapshot time (01:10:00), not 21:50.

Option D (Logs to Backup must be run first) is correct as the warning indicates that backing up remaining logs is necessary for PIT restore.

After running the backup, the administrator can proceed with the PIT restore.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Point-in-Time Restore Requirements

Nutanix Support & Insights, Knowledge Base Article: " Troubleshooting PIT Restore Issues in NDB "

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

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

A.  Grid home 2  B.  Oracle home 2

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

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.

In this scenario, a PostgreSQL instance managed by NDB on a Linux VM is malfunctioning after a manual OS update, and a new Linux DB server VM has been prepared to host the data. To migrate the data to the new VM, the administrator must integrate the new VM into NDB’s management framework. The correct action is to register the new DB Server VM in NDB , which allows NDB to recognize and manage the VM as a database server. Once registered, the administrator can use NDB’s features (e.g., cloning, restoring, or reprovisioning) to migrate the data from the broken instance to the new VM.

Here’s why the other options are incorrect:

A. Provision a new PostgreSQL instance from the Databases page : This creates a fresh instance without migrating existing data, losing the broken instance’s data unless separately restored.

B. From The Machine policy, Authorize Database Server VMs : Machine policies in NDB define rules for VM management, but authorizing VMs is not a direct migration action and assumes prior registration.

C. Follow the Provision a PostgreSQL Instance wizard : Similar to A, this provisions a new instance rather than migrating data to an existing prepared VM.

Registering the new VM in NDB (via the " Database Server VMs " section) enables the administrator to associate it with the existing PostgreSQL instance’s configuration and perform a data migration (e.g., using a snapshot or backup). This aligns with NDB’s workflow for replacing a broken server. Thus, the verified answer is D .

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.3: Registering and Managing Database Server VMs.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.2: Register and Manage DB Server VMs (applicable to v6.10).

Nutanix NDB Administration Guide: " Registering a Database Server VM " section.

 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”

To apply the latest OS security patches on a Windows server managed by NDB, the user should create and apply a Maintenance Plan within the NDB interface. NDB provides a Maintenance Plan feature that allows administrators to schedule and automate OS patching for database server VMs, ensuring patches are applied in a controlled manner without disrupting database operations. This includes validating the patch process, rolling back if needed, and maintaining compliance with security standards. The plan can be configured to target the specific Windows server and include the latest security updates from Microsoft.

Other options are incorrect or insufficient:

A. Reboot the system : A reboot alone does not apply patches; it may only activate previously installed updates.

C. Update the database : This focuses on database software, not OS security patches.

D. Use update functionality directly on the VM : Manual updates bypass NDB’s control, risking inconsistency and potential downtime without proper validation.

Thus, the verified answer is B , leveraging NDB’s centralized maintenance capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.3: Creating Maintenance Plans.

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

Nutanix NDB Administration Guide: " Maintenance Plans for OS Patching " section.

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

 Before patching a Linux OS on a database server VM provisioned using NDB, you must configure the repository for the OS updates. This can be done by creating a Repository Profile in NDB and specifying the URL, username, and password for the repository. The Repository Profile can be applied to one or more database server VMs during the provisioning process or later. By configuring the repository, you ensure that NDB can access and download the latest OS patches from a trusted source.  References :  Nutanix Database Automation (NCP-DB) Course Details ,  Nutanix Database Automation (NCP-DB) Certification Details ,  Nutanix Database Automation (NCP-DB) YouTube Playlist ,  Nutanix Database Automation User Guide .

The correct answer is B because the Time Machine feature of NDB collects logs and snapshots from databases and stores them in a distributed file system. The Time Machine enables the administrator to protect, clone, and restore databases using the SLA policies and the NDB UI or API. The Time Machine also manages the replication of database snapshots in an NDB multicluster environment. The other options are not correct because they describe different features or functions of NDB. Option A is not correct because Database Restore is an operation that uses the Time Machine to restore a source database or a clone to a previous point in time. Option C is not correct because SLA is a policy that defines the frequency and retention of database snapshots and logs. Option D is not correct because One-click Patching is a feature that allows the administrator to test, publish, and apply database patches using the NDB UI or API.  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

The correct answer is A because the Windows Domain profile is the profile that includes information related to the SQL service startup account and the NDB worker service account. A Windows Domain profile is a collection of settings that define how NDB manages Windows-based database servers and databases. It contains the following information:

The domain name and credentials to join the database server VMs to the domain

The SQL service startup account and password to run the SQL Server service on the database server VMs

The NDB worker service account and password to run the NDB Database Agent service on the database server VMs

The SQL Server authentication mode to use for the databases

By using a Windows Domain profile, the administrator can simplify the database provisioning process by applying the same settings to multiple database server VMs and databases, without having to manually enter them each time. The other options are not correct because they describe different types of profiles that do not include information related to the SQL service startup account and the NDB worker service account. Option B is not correct because the Network profile is a profile that defines the network settings for the database server VMs, such as the IP address, subnet mask, gateway, DNS, and VLAN. Option C is not correct because the Database Parameter profile is a profile that defines the database parameters for the databases, such as the memory, CPU, storage, and performance settings. Option D is not correct because the Software profile is a profile that defines the software settings for the database server VMs and databases, such as the database engine version, edition, and features.  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 Database Services: Database modernization with Era - Now available

NDB supports Linux OS patching for database server VMs. Linux OS patching is performed by using the yum or apt package managers, depending on the Linux distribution. To exclude Kernel patches for the Linux OS, the administrator can disable or exclude the appropriate repositories on the VM prior to patching. This can be done by editing the yum.conf or apt.conf files, or by using the --disablerepo or --exclude options in the yum or apt commands. This way, the administrator can control which patches are applied to the VM without affecting other VMs or requiring additional scripts or reboots.

References :

Nutanix Database Automation (NCP-DB) Course Details , Section 4.2: NDB Linux OS Patching

Nutanix Database Automation (NCP-DB) Certification Details , Objective 4.2: Perform Linux OS Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist , Video 4.2: NDB Linux OS Patching

Nutanix Database Automation (NCP-DB) User Guide , Section 4.5: Patch Linux OS Software

During an NDB upgrade, the upgrade process follows a specific order to maintain stability and HA. The Leader NDB API Server is upgraded first. This server coordinates API requests and ensures the control plane remains operational. Upgrading the leader first minimizes disruption, as subsequent components (e.g., other API servers, HAProxy) rely on its leadership role. Once the leader is upgraded, the remaining NDB HA control plane VMs (e.g., follower API servers, HAProxy) are updated in sequence.

Other options are incorrect:

A. NDB Server : Refers to the main NDB instance, not upgraded first.

C. Leader HAProxy : Upgraded after API servers to maintain load balancing.

D. NDB Agent VMs : Upgraded last, as they are client-side components.

Thus, the verified answer is B , reflecting the upgrade sequence.

Official Nutanix Database Automation References

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

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: " NDB Upgrade Process " section.

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) v6.5 Blueprint, Section 4: Manage Database Software Profiles

The exhibit shows the configuration of unencrypted Active Directory (AD) access in NDB, with the " Primary URL " set to ldap:// (indicating LDAP rather than LDAPS). Unencrypted LDAP communication uses port 389 by default. For NDB to communicate with Active Directory, this port must be allowed through the firewall to enable the NDB server to perform authentication and directory lookups using the specified service account (e.g., administrator).

Other options are incorrect in this context:

B. 636 : This is the default port for LDAPS (LDAP over SSL/TLS), which is encrypted and not applicable since the configuration uses unencrypted LDAP.

C. 2009 : This is not a standard port for LDAP or AD communication and is unrelated to NDB’s AD integration.

D. 9440 : This is associated with Prism Element’s HTTPS management interface, not AD access.

Thus, the verified answer is A. 389 , ensuring unencrypted LDAP communication between NDB and Active Directory.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.5: Configuring Active Directory Integration.

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

Nutanix NDB Administration Guide: " Active Directory Integration " section, detailing LDAP port requirements.

According to the NDB documentation, the NDB patching process for MongoDB Server Cluster follows these steps 1 :

NDB identifies the primary member of the MongoDB Server Cluster and patches it first.

NDB triggers a failover to elect a new primary member from the remaining secondary members.

NDB patches the former primary member, which becomes a secondary member after the failover.

NDB patches the remaining secondary members one by one.

NDB verifies the patching status and the cluster health.

This process ensures that the MongoDB Server Cluster always has a primary member available to handle write operations, while minimizing the downtime and the impact on the cluster performance.

References :  Nutanix Support & Insights , section “Patching a MongoDB Server Cluster”

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

Other options are incorrect:

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

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

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

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

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: " Configuring SMTP for Alerts " section.

 Nutanix Era supports a variety of database engines, including Oracle, PostgreSQL, MySQL, and Microsoft SQL Server 1 .  However, when it comes to rolling back a patch using the Command Line Interface (CLI), this feature is specifically supported for the Oracle database engine 1 .  This allows for efficient validation of critical database updates and simplifies database rollback 1 .  Please note that while Era does provide support for other database engines, the ability to rollback a patch using CLI is currently specific to Oracle 1 .

To reset the NDB GUI password in Nutanix Database Service (NDB), an administrator must access the system through an SSH session and use the appropriate command-line interface (CLI) tools provided by NDB. The correct process involves entering the era-server CLI, which is the specific CLI environment for managing NDB-related configurations, including security settings like password resets. Once in the era- server CLI, the administrator executes the security password reset command to initiate the password reset process for the NDB GUI. This method ensures that the reset is performed within the NDB-managed environment securely and aligns with Nutanix’s recommended administrative procedures.

Option A is correct because it specifies the era-server CLI and the exact command security password reset, which are consistent with NDB’s administrative tools for managing GUI access credentials.

Option B (sudo passwd era) is incorrect because era is not a system user account in the context of NDB’s Linux-based control plane; this command pertains to standard Linux user management, not NDB-specific GUI password resets.

Option C (sudo passwd admin) is also incorrect as admin refers to a generic user that may not correspond to the NDB GUI account, and this approach bypasses NDB’s internal security mechanisms.

Option D is incorrect due to a typo (era CLI instead of era-server CLI), which renders it imprecise despite the intent being similar to Option A.

This process assumes the administrator has SSH access to the NDB control plane VM and the necessary privileges to execute these commands.

References

Nutanix Database Service (NDB) User Guide, Section: Administering an NDB Environment, Subsection: Managing Access Controls and Password Resets

Nutanix Support & Insights, Knowledge Base Article: " Resetting NDB GUI Password via CLI "

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

Page files are temporary files that Windows uses to store data that does not fit in the physical memory. Page files can interfere with the registration of a database server VM with NDB, as they can cause errors or performance issues. Therefore, page files should be located in a separate drive or partition from the C:\ drive, where the NDB agent and other files are installed. System, database, and backup files do not prevent the registration of a database server VM with NDB, as long as they are not corrupted or incompatible with the NDB requirements.  References :

Nutanix Database Management & Automation Training Course , Module 2: Deploying and Configuring an NDB Solution, Lesson 2: Configuring an NDB Instance, Slide 13: Registering Database Server VMs

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam , Section 4: Operate and Maintain an NDB Environment, Objective 4.1: Apply procedural concepts to register database server VMs and databases

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

The recovery plans policy defines the Time Machine data availability across multiple registered clusters in NDB. The recovery plans policy allows the database administrator to specify the source and target clusters, the frequency and retention of the cross-cluster snapshots, and the network and compute profiles for the recovery operations. The recovery plans policy helps to ensure the disaster recovery and business continuity of the NDB-managed databases in case of a cluster failure or outage.

The data access management policy defines the access permissions and roles for the NDB users and groups. The data access management policy allows the database administrator to grant or revoke access to the NDB instance, the database server VMs, the databases, and the database operations. The data access management policy helps to ensure the security and compliance of the NDB-managed databases and users.

The data protection policy defines the backup and restore settings for the NDB-managed databases. The data protection policy allows the database administrator to specify the frequency, retention, and compression of the database snapshots, and the backup location and encryption for the database backups. The data protection policy helps to ensure the backup and recovery of the NDB-managed databases within the same cluster.

The service level agreements policy defines the performance and availability metrics for the NDB-managed databases. The service level agreements policy allows the database administrator to monitor and enforce the database uptime, latency, throughput, and IOPS. The service level agreements policy helps to ensure the quality of service and performance of the NDB-managed databases.

References :

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

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

Nutanix Database Management & Automation Training Course , Module 6: Nutanix Era Disaster Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 5-7.

 In the context of Nutanix Database Automation (NCP-DB), a Super Admin has the authority to apply patch profiles. However, if a patch is marked as deprecated, even if it’s published, it cannot be applied.  This is because deprecation is a status that indicates the patch is outdated or has been superseded by a newer version, and thus should not be used 1 .  This behavior ensures that only the most up-to-date and secure patches are applied to the system, maintaining the integrity and security of the database environment 1 .

Configuring VM Host Affinity in a Nutanix AHV-powered cluster ensures that VMs are placed on specific hosts to optimize performance or HA. However, after a host failure, if database VMs cluster on a single remaining host, it indicates that the affinity rules alone are insufficient to maintain high availability (HA) during failover scenarios. To prevent this, the administrator should configure anti-affinity rules, which dynamically ensure that VMs (e.g., database server VMs) are spread across multiple hosts. Anti-affinity rules override default VM placement behavior during failover, reducing the risk of a single point of failure by keeping VMs separated even after a host outage.

Option A (Assign additional backup VMs on the same host) is incorrect because placing backups on the same host increases risk rather than mitigating it.

Option B (Increase affinity zones) is incorrect as " affinity zones " is not a standard Nutanix term in this context, and it does not address dynamic VM separation.

Option C (Configure automatic host failover in Prism Central) is incorrect because while failover is managed by AHV, it does not inherently prevent VMs from clustering without specific rules.

Option D is correct as anti-affinity rules proactively distribute VMs, enhancing HA in failure scenarios.

This approach leverages Nutanix AHV’s VM placement policies to ensure resilience.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring VM Affinity and Anti-Affinity

Nutanix AHV Administration Guide, Section: VM High Availability and Placement Rules

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

NDB supports SMTP server configuration for sending email notifications and alerts. SMTP server configuration requires specifying the SMTP server address, port, username, password, and encryption method. The encryption method determines how the email messages are secured during transmission. NDB supports two encryption methods for SMTP server configuration: TLS and SSL.

TLS (Transport Layer Security) is a protocol that encrypts and authenticates data between the email client and the SMTP server. TLS can operate in two modes: explicit and implicit. In explicit mode, the email client and the SMTP server negotiate the encryption method and parameters after establishing a plain text connection. This mode typically uses port 587. In implicit mode, the email client and the SMTP server assume that the connection is encrypted from the start, without any negotiation. This mode typically uses port 465.

SSL (Secure Sockets Layer) is a predecessor of TLS that also encrypts and authenticates data between the email client and the SMTP server. SSL operates in implicit mode only, and uses port 465 by default. SSL is less secure than TLS, but it is still widely used and supported by many email providers.

S/MIME (Secure/Multipurpose Internet Mail Extensions) is a standard that encrypts and signs email messages at the application layer, rather than the transport layer. S/MIME requires the use of digital certificates and public key cryptography to ensure the confidentiality and integrity of email messages. S/MIME is not a valid encryption method for SMTP server configuration, as it does not affect the connection between the email client and the SMTP server.

IPsec (Internet Protocol Security) is a suite of protocols that secures IP packets at the network layer, rather than the application or transport layer. IPsec can encrypt and authenticate data between any two IP endpoints, such as routers, firewalls, or hosts. IPsec is not a valid encryption method for SMTP server configuration, as it does not apply to the specific protocol or port used by SMTP.

References :

Nutanix Database Automation (NCP-DB) Course Details , Section 1.4: NDB Alerts and Notifications

Nutanix Database Automation (NCP-DB) Certification Details , Objective 1.4: Configure NDB Alerts and Notifications

Nutanix Database Automation (NCP-DB) YouTube Playlist , Video 1.4: NDB Alerts and Notifications

[Nutanix Database Automation (NCP-DB) User Guide], Section 1.4: Configure SMTP Server Settings

The Nutanix Era Time Machine provides various capabilities depending on the Service Level Agreement (SLA) selected during database registration 1 .  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 data 2 .  “Snapshots” are point-in-time copies of the database that can be used for recovery or cloning 2 .

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

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

Nutanix Era leverages the Nutanix time-efficient snapshots to create the clones 1 .  These database clones are highly space-efficient, consuming near-zero bytes by having only the further writes constituting to its size 1 . 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.

Ports 3205 and 3260 are important when working with Era because they must be open on the Era server and all Controller VMs (CVMs) to facilitate iSCSI connections 1 .  Specifically, port 3205 is used for iSCSI redirection 2 .  Please be careful of routing iSCSI traffic, as it could impact performance 2 .

When patching an Oracle Database Server VM, it ' s important to ensure that there is sufficient storage space allocated for the Grid home. A minimum of 10GB space is required for this purpose to accommodate the patching process without storage constraints. References: Nutanix Database Automation documentation, particularly in the sections discussing Oracle database server VM management and patching requirements.