NCP-DB Exam Dumps - Nutanix Certified Professional - Database Automation (NCP-DB v6.10)

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.

If an SQL database clone deletion fails immediately in NDB, the most likely cause is that the clone has been marked as Immutable. An immutable clone is protected from deletion to prevent accidental data loss, often set for critical development or testing environments. This protection must be explicitly removed by the administrator (e.g., via the NDB GUI or CLI) before the deletion can proceed.

Option A (A refresh operation is in progress) is incorrect because a refresh operation would delay but not immediately fail the deletion.

Option B (The clone has been marked as Immutable) is correct as immutability blocks deletion until changed.

Option C (The database was not marked as Offline before the operation) is incorrect because the offline state is not a prerequisite for clone deletion.

Option D (The database data drives are shared with other applications) is incorrect because shared drives might cause issues, but immutability is a more direct cause of immediate failure.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Clones and Deletion

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Clone Deletion Failures in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

NDB can leverage snapshots and transaction logs to refresh a database clone to the latest state of the source database. Snapshots are point-in-time copies of the database that are stored on the Nutanix cluster. Transaction logs are records of the changes made to the database after the snapshot was taken. NDB can use either snapshots or transaction logs, or a combination of both, to refresh a database clone. Cerebro logs and templates are not used for refreshing database clones. Cerebro logs are used for log catch-up operations, which are different from refresh operations. Templates are used for provisioning new databases, not for refreshing existing ones. References:

Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.3 - Refreshing Clones

Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Clone Database Management

 Before patching a Linux OS on a database server VM provisioned using NDB, you must configure the repository for the OS updates. This can be done by creating a Repository Profile in NDB and specifying the URL, username, and password for the repository. The Repository Profile can be applied to one or more database server VMs during the provisioning process or later. By configuring the repository, you ensure that NDB can access and download the latest OS patches from a trusted source. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, Nutanix Database Automation User Guide.

The Nutanix Era Time Machine provides various capabilities depending on the Service Level Agreement (SLA) selected during database registration1. For a database with a Bronze SLA, the Time Machine supports both “Log Catch up” and "Snapshots"2. “Log Catch up” allows the Time Machine to keep up with the latest changes in the database by capturing log data2. “Snapshots” are point-in-time copies of the database that can be used for recovery or cloning2.

The provided exhibit shows the "Enable Multi-Cluster" configuration wizard in NDB, where the VLAN dropdown is empty with a "Nothing found" message, indicating that no VLANs are available for selection. This issue arises because NDB requires a network profile to be created before provisioning the NDB Agent VM and enabling multi-cluster support. A network profile defines the static VLANs managed by NDB, which are essential for network configuration during multi-cluster setup. The warning in the exhibit ("An NDB managed static vLAN is required to provision the NDB Agent VM. Add an NDB managed static vLAN using the Networks page to continue.") reinforces that the administrator must create a network profile via the Networks page to populate the VLAN dropdown.

Option A (A network profile must be created first) is correct as it addresses the root cause by ensuring VLANs are defined in a network profile.

Option B (Verify if subnet leverages advanced network control) is incorrect because advanced network control is not a prerequisite for VLAN selection in this context.

Option C (IP address pool must be managed in NDB) is incorrect because IP address pools are managed separately and not required for VLAN selection at this stage.

Option D (VLAN subnet must use IP address management) is incorrect because IP address management is not a direct requirement for enabling VLAN selection in the wizard.

After creating the network profile, the administrator can proceed with the multi-cluster enablement.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring Network Profiles for Multi-Cluster

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting VLAN Issues in NDB Multi-Cluster Setup"

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

For restoring a database provisioned on Storage Spaces, especially when virtual disks are shared among multiple databases, the supported method is a copy-based restore via the NDB GUI. This method allows for a precise and controlled restoration process suitable for shared storage environments.References: Nutanix Database Automation documentation, specifically in the section on database restoration methods and storage spaces.

Based on the exhibit, the administrator is logged in with the Database Admin account (bsmith@ntnxlab.local), which does not have the permission to create local users on NDB. Only the Super Admin account (bsmith) has this permission, as indicated by the User type column. Therefore, the administrator needs to log out and log in again with the Super Admin account to add a new database admin as a local user to NDB. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, Nutanix Database Automation User Guide.