Get Nutanix NCP-DB Exam Practice Questions - Real and Updated

Answer : A

In a Nutanix Era setup where Multi-Cluster is enabled and the Era Server storage container and Era provisioning container are different on the Era cluster, the administrator should configure a storage mapping between the Era server container and the remote container that is used for provisioning databases1.This is because Nutanix Era uses the storage container specified during the registration of the Nutanix cluster for provisioning databases1.Therefore, a storage mapping needs to be established between the Era server container and the remote container used for provisioning to ensure that the databases are provisioned correctly1.

Answer : A

According to the Nutanix Database Automation (NCP-DB) course, a Software Profile is a template that defines the configuration of the database engine, such as the version, edition, features, and parameters1.It also specifies the disk layout for the database installation, such as the size, type, and mount point of each disk1.However, the System Page File disk is omitted from the Software Profile, as it is automatically created by the NDB service based on the memory size of the database server VM1.The other options are included in the Software Profile, as they are essential for the database operation and performance1.Reference::

1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.3: Software Profiles, slide 5

Answer : B

When upgrading NDB and the upgrade includes updates to out-of-the-box (OOB) software profiles (e.g., predefined profiles for database software like PostgreSQL, SQL Server, etc.), NDB manages older versions of these profiles based on their usage. If the older OOB software profiles are not actively in use by any database VMs, NDB automatically deletes all versions of those profiles from its metadata and associated protection domains during the upgrade process. This cleanup mechanism helps maintain a lean and efficient system by removing obsolete profiles that are no longer relevant or required.

Option A is incorrect because the condition about Time Machines and snapshots in the last 24 hours is not a documented criterion for profile deletion during an NDB upgrade.

Option B is correct as it reflects NDB's behavior of removing unused OOB software profiles during upgrades to optimize resource usage and metadata.

Option C is incorrect because shutting down database VMs does not trigger automatic deletion of software profiles; the key factor is whether the profiles are in use.

Option D is incorrect because the concept of a 'base version' is not relevant here; deletion depends solely on whether the profiles are unused, not on versioning specifics.

This behavior ensures that only active and necessary profiles persist post-upgrade, streamlining administration.

Nutanix Database Service (NDB) User Guide, Chapter 6: Upgrading NDB, Section: Handling Software Profile Updates

Nutanix Support & Insights, Technical Note: 'NDB Upgrade Process and Software Profile Management'

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

Answer : A

When an administrator needs to scale the size of an Oracle database running on Nutanix NDB and originally configured using ASMLib (Automatic Storage Management Library), the most efficient approach is to use NDB's built-in scaling ability to resize existing vDisks. NDB supports dynamic resizing of virtual disks (vDisks) associated with database VMs, allowing the administrator to increase storage capacity without disrupting the database or requiring complex migrations. This method leverages Nutanix's storage integration, resizing the underlying vDisks and updating the ASMLib configuration to reflect the new size, ensuring seamless operation.

Option A (Leverage the scaling ability built into NDB to resize existing vDisks) is correct as it is the most efficient, native NDB feature for scaling storage.

Option B (Extend the size by adding new vDisks) is incorrect because adding new vDisks requires additional configuration (e.g., ASM disk group adjustments), making it less efficient than resizing.

Option C (Create a new, larger database and migrate) is incorrect because migration is time-consuming and unnecessary when resizing is supported.

Option D (Mount an iSCSI LUN and extend the database onto the new LUN) is incorrect because iSCSI LUNs are not the preferred method in NDB, and resizing vDisks is more integrated.

This approach minimizes downtime and complexity.

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Scaling Storage for Databases

Nutanix Support & Insights, Knowledge Base Article: 'Resizing vDisks for Oracle Databases in NDB'

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Servers

Answer : C, D

In the context of Nutanix Database Automation (NCP-DB), when there are insufficient resources on a development cluster, the administrator can adjust theComputeandDatabase Parametersprofiles to make the copy fit within the available resources1. The Compute profile includes settings related to CPU and memory resources, which can be adjusted to fit within the available resources.The Database Parameters profile includes settings that control the behavior and resource usage of the database, which can also be adjusted to optimize resource usage1.