Nutanix NCP-DB - Nutanix Certified Professional - Database Automation (NCP-DB v7.5)

 In the context of Nutanix Database Automation (NCP-DB), a Super Admin has the authority to apply patch profiles. However, if a patch is marked as deprecated, even if it’s published, it cannot be applied. This is because deprecation is a status that indicates the patch is outdated or has been superseded by a newer version, and thus should not be used1. This behavior ensures that only the most up-to-date and secure patches are applied to the system, maintaining the integrity and security of the database environment1.

 The correct answer is A because NDB handles the database restore operation by copying the specific database files from the snapshot volume to the source volume, without affecting the other databases that share the same source volume. NDB uses a copy-on-write mechanism to create snapshots and clones, which means that only the changes made to the database files are stored in the snapshot or clone volume, while the original files are kept in the source volume. Therefore, when restoring a source database from a snapshot, NDB only needs to copy the specific database files that have been modified since the snapshot was taken, and overwrite them on the source volume. The other options are not correct because they either cause data loss or unnecessary data transfer. Option B is not correct because replacing the source volume with specific db disks would erase the other databases that share the same source volume, which is not desirable. Option C is not correct because replacing the source volume with the snapshot volume would also erase the other databases that share the same source volume, as well as any changes made to the source database after the snapshot was taken, which is not desirable. Option D is not correct because copying all database files to the source volume would be inefficient and unnecessary, as only the modified files need to be copied, and the other files are already present on the source volume. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, [Nutanix Support & Insights]

Nutanix NDB provides the ability to create highly-available (HA) database pairs, leveraging replication and failover across clusters. The two databases explicitly supported for HA pairs in NDB are PostgreSQL and SQL Server. NDB orchestrates HA for PostgreSQL using streaming replication and for SQL Server using Always On Availability Groups or Failover Cluster Instances, ensuring data redundancy and failover capabilities across Nutanix clusters.

Other options are not supported for HA pairs:

A. MySQL: MySQL is supported by NDB but lacks native HA pair configuration.

D. MariaDB: Similar to MySQL, MariaDB is managed by NDB but does not support HA pairs.

Thus, the verified answers are B and C, reflecting NDB’s HA capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.1: Configuring HA for Databases.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.1: Configure HA for Supported Databases (applicable to v7.5).

Nutanix NDB Administration Guide: "High Availability Supported Databases" section.

The correct answer is B because it allows the administrator to create a custom role with the specific privileges that the Jr DBA user needs, and then assign that role to the user. This way, the administrator can control the access level of the Jr DBA user without affecting the existing roles or users in NDB. Option A is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then adding more privileges, which is unnecessary and redundant. Option C is incorrect because it involves creating a user for the Jr DBA, but not assigning a role to the user, which means the user will not have any privileges in NDB. Option D is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then removing some of the privileges, which is inefficient and risky.

The following sources provide more information about the user roles and privileges in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 8: Administering an NDB Environment, Lesson 8.6: Managing Access Controls in NDB

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

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

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 References

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) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.5: Manage NDB Security (applicable to v7.5).

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

To roll back an Oracle patch on a database server VM using NDB, the patch must have been applied using NDB in the first place. This is because NDB maintains a patch inventory and history for each database server VM and database that it manages. NDB uses this information to determine which patches can be rolled back and how to revert the changes made by the patch. If the patch was applied outside of NDB, NDB would not have the patch information and would not be able to roll back the patch. Therefore, the patch must have been applied using NDB for the rollback action to be successful. The other options are not required for the rollback action. The database does not need to be shut down or in read-only mode, as NDB can perform the rollback operation online. The patch does not need to be applied on Grid home only, as NDB can roll back patches applied on both Grid home and Database home. References:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 4 - Operate and Maintain an NDB Environment, Objective 4.4: Determine the correct method to apply Linux OS patches

Nutanix Database Management & Automation (NDMA) Course, Module 5: Nutanix Database Service (NDB) Patching, Lesson 5.1: Patching Overview, Topic: Patching Concepts

