Nutanix NCP-DB Nutanix Certified Professional - Database Automation v6.10 Exam Practice Test

Answer : D

When using the 'Patch OS now' feature in NDB to apply updates to a Red Hat-based operating system, the administrator can limit updates to security patches only by leveraging the Advanced Options. Under the 'Custom commands' section of the operating system patching command window, entering yum update --security instructs the package manager to install only security-related updates. This ensures the system remains secure without applying all available updates, which could introduce instability.

Other options are incorrect or incomplete:

A . Point the database VM to a custom patch repository and enter yum update --security command: This requires manual intervention outside NDB's patching framework.

B . Check Advanced Options and under Pre-post commands, enter yum update security in the pre-operating system patching command window: Pre-post commands are for pre/post actions, not the main patching process, and the syntax lacks the --security flag.

C . Point the database VM to a custom patch repository before using the Patch OS now feature: This sets up a repository but doesn't specify security-only updates within NDB's interface.

Thus, the verified answer is D, aligning with NDB's patching customization.

Official Nutanix Database Automation Reference:

Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.3: Creating Maintenance Plans.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v6.10).

Nutanix NDB Administration Guide: 'Patch OS Now with Custom Commands' section.

Answer : D

To change the NDB GUI password via the CLI, the administrator should use the command era-server > security password reset. This command interacts with the NDB server (referred to as era-server in the CLI context) to reset the password for the GUI admin user. The process typically prompts for the new password and confirmation, ensuring secure password management. This is the supported method for CLI-based password changes in NDB.

Other options are incorrect:

A . sudo passwd era: The passwd command is for Linux user accounts, not NDB-specific GUI credentials.

B . sudo user name admin password: This is not a valid command syntax for NDB CLI.

C . era-server > username admin password: This lacks the correct subcommand (security password reset) and syntax.

Thus, the verified answer is D, aligning with NDB's CLI security management.

Official Nutanix Database Automation Reference:

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.6: Managing NDB via CLI.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.5: Manage NDB Security (applicable to v6.10).

Nutanix NDB Administration Guide: 'Changing GUI Password via CLI' section, detailing era-server commands.

Answer : A

The exhibit shows the configuration of unencrypted Active Directory (AD) access in NDB, with the 'Primary URL' set to ldap:// (indicating LDAP rather than LDAPS). Unencrypted LDAP communication uses port 389 by default. For NDB to communicate with Active Directory, this port must be allowed through the firewall to enable the NDB server to perform authentication and directory lookups using the specified service account (e.g., administrator).

Other options are incorrect in this context:

B . 636: This is the default port for LDAPS (LDAP over SSL/TLS), which is encrypted and not applicable since the configuration uses unencrypted LDAP.

C . 2009: This is not a standard port for LDAP or AD communication and is unrelated to NDB's AD integration.

D . 9440: This is associated with Prism Element's HTTPS management interface, not AD access.

Thus, the verified answer is A. 389, ensuring unencrypted LDAP communication between NDB and Active Directory.

Official Nutanix Database Automation Reference:

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.5: Configuring Active Directory Integration.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.4: Configure AD Access (applicable to v6.10).

Nutanix NDB Administration Guide: 'Active Directory Integration' section, detailing LDAP port requirements.

Answer : B

During an NDB upgrade, the upgrade process follows a specific order to maintain stability and HA. The Leader NDB API Server is upgraded first. This server coordinates API requests and ensures the control plane remains operational. Upgrading the leader first minimizes disruption, as subsequent components (e.g., other API servers, HAProxy) rely on its leadership role. Once the leader is upgraded, the remaining NDB HA control plane VMs (e.g., follower API servers, HAProxy) are updated in sequence.

Other options are incorrect:

A . NDB Server: Refers to the main NDB instance, not upgraded first.

C . Leader HAProxy: Upgraded after API servers to maintain load balancing.

D . NDB Agent VMs: Upgraded last, as they are client-side components.

Thus, the verified answer is B, reflecting the upgrade sequence.

Official Nutanix Database Automation Reference:

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

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.3: Perform NDB Updates (applicable to v6.10).

