Nutanix Updated NCP-DB Exam Questions and Answers by zimal

 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.

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

Option A: On the Era Dashboard Database Summary Table under Source Database. The dashboard provides a summary of the databases, including their sizes1.

Option B: Under the Capacity widget on the Database Server VMS > List database summary page. While this might provide information about the capacity, it does not specifically provide the size of a Source Database.

Option C: On the Databases > Sources table. This table provides detailed information about the databases, including their sizes1.

Option D: On the Profiles > Database Parameters list for the assigned DB Parameter Profile. This list provides parameters for the database but does not provide the size of a Source Database.

 In Nutanix Era, a Volume Group is the recommended storage provisioning method for a large I/O-intensive database that doesn’t support a multi-disk layout1. A Volume Group in Nutanix Era is a collection of disks that can be managed as a single entity, providing a way to aggregate the storage capacity of multiple disks into a larger storage unit1. This allows for better performance optimization as it enables the database to leverage the combined I/O capabilities of all the disks in the group1. It’s important to note that while other options like Load Balancing, Storage Spaces, and vDisk based provisioning can also be used in certain scenarios, a Volume Group is specifically designed for situations where a single, high-performance storage unit is required1.