[Nutanix Database Service (NDB) User Guide], Chapter 7: Patching, Section: Rolling Back a Patch

NDB supports SQL Server database groups so multiple databases can share one Time Machine and a coordinated protection schedule. Nutanix documents a maximum selection of 35 databases for group-registration workflows and states that Microsoft recommends no more than 35 databases in one database group. A SQL Server database server VM or cluster can contain as many as five NDB database groups. The efficient design for 90 databases is therefore three groups—for example, 35, 35, and 20 databases—with one Time Machine for each group. A single 90-database group exceeds the supported or recommended size, while creating 90 individual Time Machines or relocating databases to other servers introduces unnecessary operational overhead. Therefore, option B is correct. Nutanix SQL Server database-group documentation

NDB supports SMTP server configuration for sending email notifications and alerts. SMTP server configuration requires specifying the SMTP server address, port, username, password, and encryption method. The encryption method determines how the email messages are secured during transmission. NDB supports two encryption methods for SMTP server configuration: TLS and SSL.

TLS (Transport Layer Security) is a protocol that encrypts and authenticates data between the email client and the SMTP server. TLS can operate in two modes: explicit and implicit. In explicit mode, the email client and the SMTP server negotiate the encryption method and parameters after establishing a plain text connection. This mode typically uses port 587. In implicit mode, the email client and the SMTP server assume that the connection is encrypted from the start, without any negotiation. This mode typically uses port 465.

SSL (Secure Sockets Layer) is a predecessor of TLS that also encrypts and authenticates data between the email client and the SMTP server. SSL operates in implicit mode only, and uses port 465 by default. SSL is less secure than TLS, but it is still widely used and supported by many email providers.

S/MIME (Secure/Multipurpose Internet Mail Extensions) is a standard that encrypts and signs email messages at the application layer, rather than the transport layer. S/MIME requires the use of digital certificates and public key cryptography to ensure the confidentiality and integrity of email messages. S/MIME is not a valid encryption method for SMTP server configuration, as it does not affect the connection between the email client and the SMTP server.

IPsec (Internet Protocol Security) is a suite of protocols that secures IP packets at the network layer, rather than the application or transport layer. IPsec can encrypt and authenticate data between any two IP endpoints, such as routers, firewalls, or hosts. IPsec is not a valid encryption method for SMTP server configuration, as it does not apply to the specific protocol or port used by SMTP.

Nutanix Database Automation (NCP-DB) Course Details, Section 1.4: NDB Alerts and Notifications

Nutanix Database Automation (NCP-DB) Certification Details, Objective 1.4: Configure NDB Alerts and Notifications

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 1.4: NDB Alerts and Notifications

[Nutanix Database Automation (NCP-DB) User Guide], Section 1.4: Configure SMTP Server Settings

The NDB database agent is a service that runs on each database server VM and communicates with the NDB instance. It uses port 443 for HTTPS API calls and port 9440 for Nutanix cluster API calls. These ports are required to be open on the database server VMs for NDB to function properly. References: Nutanix Database Management & Automation (NDMA), page 9; Ports and Protocols Reference Chart | Nutanix Community, section “Nutanix Database Service (NDB)”

Failed NDB provisioning workflows normally perform a rollback that removes resources created during the unsuccessful operation, including the database server VM. For troubleshooting, the administrator can enable the global skip_rollback_global setting so that NDB does not execute this cleanup path. The failed VM is then preserved for inspection of its operating-system state, logs, network configuration, and database installation artifacts. Nutanix Support states that automatic deletion occurs only when delete_vm_on_failure is true and skip_rollback_global is false; other combinations preserve the VM and require manual cleanup afterward. Because the question specifically asks which global rollback option must be enabled, skip_rollback_global is the correct selection. It should be returned to its normal value after troubleshooting to avoid abandoned resources. Nutanix KB 14629