NCP-DB Nutanix Certified Professional - Database Automation (NCP-DB v6.10) Questions and Answers

A Time Machine frozen status indicates that the database that was associated with the Time Machine has been de-registered from NDB, but the Time Machine itself has not been deleted. This means that the Time Machine still contains the snapshots and logs of the de-registered database, but it cannot perform any further operations on it. To resume the normal functioning of the Time Machine, the administrator can either re-register the database with NDB, or delete the Time Machine and free up the storage space.

References: Nutanix Support & Insights, section “Resolving All Alerts for a Time Machine”

Before registering a SQL Server Single Node Database Server VM with NDB, it is necessary that the login account provided for this task must be a member of the sysadmin role. This ensures the necessary permissions are in place for managing and administering the SQL Server instance.References: Nutanix Database Automation documentation, under SQL Server database registration and permission requirements.

Ports 3205 and 3260 are important when working with Era because they must be open on the Era server and all Controller VMs (CVMs) to facilitate iSCSI connections1. Specifically, port 3205 is used for iSCSI redirection2. Please be careful of routing iSCSI traffic, as it could impact performance2.

For a One-Click Upgrade of an NDB environment with internet access, the patch should be downloaded directly within the NDB interface. The "Administrator > Maintenance" section of NDB provides an option to connect to the Nutanix download repository (e.g., https://download.nutanix.com) and download the latest patch or upgrade bundle automatically. This streamlined process ensures compatibility and simplifies the upgrade workflow. The One-Click Upgrade feature then applies the downloaded patch to update NDB components efficiently.

Other options are incorrect:

A. Download the patch from the Nutanix Support Portal and upload via the NDB CLI: This is suitable for dark sites but unnecessary with internet access, as NDB can download directly.

C. Open Prism Central and deploy the current version of NDB from the Apps and Marketplace section: This is for initial deployment, not upgrading an existing NDB instance.

D. Open Prism Element and use LCM to update the software: Lifecycle Manager (LCM) is for Nutanix cluster updates, not NDB-specific upgrades.

Thus, the verified answer is B, leveraging NDB’s built-in maintenance capabilities.

Official Nutanix Database Automation References

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

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: "One-Click Upgrade Process" section.

In an NDB HA (High Availability) setup, when planning an electrical maintenance window requiring the clusters hosting NDB to be powered off, the administrator must follow a controlled shutdown sequence to preserve data integrity and minimize disruption. After shutting down the load balancer server (HAProxy), the next step is to shut down the API standby node. In an NDB HA configuration, the API leader node handles active operations, while the standby node provides redundancy. Shutting down the standby node first ensures the leader remains operational, allowing ongoing management tasks to continue until the final shutdown of the leader node.

Option A (In the sudo systemctl stop patroni command) is incorrect because Patroni is used for PostgreSQL HA, not NDB HA node management.

Option B (Shutdown the API standby node) is correct as it follows the recommended HA shutdown order, preserving active services.

Option C (Run the high-availability list command) is incorrect because this is a diagnostic command, not a shutdown step.

Option D (Shutdown the API leader node) is incorrect because the leader should be the last node shut down to maintain service availability.

This sequence ensures a graceful shutdown of the NDB HA environment.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Managing HA Shutdown Procedures

Nutanix Support & Insights, Knowledge Base Article: "Shutting Down NDB HA During Maintenance"

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

To create a software profile version for a newly-released Oracle ISc patch, an administrator should follow these steps:

Download the required patch from MyOracle Support1. This is because Oracle patches are typically available from MyOracle Support, not Microsoft Support.

Apply the patch to the Oracle Home/Grid Home on a cloned VM of the gold image using OPatchAuto1. OPatchAuto is a utility provided by Oracle that automates the process of applying patches to a database.

Ensure success of patch application1. It’s important to verify that the patch has been applied successfully to avoid any issues down the line.

Create a new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era GUI1. This step is necessary to ensure that the new patch is included in the software profile.

Mark the original patch profile as hidden1. This step is optional but can be useful for keeping the software profile clean and organized.

Please note that these answers are based on the information available as of my last update in 2021 and may need to be verified with the most recent Nutanix Database Automation (NCP-DB) documentation or resources.

When consolidating Microsoft SQL Server instances on database server VMs managed by NDB using a medium compute profile, concerns about DB storage capacity can arise due to increased demand. In NDB, the appropriate task to address this is to "Update the Database Server VMs," which allows the administrator to adjust resource allocations, including storage capacity, for the VMs hosting the databases. This task can be performed within the NDB interface to expand disk space or reconfigure storage settings without altering the compute profile or requiring external tools.

Option A (Update the Database server VMs) is correct as it provides a direct method in NDB to modify VM resources, including storage.

Option B (Expand vDisk in Prism Element) is incorrect because NDB manages database VMs holistically, and storage expansion should be handled through NDB’s Update task rather than Prism Element directly.

Option C (Update the compute profile) is incorrect because compute profiles define CPU and memory, not storage capacity.

Option D (Scale the source database) is incorrect as scaling typically refers to database-level adjustments (e.g., adding nodes), not VM storage expansion.

This approach ensures seamless integration with NDB’s management framework.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Updating Database Server VMs

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Servers

In Nutanix Era, an administrator can modify the Alert Severity level by navigating to the Alerts Policies from the dropdown menu. Once there, they can select the Policy that needs to be modified and set the desired severity level1. This allows the administrator to customize the alerts according to their requirements, ensuring that they are notified of the most critical events in their environment21.

According to the Nutanix Database Automation (NCP-DB) learning documents, to create a network profile in Era, the network must be added to Era1. This is because Era needs to have control over the network in order to manage the databases effectively1. Once the network is added to Era, it can be used for various operations such as provisioning new databases, managing existing databases, and more1.

When registering a Nutanix cluster with the Nutanix Database Service (NDB), the Prism Element user account used for registration must have sufficient privileges to perform cluster-level operations. The recommended role for this task is Cluster Admin. The Cluster Admin role in Prism Element provides the necessary permissions to manage cluster resources, including storage, networking, and integration with external services like NDB. This role is required because registering a cluster with NDB involves tasks such as establishing connectivity, validating configurations (e.g., Data Services IP), and ensuring that NDB can interact with the cluster’s Controller VMs and storage infrastructure.

The default administrative account in Prism Element (typically "admin") often serves as the initial Cluster Admin user. However, if an administrator needs to remove or replace this default account for NDB operations, a new user with the Cluster Admin role must be created and used instead. Other roles listed have different purposes:

Super Admin: This is not a standard role in Prism Element; it may refer to elevated privileges in other contexts but is not specifically defined for Nutanix cluster registration.

User Admin: This role is limited to managing users and permissions, lacking the broader cluster management capabilities needed for NDB registration.

Backup Admin: This role is specific to backup-related tasks and does not encompass the full scope of cluster management required for NDB integration.

Therefore, the Cluster Admin role is the recommended and verified choice for registering a Nutanix cluster with NDB, ensuring seamless operation and management.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster with NDB.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix cluster in NDB (applicable to v6.10 with no significant role changes documented).

Nutanix Prism Element Guide: "Role-Based Access Control (RBAC)" section, detailing Cluster Admin privileges.

To add Time Machine data access to a Nutanix cluster, the first step is to register the cluster in NDB. This will allow NDB to discover and manage the databases and snapshots on the cluster. You can register multiple Nutanix clusters in NDB using the Add Cluster option in the NDB settings page. You can also specify the cluster role, such as source, target, or both, depending on the data access and replication needs. Enabling or disabling multi-cluster in NDB is not the first step, as this is a global setting that affects the entire NDB instance. Deleting the TM data from the source database is not the first step, as this will remove the data protection and availability of the database. References:

Nutanix Database Management & Automation Training Course, Module 6: Managing NDB Multi-Cluster, Lesson 1: NDB Multi-Cluster Overview, Slide 5: Registering Nutanix Clusters

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 6: Administer an NDB Environment, Objective 6.4: Apply procedural concepts to add Nutanix clusters to NDB

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

Nutanix Era is a database management solution that automates and simplifies database administration tasks such as provisioning, patching, cloning, and backup. In the event of a database crash, the most effective way to minimize data loss and reduce restore time is to perform a restore of the source database by selecting the most recent point in time and including the Tail log Backup12.

The Tail log Backup includes all the transactions that have occurred since the last transaction log backup, which helps to minimize data loss. By selecting the most recent point in time for the restore, the administrator ensures that the database is restored to the state it was in just before the crash, thereby reducing the amount of data that needs to be reprocessed or reentered12. This approach aligns with the Nutanix Era’s capabilities and best practices for database recovery12.

NDB High Availability (HA) is a feature that ensures the availability and reliability of the NDB management plane components, such as the API Server, the Repository VMs, and the NDB Agents. To enable NDB HA, you need to deploy at least three HA Proxy VMs on the same L2 network as the NDB Server VM. The HA Proxy VMs act as load balancers and health monitors for the NDB management plane components, and they also provide a single endpoint for accessing the NDB APIs and UI. References:

Nutanix Certified Professional - Database Automation (NCP-DB), Section 2 - Deploy and Configure an NDB Solution

Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 7, Objective 2.3

Nutanix Database Management & Automation (NDMA) course, Module 2, Lesson 2.3 - NDB High Availability

In Nutanix Database Service (NDB), patching Oracle database engines requires the "Update" button to be available on the database server VM’s management interface. If this button is missing, it typically indicates a configuration issue preventing NDB from performing the patching operation. The most common and critical reason is that the operating system (OS) credentials for the database server VM have not been set or registered with NDB. These credentials are necessary for NDB to authenticate and execute patching tasks on the VM, such as accessing the Oracle software and applying updates via a software profile.

Option A is correct because missing OS credentials prevent NDB from establishing the required connection to the VM, disabling the Update button.

Option B (Database parameters are missing) is incorrect because while database parameters are important for configuration, they do not directly control the visibility of the Update button for patching.

Option C (Oracle DB engines cannot be patched) is incorrect as NDB explicitly supports patching Oracle databases when properly configured.

Option D (Software profile is not published) is incorrect because an unpublished software profile might limit availability to users, but the Update button’s presence relies on VM connectivity, not profile publication status.

To resolve this, the administrator must register valid OS credentials for the VM in NDB, enabling the patching functionality.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Patching Database Engines

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Missing Update Button in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles

The default continuous recovery for the Gold SLA in Era Time Machine is 30 days1. This means that the system keeps a continuous recovery point for the last 30 days, allowing you to restore your database to any point within this period1.

Nutanix Era enables you to clone your source databases and refresh the database clones by using snapshots or transaction logs1. For an online retail application that requires data to be synchronized between multiple SQL Server databases, having all the databases present in the same Database Virtual Machine (DBVM) and registering them in Era with Multiple Databases as a Group with one Time Machine would be the most efficient way to fulfill this requirement1. This approach allows for clearer reporting from multiple databases at the same time for consistency at the end of each business day1.

In the Nutanix Database Automation (NCP-DB) framework, provisioning a new Oracle database through Era requires the configuration of both a Compute and a Storage profile1. The Compute profile is used to define the resources allocated to the database, such as CPU and memory, while the Storage profile is used to specify the storage configuration for the database. These profiles are essential in ensuring that the database is provisioned with the necessary resources and storage configurations for optimal performance23.

The log frequency in the Era IJI for log catchup operation can be configured to as low as 5 minutes. This allows the system to capture changes to the database at a high frequency, enabling more precise point-in-time recovery options. However, it’s important to note that a higher frequency of log catchup operations can lead to increased system load. Therefore, the optimal frequency may vary depending on the specific requirements and capabilities of your system12. Please refer to the Nutanix Database Automation (NCP-DB) Learning documents for more detailed information.

An NDB compute profile defines the CPU and memory resources for the database server VMs that are provisioned using NDB. It does not include any information about the network, domain, or software of the database server VMs. Those are specified in separate profiles, such as network profile, domain profile, and software profile.

References: Nutanix Support & Insights, section “NDB Compute”

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 References

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.

NDB Multi-Cluster is a feature that allows multiple Nutanix clusters to share a common NDB service for database management and automation. NDB service consists of two components: NDB Server and NDB Agent. NDB Server is the central component that provides the web UI, REST API, and database orchestration logic. NDB Agent is the component that runs on each Nutanix cluster and communicates with the NDB Server to perform database operations.

When NDB Multi-Cluster is enabled on Cluster A, it becomes the primary cluster that hosts the NDB Server VM. Cluster B, which is registered with NDB, becomes a secondary cluster that hosts only the NDB Agent VM. Therefore, Cluster A has both NDB Server and NDB Agent, while Cluster B has only NDB Agent. This configuration allows Cluster B to leverage the NDB service running on Cluster A for database management and automation.

References:

Nutanix Database Automation (NCP-DB) Course Details, Section 3.1: NDB Multi-Cluster Overview

Nutanix Database Automation (NCP-DB) Certification Details, Objective 3.1: Configure NDB Multi-Cluster

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 3.1: NDB Multi-Cluster Overview

NDB supports high availability (HA) across multiple Nutanix clusters, including those in separate data centers, by replicating data and ensuring failover capabilities. However, NDB imposes strict network latency requirements for HA. The official documentation specifies that the round-trip time (RTT) latency between clusters should not exceed 25ms for HA to function effectively. If the latency between two clusters exceeds this threshold (e.g., due to geographic distance or network issues), HA cannot be enabled, as the synchronization and failover mechanisms rely on low-latency communication to maintain consistency and performance.

Impact of other options:

A. HA will operate with increased delay: While latency might cause delays, exceeding 25ms RTT prevents HA setup entirely, not just delays its operation.

C. The clusters will not synchronize: Synchronization issues may occur as a symptom, but the primary impact is HA enablement failure.

D. There will be no impact on HA functionality: This is incorrect, as latency beyond 25ms RTT violates HA prerequisites.

Thus, the verified answer is B, reflecting NDB’s latency constraints for HA across clusters.

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: "High Availability Configuration Requirements" section, specifying latency limits.

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.

When a database is de-registered from NDB without removing the associated Time Machine, the Time Machine enters a "Frozen" state. In this state, the Time Machine retains all existing snapshots and protection data but ceases to perform new snapshot captures or log catch-up operations. This allows the administrator to preserve the historical data for potential future use (e.g., auditing or recovery) while halting active management. The Frozen state prevents further modifications until the database is re-registered or the Time Machine is explicitly deleted.

Option A (Ready) is incorrect because "Ready" implies the Time Machine is active and prepared for new operations, which is not the case post-de-registration.

Option B (Frozen) is correct as it reflects the paused protection state after de-registration without removal.

Option C (Paused) is incorrect because "Paused" is not a formal Time Machine state in NDB; "Frozen" is the specific term.

Option D (Active) is incorrect because the Time Machine cannot remain active without an associated registered database.

This state provides flexibility for data retention without ongoing resource use.

References

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

Nutanix Support & Insights, Knowledge Base Article: "Understanding Time Machine States After De-registration"

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

To replicate database snapshots to remote Nutanix clusters, the administrator needs to add Data Access to each Nutanix cluster and assign a Data Availability Management (DAM) policy. Data Access is a feature of NDB that enables cross-cluster data mobility and protection. A DAM policy defines the replication frequency, retention period, and priority of the database snapshots across the clusters. By adding Data Access to each Nutanix cluster and assigning a DAM policy, the administrator can manage the Time Machine data availability across all registered Nutanix clusters in NDB.

References: Nutanix Support & Insights, section “NDB Data Access”

Option A: Nutanix Era requires network prerequisites like NTP, DNS servers, gateway, and subnet mask to be available and visible. These are essential for the proper functioning of the Era instance1.

Option B: One static IP address must be available and can be changed using CLI after VM deployment. This is necessary for the Era VM to communicate with other components in the network1.

Option C: While a storage container is necessary for Nutanix infrastructure, it is not a network prerequisite specifically for deploying an Era instance.

Option D: An SMTP server and details are typically used for sending notifications, but they are not a network prerequisite for deploying an Era instance. They are more related to the operational aspect post-deployment.

The Nutanix Era platform provides a feature called Time Machine, which is designed to manage the lifecycle of database copies and clones1. When a new table is added to the source database, the administrator should perform a Log Catch-up using the source database’s Time Machine. This action ensures that the Time Machine captures the latest state of the source database, including the newly added table1. After performing the Log Catch-up, the administrator should refresh the clone database. The refresh operation updates the clone with the latest state captured by the Time Machine, thereby publishing the new table to the clone1.

 Nutanix Era enables you to clone your source databases (running on Nutanix clusters) and refresh the database clones by using snapshots or transaction logs1. Era uses storage-efficient and time-efficient Nutanix snapshots, thus lowering the cost of managing multiple copies of your databases1. In this case, the administrator should create a clone from the July 31st snapshot in Time Machine to provide the legal team with the specific banking transaction event data they need for their audit1.

The recovery plans policy defines the Time Machine data availability across multiple registered clusters in NDB. The recovery plans policy allows the database administrator to specify the source and target clusters, the frequency and retention of the cross-cluster snapshots, and the network and compute profiles for the recovery operations. The recovery plans policy helps to ensure the disaster recovery and business continuity of the NDB-managed databases in case of a cluster failure or outage.

The data access management policy defines the access permissions and roles for the NDB users and groups. The data access management policy allows the database administrator to grant or revoke access to the NDB instance, the database server VMs, the databases, and the database operations. The data access management policy helps to ensure the security and compliance of the NDB-managed databases and users.

The data protection policy defines the backup and restore settings for the NDB-managed databases. The data protection policy allows the database administrator to specify the frequency, retention, and compression of the database snapshots, and the backup location and encryption for the database backups. The data protection policy helps to ensure the backup and recovery of the NDB-managed databases within the same cluster.

The service level agreements policy defines the performance and availability metrics for the NDB-managed databases. The service level agreements policy allows the database administrator to monitor and enforce the database uptime, latency, throughput, and IOPS. The service level agreements policy helps to ensure the quality of service and performance of the NDB-managed databases.

References:

Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slide 9.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 8, 12, 16, 20.

Nutanix Database Management & Automation Training Course, Module 6: Nutanix Era Disaster Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 5-7.

The exhibit shows the NDB user management interface with a newly created user named "ndb_test" assigned the "Database Infrastructure Admin" role and sourced as a "Local User." In NDB, the "Database Infrastructure Admin" role grants specific permissions, allowing the user to manage database-related tasks such as creating, managing, and deleting clones, as well as performing configuration tasks within the NDB environment (e.g., updating settings or managing database servers). However, this role does not extend to higher-level administrative functions like Access Control or Network Profiles, which are reserved for roles with broader administrative privileges (e.g., System Administrator).

Option A (Access Control) is incorrect because managing user access and roles requires a higher privilege level, such as System Administrator, not Database Infrastructure Admin.

Option B (Network Profiles) is incorrect because configuring network profiles is an administrative task outside the Database Infrastructure Admin scope.

Option C (Clones) is correct as the Database Infrastructure Admin role includes permissions to create and manage clones using Time Machine.

Option D (NDB Configuration) is correct as this role allows configuration of database-related settings within NDB, such as registering VMs or adjusting database parameters.

Thus, the "ndb_test" user can perform clone management and NDB configuration tasks.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: User Roles and Permissions

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

According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era is a database management tool that automates and simplifies database operations, including provisioning, patching, upgrading, and more1. However, for a database to be managed by Era, it must be registered with Era1. This means that if a database is on a non-Nutanix platform, it cannot be directly upgraded using an Era workflow. It must first be migrated to a Nutanix platform and registered with Era before it can be managed and upgraded using Era1.

The NDB user interface supports multiple languages, including English, Chinese, and Japanese. You can change the language preference in the NDB settings page. The NDB user interface does not support Korean, French, or German languages at this time. References:

Nutanix Database Management & Automation Training Course, Module 1: Introduction to Nutanix Era, Lesson 1: Nutanix Era Overview, Slide 7: NDB User Interface

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 1: Describe NDB Concepts, Objective 1.6: Languages

Nutanix Era is a database management system that provides API endpoints for automation and integration with external applications. These API calls are typically made over HTTPS for security, and the standard ports for HTTPS are 443 and 94401. Please note that the actual ports used can depend on the specific configuration of the Nutanix Era system. It’s always a good idea to check the system’s documentation or consult with the system administrator for the most accurate information.

When an administrator cannot proceed with the first step of the wizard to provision a new Oracle single instance database in NDB, the most likely reason is that a software profile for Oracle is missing. NDB requires a software profile (which defines the database version, patches, and configuration) to provision a database instance. Without a profile created from a reference VM or uploaded manually, the wizard cannot proceed, as it relies on this profile to configure the instance correctly.

Option A (Time Machine is not configured) is incorrect because Time Machine is optional for backups and not required for initial provisioning.

Option B (Software profile is missing) is correct as it is a mandatory prerequisite for provisioning any database instance.

Option C (No remote clusters are configured) is incorrect because remote clusters are relevant for multi-cluster setups, not single instance provisioning.

Option D (A snapshot must be taken on the original DB) is incorrect because snapshots are for protection, not a prerequisite for provisioning.

The administrator must create or import a software profile to resolve this issue.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Provisioning Databases

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

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles

When an Oracle database is upgraded using Era, the type of upgrade category is an “In-place upgrade”. This method involves upgrading the database software within the same Oracle home as the existing database. The AutoUpgrade utility is used to automate the upgrade process, both before starting upgrades, during upgrade deployments, and during post-upgrade checks and configuration migration1. This method is preferred due to its simplicity and efficiency1.

To create an NDB Software Profile Version for PostgreSQL, it is required to have an installer package for the database software. This package forms the basis of the software profile, enabling the deployment and management of PostgreSQL instances.References: Nutanix Database Automation documentation, particularly in the area of software profile creation and management for PostgreSQL.

The correct answer is D because it meets the requirements of maintaining five days of time-travel capability to any second and an additional seven days of discrete recovery at a daily interval. Continuous log retention allows the administrator to restore the database to any point in time within the specified number of days, while snapshot retention allows the administrator to restore the database to a specific point in time at a fixed interval. Therefore, by setting the daily snapshot retention to 7 days, the administrator can ensure that there is a discrete recovery point for each day of the week. By setting the continuous log retention to 5 days, the administrator can ensure that there is a time-travel capability to any second within the last five days. The other options do not meet the requirements because they either have less than five days of continuous log retention or less than seven days of snapshot retention. 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 Certified Professional - Database Automation (NCP-DB) datasheet

To add multiple databases to an existing PostgreSQL instance managed by NDB, the administrator should use the NDB graphical user interface (GUI). The GUI provides a user-friendly way to modify the parameter profile associated with the PostgreSQL instance, allowing the addition of new databases by adjusting settings such as database names, sizes, or configurations. This process typically involves navigating to the "Databases" or "Instances" section, selecting the PostgreSQL instance, and editing the parameter profile to include additional databases.

Other options are less appropriate:

A. Modify parameter profile using ncli: The ncli (Nutanix Command Line Interface) is used for cluster-level management in Prism, not for NDB database configuration.

C. Modify parameter profile using post script: Post-scripts are used for custom actions post-provisioning, not for modifying parameter profiles to add databases.

D. Modify parameter profile using NDB CLI: While NDB has a CLI, the GUI is the recommended and supported method for such configuration changes, offering a guided workflow and validation.

Thus, the verified answer is B, leveraging the NDB GUI for ease and compliance with best practices.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.4: Modifying Database Configurations.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.3: Modify Parameter Profiles (applicable to v6.10).

Nutanix NDB Administration Guide: "Managing PostgreSQL Instances" section, detailing GUI-based modifications.

 According to the Nutanix Database Automation (NCP-DB) learning documents, when provisioning a new database, there are two options available for the target12:

Provision database to an existing registered: This option allows you to provision a database to an existing registered database server. This is useful when you want to add a database to a server that is already being managed by Nutanix Era1.

Provision databases to a new container: This option allows you to provision a database to a new container. This is useful when you want to create a new isolated environment for your database1.

The exhibit shows an error during the provisioning of NDB from the Prism Central Marketplace, with a failure reason stating "IP not found" in the "EraService - Substrate Create" step. This indicates that the provisioning process could not assign or detect an IP address for the NDB instance, likely due to an unconfigured or missing IP address during deployment. To prevent this issue, the administrator should configure an IP address when deploying the application. This involves specifying a static IP or ensuring IP Address Management (IPAM) is properly set up to allocate an IP during the Prism Central Marketplace deployment wizard.

Other options are less directly relevant:

B. Import the proper image in the Prism Central: This ensures the correct NDB image is available but does not address the IP assignment issue.

C. Provide a subnet with IP Address Management: While useful, this is a broader configuration step and not the specific action needed during deployment.

D. Register NDB using the correct IP address: Registration occurs after deployment and does not prevent the initial IP assignment failure.

Thus, the verified answer is A, as configuring the IP address during deployment directly addresses the "IP not found" error.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.2: Deploying NDB from Prism Central.

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

Nutanix NDB Installation Guide: "Deploying NDB via Prism Central Marketplace" section, emphasizing IP configuration.

To view information about all roles and the number of users assigned to each in NDB, the user must belong to the Super Administrator role. This role provides full administrative privileges, including access to the "Users and Roles" section of the NDB GUI, where role assignments and user counts are visible. Lower-tier roles (e.g., Database Infrastructure Administrator, Database Administrator, Infrastructure Administrator) have limited scopes and cannot access this comprehensive role/user overview.

Other options are insufficient:

A. Database Infrastructure Administrator: Manages infrastructure but not role/user details.

B. Database Administrator: Focuses on database operations, not user management.

C. Infrastructure Administrator: Handles cluster resources, not role/user analytics.

Thus, the verified answer is D, requiring the highest privilege level.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.4: Managing Users and Roles.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.3: Manage User Permissions (applicable to v6.10).

Nutanix NDB Administration Guide: "Role-Based Access Control (RBAC)" section, detailing Super Administrator privileges.

Configuring VM Host Affinity in a Nutanix AHV-powered cluster ensures that VMs are placed on specific hosts to optimize performance or HA. However, after a host failure, if database VMs cluster on a single remaining host, it indicates that the affinity rules alone are insufficient to maintain high availability (HA) during failover scenarios. To prevent this, the administrator should configure anti-affinity rules, which dynamically ensure that VMs (e.g., database server VMs) are spread across multiple hosts. Anti-affinity rules override default VM placement behavior during failover, reducing the risk of a single point of failure by keeping VMs separated even after a host outage.

Option A (Assign additional backup VMs on the same host) is incorrect because placing backups on the same host increases risk rather than mitigating it.

Option B (Increase affinity zones) is incorrect as "affinity zones" is not a standard Nutanix term in this context, and it does not address dynamic VM separation.

Option C (Configure automatic host failover in Prism Central) is incorrect because while failover is managed by AHV, it does not inherently prevent VMs from clustering without specific rules.

Option D is correct as anti-affinity rules proactively distribute VMs, enhancing HA in failure scenarios.

This approach leverages Nutanix AHV’s VM placement policies to ensure resilience.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring VM Affinity and Anti-Affinity

Nutanix AHV Administration Guide, Section: VM High Availability and Placement Rules

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

To enable iSCSI connections between the Nutanix Database Service (NDB) server, Controller VMs (CVMs), and Prism Element, a Data Services IP must be configured in Prism Element. The Data Services IP acts as a cluster-wide address that facilitates iSCSI target discovery and connectivity. It is used by Nutanix Volumes (a block storage service) to present storage to external clients or services, such as the NDB server, via the iSCSI protocol. This IP ensures that iSCSI traffic is routed correctly and remains available even if a CVM fails, as ownership of the Data Services IP can move to another CVM in the cluster.

Configuring the Data Services IP is a prerequisite for integrating NDB with a Nutanix cluster, as NDB relies on iSCSI to manage database storage operations like provisioning and cloning. Without this configuration, the NDB server cannot establish the necessary connections to the CVMs for database-related tasks. Options like Virtual IP, Secondary DNS IP, and Backplane IP are not relevant in this context:

Virtual IP: This is typically associated with high-availability setups for applications, not iSCSI connectivity.

Secondary DNS IP: This pertains to network resolution, not storage connectivity.

Backplane IP: This is an internal network IP for cluster communication, not for external iSCSI access.

Thus, the correct and verified answer is the Data Services IP.

Official Nutanix Database Automation References

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

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution (applicable to v6.10 as foundational concepts remain consistent).

Nutanix Support & Insights Portal: "Configuring iSCSI Data Services IP for Nutanix Volumes" (general Volumes configuration applicable to NDB).

 Nutanix Era supports a variety of database engines, including Oracle, PostgreSQL, MySQL, and Microsoft SQL Server1. However, when it comes to rolling back a patch using the Command Line Interface (CLI), this feature is specifically supported for the Oracle database engine1. This allows for efficient validation of critical database updates and simplifies database rollback1. Please note that while Era does provide support for other database engines, the ability to rollback a patch using CLI is currently specific to Oracle1.

 The correct answer is D because it matches the requirement of taking multiple snapshots per day and retaining them for one week. Option A is incorrect because it only takes one snapshot per day, which is not enough for the administrator’s need. Option B is incorrect because it only retains the snapshots for one week, which means the older snapshots will be deleted after seven days. Option C is incorrect because it only takes two snapshots per week, which is not frequent enough for the administrator’s need.

References: The following sources provide more information about the SLA retention policies and how to create and modify them in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases Using Time Machine, Lesson 4.1: Creating and Modifying SLA Retention Policies

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 5 - Protect NDB-managed Databases Using Time Machine

Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section 6.1: Creating and Modifying SLA Retention Policies

When setting up a Time Machine for a newly-provisioned database in NDB, the GUI allows the administrator to configure the frequency of snapshots for data protection. The maximum number of snapshots per day that can be configured in the NDB GUI is 6. This limit ensures a balance between data granularity (for point-in-time recovery) and storage overhead, preventing excessive resource consumption. The administrator can schedule these snapshots at regular intervals (e.g., every 4 hours) within the Time Machine configuration wizard.

Other options are incorrect based on NDB’s design:

A. 4: This is below the maximum supported limit.

C. 8: Exceeds the GUI-configurable maximum.

D. 12: Far exceeds the limit, suggesting manual or unsupported customization.

Thus, the verified answer is B, aligning with NDB’s snapshot scheduling constraints.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.1: Configuring Time Machine.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.1: Configure Time Machine Settings (applicable to v6.10).

Nutanix NDB Administration Guide: "Time Machine Snapshot Scheduling" section.

To apply patches to Microsoft SQL Server databases in an NDB environment, the administrator should follow a structured process:

Create a new software profile version: Download the latest cumulative update (CU) or patch from Microsoft and use it to create a new version of the existing SQL Server Software Profile in NDB. This ensures the patch is integrated into NDB’s management framework.

Publish the updated software profile: Promote the new version to "Published" status, making it available for use across the environment.

Apply the update: Navigate to the "Database VM Menu" for each database server, select the updated software profile, and apply the patch. This automates the patching process while maintaining database consistency and allowing rollback if needed.

Other options are incorrect or incomplete:

A. Create a Maintenance window schedule and associate the SQL server with that maintenance window in the Database VM Menu: Maintenance windows manage downtime, not patch application for databases.

B. Apply the patch to the database VM then create a new software profile using that updated VM as the source: This manual approach bypasses NDB’s structured patching and lacks version control.

C. Apply the patch to the database VM, then create a new software profile version using that updated database VM as the source, publish the updated software profile then apply that patch under the database VM Menu for each database server: This is overly complex and risky, as manually patching a VM first can lead to inconsistencies.

Thus, the verified answer is D, aligning with NDB’s best practices for database patching.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.2: Patching SQL Server Databases.

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: "Patching Microsoft SQL Server" section.

To free up space in the NDB-managed container, the administrator needs to identify storage consumption sources. Two key locations in NDB provide actionable insights:

C. Clone Database table: This displays all clone databases, including their Size (current storage usage) and Last Refresh (indicating age or staleness). Clones often consume significant space, and older or unused ones can be deleted to reclaim storage.

D. Snapshot table in Time Machine: This shows snapshots with details like Reclaimable Space (space recoverable by deletion) and Age (how long snapshots have existed). Old or unnecessary snapshots are prime candidates for reclamation.

Why not the other options?

A. NDB Dashboard (Clone Data Age): While it provides a high-level view, it lacks granular details (e.g., size per clone) needed for targeted reclamation.

B. Source Database grid: This shows registered databases’ size and status but doesn’t focus on derivative objects (clones/snapshots) that typically consume more space.

Thus, C and D are the best locations for detailed storage analysis and reclamation research.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Storage and Resource Management, Lesson 6.2: Monitoring and Reclaiming Storage.

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

Nutanix NDB Administration Guide: "Clone Database Table" and "Time Machine Snapshot Table" sections.

When cloning an SQL database with Transparent Data Encryption (TDE) enabled in NDB, the target server must handle the encryption keys to ensure the cloned database remains functional and secure. TDE uses a keystore (e.g., a bundle file containing the master key and certificate) to encrypt data. Two steps are required: (1) The administrator must back up the keystore bundle file from the source database server VM and transfer it to the target server, ensuring the clone can decrypt the data. (2) After the clone is created, the administrator must run the post-clone command script, which configures the TDE keys on the target server, completes the encryption setup, and activates the cloned database.

Option A (Backup the .cer and .pvk files from the source database server VM) is incorrect because TDE in SQL Server typically uses a keystore bundle, not separate .cer and .pvk files.

Option B (Backup the keystore bundle file from the source database server VM) is correct as it ensures the encryption keys are available on the target.

Option C (Run the pre-clone command script) is incorrect because pre-clone scripts are for preparation, not TDE-specific post-clone setup.

Option D (Run the post-clone command script) is correct as it finalizes the TDE configuration on the target server.

These steps ensure a successful TDE-enabled clone.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Cloning TDE-Enabled Databases

Nutanix Support & Insights, Knowledge Base Article: "Cloning SQL Server with TDE in NDB"

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

After a DBA’s script corrupts an Oracle DB managed by NDB, the administrator needs to restore a clean copy using the latest available snapshot. The most straightforward action is to use the NDB Time Machine feature to select the most recent uncorrupted snapshot and create a new clone. This clone can serve as a restored version of the database, bypassing the corrupted data while leveraging existing snapshots for efficiency.

Option A (Fail the Oracle cluster over to a surviving RAC node) is incorrect because RAC failover is for HA, not corruption recovery via snapshots.

Option B is correct as it uses Time Machine to create a clone from a valid snapshot, addressing the corruption.

Option C (Use Time Machine to create a clone from file-level database backup) is incorrect because NDB primarily uses snapshots, not file-level backups, for cloning.

Option D (Provision a new Oracle DB and perform log catch-up) is incorrect because provisioning a new DB is more complex and unnecessary when a snapshot-based clone suffices.

This method ensures rapid recovery with minimal disruption.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring and Cloning from Snapshots

Nutanix Support & Insights, Knowledge Base Article: "Recovering from Database Corruption in NDB"

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

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.

References

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"

According to the Nutanix Database Automation (NCP-DB) learning documents, to provision a new network in Clusters and extend it to Era, you need to:

B. Add the new subnet and VLAN in Network Configuration in PE1. C. Add the new VLAN in Era Networks1.

These steps ensure that the new network is properly configured in both the Nutanix environment and Era, allowing for seamless communication and operation. Please refer to the official Nutanix documentation and training materials for more detailed information1.

 In Nutanix Era, a Volume Group is the recommended storage provisioning method for a large I/O-intensive database that doesn’t support a multi-disk layout1. A Volume Group in Nutanix Era is a collection of disks that can be managed as a single entity, providing a way to aggregate the storage capacity of multiple disks into a larger storage unit1. This allows for better performance optimization as it enables the database to leverage the combined I/O capabilities of all the disks in the group1. It’s important to note that while other options like Load Balancing, Storage Spaces, and vDisk based provisioning can also be used in certain scenarios, a Volume Group is specifically designed for situations where a single, high-performance storage unit is required1.

To ensure the NDB server, NDB agent, and NDB database agent can communicate with the registered cluster via REST API calls, port 2009 must be opened. This port is used by NDB components to facilitate RESTful communication with the Nutanix cluster (e.g., Prism Element or Prism Central) for operations such as provisioning, monitoring, and management. Proper firewall configuration to allow traffic on this port is a prerequisite for NDB’s integration with the cluster.

Other options are incorrect:

B. 3205: Not a standard NDB port; used for other Nutanix services.

C. 3260: Associated with iSCSI, not REST API communication.

D. 9440: Used for Prism Element’s HTTPS management interface, not NDB-specific REST calls.

Thus, the verified answer is A, reflecting NDB’s REST API requirements.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.1: Network and Port Requirements.

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

Nutanix NDB Installation Guide: "Network Ports and Protocols" section, specifying port 2009.

To install NDB on a Nutanix AHV cluster, you need to download the QCOW2 image file of NDB from the Nutanix Support Portal and upload it to Prism Element. This image file contains the NDB software and the CentOS operating system. After uploading the image, you need to create a VM from the image and configure the network settings. Then, you need to register the NDB VM with Prism Central and enable the NDB service in the settings menu. References: Nutanix Support & Insights, Professional Services: NDB Database Cloning

When performing a SQL Server Restore Source Database operation in Nutanix Database Automation (NCP-DB), an administrator might choose the Restore Location as New Location if they want to restore to a new location and have Era apply Nutanix best practices1. This is because Nutanix Era automates and simplifies database management, allowing the administrator to manage databases at scale, and it applies Nutanix best practices during the restore process1. This ensures optimal performance and reliability of the restored database1.

A database administrator wanting to be notified in advance before any database clones are removed using a removal schedule can configure this directly within the NDB interface. The "Update Removal Schedule" feature includes an option labeled "Create an Alert Before Removal," which is pre-selected as non-optional by default but can be customized. Selecting this option generates an alert (e.g., via email or the NDB dashboard) prior to the scheduled clone removal, allowing the administrator to take action if needed. This is the most efficient and built-in method, avoiding the complexity of custom scripts or reports.

Option A (Create a Playbook to create an alert based on the removal event) is incorrect because a Playbook is an advanced automation tool, not the simplest solution for this notification need.

Option B (Select the Create an Alert Before Removal option) is correct as it is a native NDB feature designed for this purpose.

Option C (Build a custom report in Prism to report on these events) is incorrect because Prism reports are for historical analysis, not real-time notifications.

Option D (Configure SMTP alerts for all actions in NDB) is incorrect because configuring SMTP for all actions is overly broad and less targeted than the specific alert option.

This ensures timely notifications with minimal configuration.

References

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

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

The correct answer is A and D because these are the two Time Machine options that are available when creating a database clone in NDB. Point in time allows the user to specify a date and time to create a clone from a specific point in the database history. Snapshot allows the user to select a previously taken snapshot to create a clone from a consistent state of the database. Option B is incorrect because Restore point is not a Time Machine option, but a feature that allows the user to restore a source database to a previous point in time. Option C is incorrect because Backup is not a Time Machine option, but a feature that allows the user to backup a database to a remote location.

References: The following sources provide more information about the Time Machine options and cloning features in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases Using Time Machine, Lesson 4.2: Cloning Databases

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 5 - Protect NDB-managed Databases Using Time Machine

Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section 6.2: Cloning Databases

[Nutanix Support & Insights], NDB Time Machine Under the Hood

The administrator can add a stretched VLAN in NDB using either static or dynamic VLANs. A stretched VLAN is a VLAN that spans across multiple Nutanix clusters, and allows the NDB-managed databases to communicate and migrate between different clusters. A static VLAN is a VLAN that is manually configured and assigned to the database server VMs and the databases by the administrator. A dynamic VLAN is a VLAN that is automatically configured and assigned to the database server VMs and the databases by the NDB instance, using the Nutanix Calm orchestration service. Both static and dynamic VLANs can be used to create a stretched VLAN in NDB, as long as they have the same VLAN ID and network configuration across the clusters.

The administrator cannot add a stretched VLAN in NDB using only VLANs that are not managed in NDB. A VLAN that is not managed in NDB is a VLAN that is configured and assigned to the database server VMs and the databases outside of the NDB instance, using the Nutanix Prism web console or other tools. A VLAN that is not managed in NDB cannot be used to create a stretched VLAN in NDB, as it is not recognized or controlled by the NDB instance.

References:

Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slide 8.

Nutanix Database Management & Automation Training Course, Module 6: Nutanix Era Disaster Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 6-7.

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.

The administrator can remediate the issue of critical storage alerts by scaling up the storage directly from the Database Summary page for that specific DBA database. This action allows for an increase in storage capacity to alleviate space constraints and prevent future critical alerts related to storage space1. The other options are not correct, as they either involve scaling the entire database group, which may not be necessary or desired, or require additional steps outside of NDB, which may not be feasible or efficient. References:

1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.4: Database Scaling, slide 5

According to the Nutanix Database Automation (NCP-DB) course, the ports 3205 and 3260 are required for iSCSI connections between the NDB server and the Controller VMs1. Port 3205 is used for the NDB iSCSI initiator service, which initiates the iSCSI sessions and sends SCSI commands to the Controller VMs1. Port 3260 is used for the iSCSI target service, which listens for incoming iSCSI requests and provides access to the storage devices on the Controller VMs1. The other options are not related to iSCSI connections. Port 22 is used for SSH, port 9440 is used for Prism Central, port 80 is used for HTTP, port 443 is used for HTTPS, port 5985 is used for WinRM HTTP, and port 5986 is used for WinRM HTTPS2. References:

1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.2: Database Engine Installation, slide 13

2: Nutanix NCP-DB Certification Exam Sample Questions, Question 18, Answer

When an administrator is asked to add a database to a PostgreSQL instance already managed by NDB, the most appropriate task is to add a new database to the existing source database. In NDB, a PostgreSQL instance refers to a managed database server or cluster, and adding a new database involves creating it within the existing instance using NDB’s database management capabilities. This can be done through the NDB GUI or CLI by selecting the source database and adding the new database, leveraging the current configuration and resources without requiring new VM provisioning.

Option A (Add a new database to a source DB) is correct as it directly addresses adding a database to an existing managed instance.

Option B (Register a new DB VM to add the DB) is incorrect because a new VM registration is unnecessary when the instance is already managed.

Option C (Provision a new DB server VM and add the new DB) is incorrect because provisioning a new VM is overkill for adding a database to an existing instance.

Option D (Update a database clone to add a new DB) is incorrect because clones are read-only copies, not suitable for adding new databases.

This approach ensures efficiency and leverages the existing NDB-managed infrastructure.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Managing Databases in an Instance

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Engines

 The correct answer is C because the NDB Database Agent service is responsible for scheduling and monitoring the NDB-related operations, such as provisioning, patching, cloning, and restoring databases. The NDB Database Agent service is deployed on the NDB server and on each of the database server VMs provisioned by NDB. It contains the tools required to perform each task and communicates with the NDB server through the NDB API. The other options are not correct because they describe different components or functions of the NDB solution. Option A is not correct because the transaction logs are not stored by the NDB Database Agent service, but by the NDB Time Machine service, which is a distributed file system that stores the database snapshots and logs. Option B is not correct because the source databases are not hosted by the NDB Database Agent service, but by the database server VMs, which are virtual machines that contain an instance of the database engine software and the database files. Option D is not correct because the NDB Database Agent service does not contain an instance of the database engine software, but only the tools required to perform the NDB-related operations. The database engine software is installed on the database server VMs, which are provisioned by NDB using the profiles defined by the administrator. 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

According to the Nutanix Database Automation (NCP-DB) learning documents, to configure Era to send alert notifications to email recipients, you need to go to the Administration section, select Era Service, then go to the configure notification widget. From there, you can update the SMTP server configuration1. This allows Era to use the SMTP server to send alert notifications to the specified email recipients1.

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 References

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.

When a vCenter instance managing multiple clusters, including a Nutanix cluster hosting the NDB service, crashes and a new dedicated vCenter server is deployed, the administrator must update the vCenter settings within NDB to re-establish connectivity and management. The correct action is to navigate to the NDB Administration page, where cluster and vCenter configurations can be updated. This page allows the administrator to re-register the new vCenter instance, ensuring NDB can continue to manage the clusters and database VMs effectively. This approach avoids unnecessary reconfiguration wizards or waiting for automatic syncs.

Option A (Click the Getting Started page and perform the configuration wizard) is incorrect because the Getting Started wizard is for initial setup, not post-crash vCenter updates.

Option B (Update cluster settings from the NDB administration page) is correct as it provides the specific interface to modify vCenter settings after a crash.

Option C (Open the maintenance page in NDB and configure the cluster settings) is incorrect because the maintenance page is for service operations, not vCenter reconfiguration.

Option D (Wait 60 minutes and Prism Central will automatically sync NDB) is incorrect because Prism Central does not automatically sync vCenter settings in NDB; manual updates are required.

This ensures seamless integration with the new vCenter instance.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Updating vCenter Settings

Nutanix Support & Insights, Knowledge Base Article: "Reconfiguring vCenter in NDB After Failure"

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

For deploying Nutanix Database Service (NDB), the required file type to download from the Nutanix Portal is an OVA (Open Virtual Appliance) file. The OVA format is a standardized package that includes a pre-configured virtual machine image, including the NDB software, which can be imported into supported hypervisors (e.g., VMware ESXi or Nutanix AHV). This simplifies the deployment process by providing a ready-to-use VM template with all necessary components.

Option A (ZIP) is incorrect as ZIP files are generic archives, not deployment-specific formats for NDB.

Option B (QCOW2) is incorrect because QCOW2 is a disk image format primarily used with KVM/QEMU, not the standard for NDB deployment.

Option C (OVA) is correct as it is the official file type provided by Nutanix for NDB deployment.

Option D (TAR) is incorrect as TAR files are used for archiving, not as a deployment package for NDB.

Administrators should download the OVA from the Nutanix Portal and follow the deployment guide.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Deploying NDB, Section: Downloading and Deploying the OVA

Nutanix Support & Insights, Knowledge Base Article: "NDB Deployment Prerequisites"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 1: Deploy NDB

In Nutanix Database Service (NDB), alert policies are configured to notify administrators of significant events affecting database operations. The default severity level for NDB alert policies is set to Error. This level indicates issues that require attention, such as failed operations (e.g., provisioning failures, as shown in the exhibit), connectivity issues, or other critical operational problems. Other severity levels like Info, Critical, and Warning may be used for different scenarios, but the base configuration for NDB alert policies starts at Error to ensure administrators are alerted to actionable issues without being overwhelmed by less severe notifications.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.1: Configuring Alert Policies.

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

Nutanix NDB Administration Guide: "Alert Policies and Severity Levels" section.

When provisioning a PostgreSQL cluster instance with an external load balancer in NDB, the administrator creates a software profile from a reference VM. The reference VM typically includes software like Patroni (for HA management), HAProxy (for internal load balancing), keepalived (for high availability IP management), and etcd (for distributed configuration). Since an external load balancer is used, the internal HAProxy can be omitted from the reference VM. NDB will rely on the external load balancer to distribute traffic, eliminating the need for HAProxy in the software profile, while the other components remain essential for cluster management.

Option A (Patroni) is incorrect because Patroni is required for PostgreSQL HA management.

Option B (HAProxy) is correct as it can be omitted when an external load balancer is configured.

Option C (keepalived) is incorrect because keepalived is needed for HA IP failover.

Option D (etcd) is incorrect because etcd is necessary for distributed configuration in the cluster.

This adjustment streamlines the profile for external load balancer use.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Creating Software Profiles for HA Instances

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles

The size of a database Time Machine in Nutanix Era is defined by the size of all snapshots and/or transaction logs maintained by Era1. The Time Machine leverages Nutanix’s efficient snapshot technology to capture the state of the database at different points in time1. These snapshots, along with transaction logs that record changes between snapshots, constitute the data maintained by the Time Machine1. Therefore, the size of the Time Machine is determined by the total size of these snapshots and transaction logs1.