NCP-DB Exam Dumps - Nutanix Certified Professional (NCP) Questions and Answers

After a DBA’s script corrupts an Oracle DB managed by NDB, the administrator needs to restore a clean copy using the latest available snapshot. The most straightforward action is to use the NDB Time Machine feature to select the most recent uncorrupted snapshot and create a new clone. This clone can serve as a restored version of the database, bypassing the corrupted data while leveraging existing snapshots for efficiency.

Option A (Fail the Oracle cluster over to a surviving RAC node) is incorrect because RAC failover is for HA, not corruption recovery via snapshots.

Option B is correct as it uses Time Machine to create a clone from a valid snapshot, addressing the corruption.

Option C (Use Time Machine to create a clone from file-level database backup) is incorrect because NDB primarily uses snapshots, not file-level backups, for cloning.

Option D (Provision a new Oracle DB and perform log catch-up) is incorrect because provisioning a new DB is more complex and unnecessary when a snapshot-based clone suffices.

This method ensures rapid recovery with minimal disruption.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring and Cloning from Snapshots

Nutanix Support & Insights, Knowledge Base Article: "Recovering from Database Corruption in NDB"

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

 To increase storage for a MongoDB database provisioned using NDB, the administrator needs to use the extend_storage parameter in the input file for the NDB CLI. This parameter specifies the amount of additional storage to be added to the database server VM in GB. For example, if the current storage size is 100 GB and the administrator wants to increase it to 150 GB, the input file should contain the following line:

extend_storage: 50

The other parameters are not relevant for this operation. The update parameter is used to update the database software version, the database parameter is used to specify the database name, and the data_percent parameter is used to specify the percentage of data to be copied during a clone operation. 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 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.

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

To assign the minimum permissions required for provisioning new databases in an NDB deployment, the IT manager should assign the Database Administrator role. This role provides the necessary privileges to provision, configure, and manage database instances within NDB, including creating new databases using software profiles and registering database servers. It is designed for database-specific tasks without granting broader infrastructure or administrative control, making it the least privileged role suited for this purpose.

Other options exceed the minimum requirements:

A. Infrastructure Administrator: Manages cluster infrastructure (e.g., storage, networking), which is more than needed for database provisioning.

B. Super Administrator: Grants full control over NDB, including user management and system configuration, far beyond provisioning.

C. Database Infrastructure Administrator: Includes infrastructure management in addition to database tasks, exceeding the minimum scope.

Thus, the verified answer is D, aligning with the principle of least privilege.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.4: Managing Users and Roles.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.3: Manage User Permissions (applicable to v7.5).

Nutanix NDB Administration Guide: "Role-Based Access Control (RBAC)" section, detailing Database Administrator role.

 In the Nutanix Database Automation (NCP-DB) process, when a database administrator is tasked with creating a new clone of a running SQL database and there are no authorized servers available, the administrator should click the Action icon to authorize one or more database server VMs1. This is because the Nutanix Database Service (NDB) requires authorized servers to perform operations such as cloning1. The authorization process allows the NDB to manage and perform operations on the database server VMs1.

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.

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

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

Other options are incorrect:

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

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

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

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

Official Nutanix Database Automation References

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

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

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

When a quality assurance (QA) team notices a significant change between a cloned database currently in use and one used a week ago, and they have an SQL script to verify differences, the NDB administrator needs to provide a clone reflecting the database state from a week ago. The task "Clone database selecting Point in Time data" allows the administrator to select a specific point-in-time snapshot (e.g., from a week ago) using the Time Machine feature. This creates a new clone with the exact data state at that time, enabling the QA team to compare it with the current clone.

Option A (Replicate a selected snapshot) is incorrect because replication is for HA, not creating a usable clone for QA.

Option B (Create a clone database from a snapshot) is incorrect because it does not specify point-in-time selection, limiting flexibility to the latest snapshot.

Option C (Clone database selecting Point in Time data) is correct as it allows precise selection of the week-old data state.

Option D (Perform a Log Catch Up operation) is incorrect because Log Catch Up applies recent logs, not reverting to a past state.

This approach meets the QA team’s need for historical data comparison.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Cloning with Point-in-Time Data

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

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

In a Nutanix Era setup where Multi-Cluster is enabled and the Era Server storage container and Era provisioning container are different on the Era cluster, the administrator should configure a storage mapping between the Era server container and the remote container that is used for provisioning databases1. This is because Nutanix Era uses the storage container specified during the registration of the Nutanix cluster for provisioning databases1. Therefore, a storage mapping needs to be established between the Era server container and the remote container used for provisioning to ensure that the databases are provisioned correctly1.