Nutanix NDB Administration Guide: 'NDB Upgrade Process' section.

Answer : A

After a new NDB deployment, the administrator can test the provisioning capabilities using a database instance that is fully supported and readily configurable out of the box. PostgreSQL is the most suitable option because it is one of the core database engines supported by NDB from the initial deployment, with built-in provisioning templates and HA capabilities. NDB provides a streamlined process to provision PostgreSQL instances, making it an ideal choice for testing provisioning workflows, including VM creation, storage allocation, and network configuration.

Other options may require additional setup or licensing:

B . Oracle DB: Requires specific licensing and additional configuration, not typically available for initial testing.

C . MSSQL Server: Supported but may need Microsoft licensing and setup, less immediate than PostgreSQL.

D . MongoDB: Supported but less commonly used for initial testing due to its NoSQL nature and additional configuration needs.

Thus, the verified answer is A, reflecting PostgreSQL's accessibility for testing.

Official Nutanix Database Automation Reference:

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Provisioning Databases.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Provision Database Instances (applicable to v6.10).

Nutanix NDB Administration Guide: 'Supported Databases for Provisioning' section, noting PostgreSQL availability.

Answer : A, C

When creating a clone on an existing database server but no Authorized database servers are defined to support the cloned database, the administrator must authorize the necessary Database Server VMs. Two valid methods exist within NDB: (1) Using the Time Machine interface, the administrator can navigate to the Actions menu and select 'Authorize Database Server VMs' to designate specific VMs for clone support, providing a proactive authorization step. (2) During the Clone creation process, the wizard includes an option (e.g., a plus icon) to authorize one or more database server VMs on the fly, streamlining the process if authorization is needed mid-operation.

Option A (Within Time Machine, use the Actions menu and Authorize Database Server VMs to identify which database server VMs to authorize for clones) is correct as it is a dedicated authorization method in Time Machine.

Option B (Within the Database Server VM Summary window, update the database server to be authorized for supporting cloned databases) is incorrect because the Summary window is for viewing, not authorizing, clone support.

Option C (During the Clone creation process, click the plus icon to authorize one or more database server VMs) is correct as it allows real-time authorization during cloning.

Option D (During the database server provisioning process, flag the database server to be authorized for supporting cloned databases) is incorrect because authorization is not typically set during initial provisioning but rather during clone operations.

These methods ensure the clone can be created on authorized servers.

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Authorizing Database Servers for Clones

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

Answer : B

Before registering a SQL Server VM with Nutanix Database Service (NDB), the administrator must ensure that the VM is configured to allow NDB to communicate with and manage it. For SQL Server VMs running on Windows, NDB relies on Windows Remote Management (WinRM) to facilitate remote administration, discovery, and management tasks. WinRM is a Microsoft protocol that enables secure communication between the NDB control plane and the Windows-based database server VM. It must be enabled and properly configured (e.g., with HTTP or HTTPS listeners and appropriate firewall rules) to allow NDB to register the VM and perform operations like provisioning, patching, or cloning.

Option A (Secure Shell - SSH) is incorrect because SSH is a protocol primarily used for Linux-based systems, not Windows-based SQL Server VMs. NDB uses WinRM for Windows environments.

Option B (Remote Management - WinRM) is correct as it aligns with NDB's requirements for managing Windows VMs hosting SQL Server instances.

Option C (Remote Desktop - RDP) is incorrect because RDP is a protocol for interactive desktop access, not for the automated management and communication required by NDB.

Option D (Windows PowerShell) is incorrect as a standalone answer. While PowerShell can leverage WinRM for remote execution, NDB specifically requires WinRM to be enabled as the underlying service, not just PowerShell itself.

To verify WinRM is enabled, the administrator can run winrm quickconfig on the SQL Server VM or check the service status and firewall settings. NDB documentation emphasizes this prerequisite to ensure successful registration and management of SQL Server VMs.

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

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

Nutanix Support & Insights, Technical Note: 'Preparing Windows VMs for NDB Registration'