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. Reference:: Nutanix

Support & Insights, Cisco Nexus Data Broker Deployment Guide, Release 3.10.x

The NDB user interface supports multiple languages, including English, Chinese, and Japanese. You

can change the language pReference: in the NDB settings page. The NDB user interface does not

support Korean, French, or German languages at this time. Reference::

Nutanix Database Management & Automation Training Course, Module 1: Introduction to Nutanix

Era, Lesson 1: Nutanix Era Overview, Slide 7: NDB User Interface

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 1: Describe NDB

Concepts, Objective 1.6: Languages

Nutanix Database Service (NDB) uses software profiles for database patching to keep your databases

secure and optimized1. When a new database is provisioned, it will be on your current

environment’s database version to maintain consistency and stop version sprawl1. Therefore, after

an administrator has applied an Oracle security patch to a database server VM registered in Era, the

change can be made available to other existing database instances by creating a new software profile

in Era from the patched VM1.

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.

Reference:: 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 C because it follows the recommended procedure for applying a CU to a SQL

Server Software Profile in NDB. By applying the patch to the profile VM, the administrator ensures

that the CU is compatible with the existing Software Profile settings and configuration. By creating a

new Software Profile version, the administrator preserves the previous version of the Software

Profile for rollback purposes and allows the new version to be tested and published. Option A is

incorrect because it deletes the existing Software Profile, which may cause data loss and prevent

rollback. Option B is incorrect because it does not apply the patch to the profile VM, which may result

in errors or inconsistencies in the Software Profile. Option D is incorrect because it creates a new

Software Profile instead of a new version, which may cause confusion and duplication.

Reference:: The following sources provide more information about the Software Profile management

and patching in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 5: Patching Databases Using

NDB, Lesson 5.2: Creating and Modifying Software Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section

4 - Operate and Maintain an NDB Environment

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.2:

Creating and Modifying Software Profiles

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.3:

Testing and Publishing Database Patches

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.

Reference:: Nutanix Database Automation documentation, focusing on database agents and their

roles in transaction log management.

To enable iSCSI connections between the Nutanix Database Service (NDB) server, Controller VMs

(CVMs), and Prism Element, a Data Services IP must be configured in Prism Element. The Data

Services IP acts as a cluster-wide address that facilitates iSCSI target discovery and connectivity. It is

used by Nutanix Volumes (a block storage service) to present storage to external clients or services,

such as the NDB server, via the iSCSI protocol. This IP ensures that iSCSI traffic is routed correctly and

remains available even if a CVM fails, as ownership of the Data Services IP can move to another CVM

in the cluster.

Configuring the Data Services IP is a prerequisite for integrating NDB with a Nutanix cluster, as NDB

relies on iSCSI to manage database storage operations like provisioning and cloning. Without this

configuration, the NDB server cannot establish the necessary connections to the CVMs for database-

related tasks. Options like Virtual IP, Secondary DNS IP, and Backplane IP are not relevant in this

context:

Virtual IP: This is typically associated with high-availability setups for applications, not iSCSI

connectivity.

Secondary DNS IP: This pertains to network resolution, not storage connectivity.

Backplane IP: This is an internal network IP for cluster communication, not for external iSCSI access.

Thus, the correct and verified answer is the Data Services IP.

Official Nutanix Database Automation Reference:

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring

an NDB Solution, Lesson 2.2: Configuring NDB Prerequisites.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section

2: Deploy and Configure an NDB Solution (applicable to v6.10 as foundational concepts remain

consistent).

Nutanix Support & Insights Portal: "Configuring iSCSI Data Services IP for Nutanix Volumes" (general

Volumes configuration applicable to NDB).

The correct answer is B and D because these are the two status values that can be set within the

Alerts Dashboard in NDB. Resolved means that the alert has been fixed and no longer requires

attention. Acknowledged means that the alert has been seen and is being worked on. Option A is

incorrect because Auto is not a status value, but a mode that automatically resolves alerts based on

predefined rules. Option C is incorrect because Data Resiliency is not a status value, but a feature

that ensures the availability and integrity of the data in NDB.

Reference:: The following sources provide more information about the Alerts Dashboard and its

status values in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 3: Monitoring Alerts and

Storage Usage Within an NDB Implementation, Lesson 3.1: Monitoring Alerts

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section

3 - Monitor Alerts and Storage Usage Within an NDB Implementation

Nutanix Database Service (NDB) User Guide, Chapter 3: Monitoring Alerts and Storage Usage Within

an NDB Implementation, Section 3.1: Monitoring Alerts

[Nutanix Support & Insights], Resolving All Alerts Related to a Database or Database Server VM in

NDB

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 Reference:

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 NDB alert retention feature allows the database administrator to configure the duration for

which the NDB alerts are stored and displayed in the NDB instance. The NDB alert retention feature

supports alert retention globally, meaning that the same retention period applies to all the alerts

generated by the NDB instance, regardless of the source cluster, policy, or operation. The database

administrator can set the alert retention period from 1 day to 365 days, or choose to retain the alerts

indefinitely. The NDB alert retention feature helps to manage the storage space and the visibility of

the NDB alerts.

The NDB alert retention feature does not support retention at the individual policy, grouped policy,

or registered cluster level. The NDB alert retention feature applies to all the alerts uniformly, and

does not allow the database administrator to specify different retention periods for different policies

or clusters.

Reference::

Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment,

Lesson 3.2: Nutanix Era Deployment, slide 11.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations,

Lesson 5.1: Nutanix Era Operations, slide 6.