Pass the Nutanix Certified Professional (NCP) NCP-DB Questions and answers with ExamsMirror

The image provided shows the "Register Database Server VM" interface in NDB, which includes fields for registering a database server, including options for Windows and SQL Server credentials. When an administrator wants to register a database using a SQL Server User (instead of Windows credentials), the appropriate place to specify this user is in the "Connect to SQL Server Login" section. The interface includes a "User Name" field under this section, which becomes relevant after selecting the option to use a SQL Server User (typically indicated by a radio button or dropdown, though not fully visible in the image). This allows NDB to authenticate and manage the SQL Server instance using database-specific credentials rather than relying solely on Windows Administrator credentials.

Option A (In the Windows Administrator Name field) is incorrect because this field is intended for Windows OS-level credentials, not SQL Server-specific login credentials.

Option B (In the Login field after selecting SQL Server User) is correct as it aligns with the "Connect to SQL Server Login" section in the interface, where the SQL Server User can be specified after the appropriate option is selected.

Option C (Only via the command line registration option) is incorrect because the GUI provides a direct method to specify SQL Server credentials, as shown in the image.

Option D (By modifying the code in the API Equivalent section) is incorrect because the API Equivalent section is for reference and does not allow real-time modification; it’s meant to guide API-based automation, not manual registration.

The image confirms the presence of a "User Name" field under "Connect to SQL Server Login," supporting the use of a SQL Server User for registration.

References

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Registering Database Server VMs

Nutanix Support & Insights, Knowledge Base Article: "Registering SQL Server VMs with NDB Credentials"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 2: Deploy and Configure an NDB Solution

To reset the NDB GUI password in Nutanix Database Service (NDB), an administrator must access the system through an SSH session and use the appropriate command-line interface (CLI) tools provided by NDB. The correct process involves entering the era-server CLI, which is the specific CLI environment for managing NDB-related configurations, including security settings like password resets. Once in the era-server CLI, the administrator executes the security password reset command to initiate the password reset process for the NDB GUI. This method ensures that the reset is performed within the NDB-managed environment securely and aligns with Nutanix’s recommended administrative procedures.

Option A is correct because it specifies the era-server CLI and the exact command security password reset, which are consistent with NDB’s administrative tools for managing GUI access credentials.

Option B (sudo passwd era) is incorrect because era is not a system user account in the context of NDB’s Linux-based control plane; this command pertains to standard Linux user management, not NDB-specific GUI password resets.

Option C (sudo passwd admin) is also incorrect as admin refers to a generic user that may not correspond to the NDB GUI account, and this approach bypasses NDB’s internal security mechanisms.

Option D is incorrect due to a typo (era CLI instead of era-server CLI), which renders it imprecise despite the intent being similar to Option A.

This process assumes the administrator has SSH access to the NDB control plane VM and the necessary privileges to execute these commands.

References

Nutanix Database Service (NDB) User Guide, Section: Administering an NDB Environment, Subsection: Managing Access Controls and Password Resets

Nutanix Support & Insights, Knowledge Base Article: "Resetting NDB GUI Password via CLI"

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

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

When an administrator schedules the removal of an existing database clone to minimize user impact (e.g., during weekend hours), the "Update Removal Schedule" feature in NDB allows for planning the operation. Among the options, the "Delete supporting snapshot from NDB" is pre-selected as a non-optional action. This ensures that the snapshot data associated with the clone is removed along with the clone itself, maintaining storage efficiency and consistency in the Time Machine framework. Other options may be selectable but are not mandatory by default.

Option A (Create an alert before removal) is incorrect because alerts are optional notifications, not a required action.

Option B (Delete supporting snapshot from NDB) is correct as it is a default, non-optional step to clean up snapshot data.

Option C (Unregister the database clone from NDB) is incorrect because unregistration is an optional administrative step, not pre-selected.

Option D (Delete the database clone from the VM) is incorrect because the clone deletion itself is the primary action, but snapshot deletion is the non-optional supporting task.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Clone Removal

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

The correct answer is C because a stretched VLAN is a VLAN that spans across multiple Nutanix clusters, which may cause network conflicts or latency issues when starting the database server. Option A is incorrect because a DHCP VLAN is a VLAN that uses dynamic IP address allocation, which does not affect the database server startup. Option B is incorrect because a static VLAN is a VLAN that uses fixed IP address allocation, which also does not affect the database server startup. Option D is incorrect because IPAM is not a type of VLAN, but a feature of NDB that allows managing IP addresses for database servers and databases.

References: The following sources provide more information about the VLAN and IPAM concepts and configuration in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Configuring NDB High Availability

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 2 - Deploy and Configure an NDB Solution

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section 2.4: Configuring NDB High Availability

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.5: Managing Networks in NDB

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.6: Managing IP Addresses in NDB

An administrator can configure a custom SSL certificate for Era through the Era User Interface (UI)1. This can be done by logging into the Nutanix Console and selecting SSL Certificates from the drop-down list inside the gear icon23. In the SSL Certificate dialog box, the administrator can click Replace Certificate, then select the Import Key and Certificate radio button23. This process ensures secure communication within the Nutanix Era environment4.

To deploy a database resilient cluster engine across three Nutanix clusters, the database engine must support high availability (HA) and distributed deployment capabilities that NDB can manage across multiple clusters. PostgreSQL is the only database engine listed that NDB supports for a resilient cluster deployment across multiple clusters. NDB’s HA features for PostgreSQL include automated failover, replication, and data consistency across geographically distributed clusters, making it suitable for a three-cluster scenario. This is achieved through PostgreSQL’s built-in streaming replication and NDB’s orchestration of HA policies.

Other options are not supported for this use case in NDB:

A. MariaDB: While MariaDB supports replication, NDB does not currently provide multi-cluster HA or resilient cluster deployment for MariaDB.

B. MySQL: Similar to MariaDB, MySQL lacks native multi-cluster HA support within NDB’s framework.

D. Oracle: Oracle databases can be managed by NDB, but multi-cluster resilient deployments are not natively supported; Oracle RAC (Real Application Clusters) requires specific configurations beyond NDB’s standard capabilities.

Thus, the verified answer is C, as PostgreSQL aligns with NDB’s multi-cluster resilience features.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.2: Configuring Multi-Cluster HA.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v6.10).

Nutanix NDB Administration Guide: "Supported Database Engines for HA" section, highlighting PostgreSQL multi-cluster support.

In the context of Nutanix Database Automation (NCP-DB), when provisioning a new Oracle SIHA DB & VM, if only ASMFD is available in the ASM Driver drop-down, it indicates that ASMLIB is not included in the current software profile. To provision the requested SIHA DB and DB VM with ASMLIB, it’s essential to update the software profile to include the ASMLIB driver. This action will enable ASMLIB as an option in the ASM Driver drop-down during the provisioning workflow.

References:

Nutanix Database Automation (NCP-DB) Course Details, Section 2.3: Provisioning Oracle Databases

Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.3: Provision Oracle Databases

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.3: Provisioning Oracle Databases

[Nutanix Database Automation (NCP-DB) User Guide], Section 2.3: Provision Oracle Databases

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.

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