NCP-DB-7.5 Exam Preparation Material | Nutanix Certified Professional - Database Automation v7.5

Explanation:
NDB uses Oracle out-of-place patching for Oracle database software. Instead of modifying the actively used Oracle home directly, NDB prepares or uses a separate Oracle home containing the required patched software and then moves the database to that home through an orchestrated workflow. This method keeps the original Oracle home available and reduces the risks associated with changing production binaries in place. It also supports more predictable patching and recovery procedures because the old and new software homes remain logically separated. Binary synchronization and in-memory synchronization are not Oracle patching methods used by NDB. In-place patching would directly modify the existing Oracle home and therefore does not describe the documented NDB workflow. Nutanix explicitly states that NDB uses out-of-place patching in its official Oracle database patching documentation.

Explanation:
According to the Nutanix Database Automation (NCP-DB) course, the Pre-Post Commands section allows the administrator to specify custom scripts that can be executed before or after the clone operation1. The masking script can be created on any of the VMs that have access to the source database, such as the source DB VM, the Dev VM, or the SW Profile VM2. The script should contain the commands to mask the sensitive data in the Finance database, such as replacing the real values with dummy values or encrypting the data2. The administrator can then create the clone from the Time Machine and define the post-clone option with the full path and name of the masking script1. This will ensure that the script is executed after the clone is created, and the data is masked before it is available for the development team1. The other options are not correct, as they either use the wrong field (pre-clone instead of post-clone), or do not specify where to create or store the masking script .
References:
1: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 5
2: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 7

Explanation:
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

Explanation:
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) v7.5Knowledge Objectives, Section 4:
Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v7.5).
Nutanix NDB Administration Guide: "Supported Database Engines for HA" section, highlighting PostgreSQL multi-cluster support.

Explanation:
NDB profiles are scoped by database engine and deployment type. A Network Profile identifies the VLAN and related network settings that NDB can use when creating a database server VM. Merely registering the Nutanix cluster does not create a usable engine-specific Network Profile. If the provisioning wizard for a particular engine displays no networks, the most likely missing object is the Network Profile created under that database engine. DHCP or static addressing is a configuration choice inside the profile; neither is universally required, so the absence of one addressing mode does not explain an empty list by itself. A database HA component profile would be relevant only to the corresponding HA topology, not ordinary engine provisioning .
Therefore, the administrator must create or make available a Network Profile for the specific database engine. Nutanix documents this engine-specific workflow under NDB Profiles.