Nutanix Updated NCP-DB Exam Questions and Answers by anton

The error message in the exhibit indicates that the operation failed during the “Create and Register Database Server VMs” step because “Provisioning of all the observers simultaneously took more than two hours.” This type of error is associated with MySQL, as it involves observers which are a part of MySQL Group Replication, used for ensuring high availability1. The other options are not related to the error message, as they do not use observers or Group Replication for clustering. References:

1: Nutanix Database Automation (NCP-DB) course, Module 5: Database High Availability, Lesson 5.2: MySQL Group Replication, slide 7

NDB supports SQL Server database groups so multiple databases can share one Time Machine and a coordinated protection schedule. Nutanix documents a maximum selection of 35 databases for group-registration workflows and states that Microsoft recommends no more than 35 databases in one database group. A SQL Server database server VM or cluster can contain as many as five NDB database groups. The efficient design for 90 databases is therefore three groups—for example, 35, 35, and 20 databases—with one Time Machine for each group. A single 90-database group exceeds the supported or recommended size, while creating 90 individual Time Machines or relocating databases to other servers introduces unnecessary operational overhead. Therefore, option B is correct. Nutanix SQL Server database-group documentation

MongoDB registration requires the database tools to be available to NDB and placed in the expected MongoDB software-home layout. Nutanix instructs administrators to download and extract the MongoDB tools, then copy or extract them into the bin directory under the software home specified during registration. Accordingly, both B and D describe required preparation. Installing MongoDB through YUM or DNF is not the required approach; Nutanix states that package-manager installation is not recommended and prevents NDB-managed patching in relevant workflows. The requiretty setting must be disabled or absent for NDB sudo automation, so an option stating that it must be enabled reverses the requirement. With the tools and binaries in the software-home bin path, NDB can discover and execute the utilities needed to manage the registered server. These requirements are documented under MongoDB Prerequisites.

The Removal schedule is a feature of Nutanix Era that allows you to specify when a database clone will be automatically deleted. You can modify the Removal schedule of an existing clone by selecting the clone from the Clones page, clicking on the Update button, and changing the Removal schedule option to the desired date. This way, you can extend or shorten the lifespan of a clone as per your requirements. You do not need to remove the existing Removal schedule and add a new one, as this would be an unnecessary step. You also do not need to update the Removal schedule to the end of the month, as this would not meet the request of keeping the clone for an additional 14 days. References:

Nutanix Database Management & Automation Training Course, Module 4: Protecting Databases Using Time Machine, Lesson 3: Cloning Databases, Slide 10: Clone Removal Schedule

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 5: Protect NDB-managed Databases Using Time Machine, Objective 5.3: Given business requirements, perform a database clone