Nutanix NCP-DB - Nutanix Certified Professional - Database Automation (NCP-DB v7.5)

In Nutanix Era, an administrator can modify the Alert Severity level by navigating to the Alerts Policies from the dropdown menu. Once there, they can select the Policy that needs to be modified and set the desired severity level1. This allow s the administrator to customize the alerts according to their requirements, ensuring that they are notified of the most critical events in their environment21.

NDB deployments on NC2 use overlay networking created with Nutanix Flow Virtual Networking. Consequently, an appropriate Flow overlay subnet must be created for NDB and the database server VMs that it will manage. A floating IP address must also be created or assigned to the NDB VM so that the NDB interface and services are reachable through the cloud networking environment. A Flow underlay subnet is not the supported network type for this deployment. Although an NC2 environment ultimately operates within AWS networking infrastructure, creating a native AWS VPC is not the NDB-specific deployment step requested by the question. Nutanix’s NC2 networking documentation identifies Flow-created overlay networks, while the Flow integration guidance describes assigning a floating IP address to the NDB VM.

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

To deploy Nutanix Database Service (NDB) in Prism Element, the minimum account access level required is Cluster Administrator. This role provides the necessary permissions to manage cluster resources (e.g., storage, networking, and VMs) required for NDB deployment, including registering the cluster with NDB, configuring storage containers, and deploying NDB components. Lower roles like Viewer or Backup Administrator lack the scope to perform these tasks, and User Administrator is focused on user management, not deployment.

Other options are insufficient:

A. User Administrator: Manages users and roles, not cluster operations.

C. Viewer: Read-only access, inadequate for deployment.

D. Backup Administrator: Limited to backup tasks, not deployment.

Thus, the verified answer is B, aligning with NDB deployment prerequisites.

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) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix Cluster (applicable to v7.5).

Nutanix NDB Installation Guide: "Prism Element Role Requirements" section.

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

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

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

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

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

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

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

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

In the Nutanix Era management interface, an administrator should perform an upgrade under the Administration > Maintenance section1. As part of the upgrade process, the Era server is upgraded first, followed by all the Era cluster agents and database server agents in parallel1. 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 upgrade1. This ensures that the Nutanix Era environment is always up-to-date with the latest features and security updates1.

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

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

NDB coordinates Oracle-native recovery mechanisms when restoring a selected PDB to a specified point in time. Time Machine supplies the required snapshot and transaction-log recovery points, while Oracle Recovery Manager restores the necessary PDB datafiles and applies archived redo through the requested timestamp. Oracle redo is maintained at the container database level, so the process does not literally use a completely independent redo stream for each PDB. Nevertheless, Oracle’s recovery operation limits the recovery scope to the selected PDB and processes all required archived-log switches automatically. NDB does not reconstruct Oracle transactions using Prism Central’s Cassandra data, apply flat-text backup files, or require the administrator to append database blocks manually. Nutanix documents the ability to restore selected PDBs by snapshot or timestamp in its official Oracle PDB and CDB management guidance.

According to the Nutanix Database Automation (NCP-DB) Learning documents12, to clone a source production database to an existing development server, the following actions must be taken:

A. The development server must be registered by Era in order to receive the clone1. This is because Nutanix Era is a database management tool that manages the lifecycle of databases and their copies. Registering the development server with Era allows it to manage the database on that server.

D. The development server must have the IP and credentials provided during cloning2. This is necessary for Era to access the development server and perform the cloning operation. The IP address and credentials are used to establish a connection to the development server. Without these details, Era would not be able to access the server and perform the cloning operation.