NCP-DB Exam Dumps : Nutanix Certified Professional - Database Automation (NCP-DB v6.10)

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

 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.

When setting up a Time Machine for a newly-provisioned database in NDB, the GUI allows the administrator to configure the frequency of snapshots for data protection. The maximum number of snapshots per day that can be configured in the NDB GUI is 6. This limit ensures a balance between data granularity (for point-in-time recovery) and storage overhead, preventing excessive resource consumption. The administrator can schedule these snapshots at regular intervals (e.g., every 4 hours) within the Time Machine configuration wizard.

Other options are incorrect based on NDB’s design:

A. 4: This is below the maximum supported limit.

C. 8: Exceeds the GUI-configurable maximum.

D. 12: Far exceeds the limit, suggesting manual or unsupported customization.

Thus, the verified answer is B, aligning with NDB’s snapshot scheduling constraints.

Official Nutanix Database Automation References

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

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.1: Configure Time Machine Settings (applicable to v6.10).

Nutanix NDB Administration Guide: "Time Machine Snapshot Scheduling" section.