Nutanix Updated NCP-DB Exam Questions and Answers by yasir

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.

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.

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

A. Grid home2 B. Oracle home2

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

In Nutanix Database Service (NDB), the Time Machine (TM) feature allows restores, including Point-in-Time (PIT) restores, which require continuous log retention to replay transaction logs to a specific moment. If the option to restore data to a Point in Time is unavailable, it indicates that the current Time Machine Service Level Agreement (SLA) does not support continuous log retention. NDB SLAs are categorized (e.g., BRONZE, SILVER, GOLD), with BRONZE or higher levels required to enable PIT restore by including continuous log retention. The administrator must update the TM SLA to at least BRONZE to enable this feature, ensuring logs are retained for PIT operations.

Option A (Restore Source DB using a snapshot) is incorrect because a snapshot-only restore does not support PIT; it restores to the snapshot time only.

Option B (Update TM SLA to BRONZE or higher) is correct as it enables continuous log retention necessary for PIT restores.

Option C (Create DB clone using a snapshot) is incorrect because cloning from a snapshot does not provide PIT capability without log retention.

Option D (Update TM SLA to BRASS or lower) is incorrect because "BRASS" is not a valid SLA tier, and lowering the SLA would not enable PIT.

This adjustment ensures PIT restore functionality.

References

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

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

In an NDB high-availability deployment, multiple API server and repository VMs protect the availability of the management plane. If the primary API server becomes unavailable, NDB automatically fails over API responsibilities to an available standby server. HAProxy directs management requests to the functioning service, allowing administrators and automation clients to continue accessing NDB. The managed databases operate independently of the NDB API service for normal client connections, so an API-server failure does not automatically stop database workloads. Backup or patching workflows are not categorically canceled or suspended merely because one API service fails; their processing continues through the surviving HA components, subject to the state of the individual operation. Nutanix’s official highly available NDB architecture confirms that NDB automatically fails over to a standby VM when the primary API server or repository VM becomes unavailable.