Get NCP-DB Dumps : Verified Nutanix Certified Professional - Database Automation (NCP-DB) v6.5

For enabling Multi-Cluster management on an Era installation, the hypervisor version must be supported and port 9440 must be open between the Era VM and clusters. This ensures that the Era VM can communicate with the clusters for management tasks1.

 According to the Nutanix Database Automation (NCP-DB) learning documents, when dealing with an Availability Group (AG) database, the database should be registered as an Availability database1. This is because the AG database is hosted on replicas with different named instances, and registering it as an Availability database allows for Copy Data Management operations to be performed across all instances. This is particularly important when services such as the Analytics service running on SQLAGN3\DW require real-time data1.

Page files are temporary files that Windows uses to store data that does not fit in the physical memory. Page files can interfere with the registration of a database server VM with NDB, as they can cause errors or performance issues. Therefore, page files should be located in a separate drive or partition from the C:\ drive, where the NDB agent and other files are installed. System, database, and backup files do not prevent the registration of a database server VM with NDB, as long as they are not corrupted or incompatible with the NDB requirements. References:

• Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2: Configuring an NDB Instance, Slide 13: Registering Database Server VMs
• Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.1: Apply procedural concepts to register database server VMs and databases

The correct answer is B because it allows the administrator to create a custom role with the specific privileges that the Jr DBA user needs, and then assign that role to the user. This way, the administrator can control the access level of the Jr DBA user without affecting the existing roles or users in NDB. Option A is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then adding more privileges, which is unnecessary and redundant. Option C is incorrect because it involves creating a user for the Jr DBA, but not assigning a role to the user, which means the user will not have any privileges in NDB. Option D is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then removing some of the privileges, which is inefficient and risky.

References: The following sources provide more information about the user roles and privileges in NDB:

• Nutanix Database Management & Automation (NDMA) course, Module 8: Administering an NDB Environment, Lesson 8.6: Managing Access Controls in NDB
• Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 6 - Administer an NDB Environment
• Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.6: Managing Access Controls in NDB

The administrator can remediate the issue of critical storage alerts by scaling up the storage directly from the Database Summary page for that specific DBA database. This action allows for an increase in storage capacity to alleviate space constraints and prevent future critical alerts related to storage space1. The other options are not correct, as they either involve scaling the entire database group, which may not be necessary or desired, or require additional steps outside of NDB, which may not be feasible or efficient. References:

• 1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.4: Database Scaling, slide 5