Online NCP-DB Questions Video

When a vCenter instance managing multiple clusters, including a Nutanix cluster hosting the NDB service, crashes and a new dedicated vCenter server is deployed, the administrator must update the vCenter settings within NDB to re-establish connectivity and management. The correct action is to navigate to the NDB Administration page, where cluster and vCenter configurations can be updated. This page allows the administrator to re-register the new vCenter instance, ensuring NDB can continue to manage the clusters and database VMs effectively. This approach avoids unnecessary reconfiguration wizards or waiting for automatic syncs.

Option A (Click the Getting Started page and perform the configuration wizard) is incorrect because the Getting Started wizard is for initial setup, not post-crash vCenter updates.

Option B (Update cluster settings from the NDB administration page) is correct as it provides the specific interface to modify vCenter settings after a crash.

Option C (Open the maintenance page in NDB and configure the cluster settings) is incorrect because the maintenance page is for service operations, not vCenter reconfiguration.

Option D (Wait 60 minutes and Prism Central will automatically sync NDB) is incorrect because Prism Central does not automatically sync vCenter settings in NDB; manual updates are required.

This ensures seamless integration with the new vCenter instance.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Updating vCenter Settings

Nutanix Support & Insights, Knowledge Base Article: "Reconfiguring vCenter in NDB After Failure"

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

 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.

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 References

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.