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

According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era supports x509 certificates in Base-64 encoded PEM format1. This format is used when an administrator needs to replace the default Nutanix self-signed certificates in Era1.

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.

To provision a PostgreSQL HA instance from a software profile created from a VM with services like etcd, HAProxy, Patroni, and keepalived installed, the administrator must ensure the instance aligns with NDB’s HA framework. These services (e.g., Patroni for PostgreSQL HA management, HAProxy for load balancing) may conflict with NDB’s built-in HA mechanisms. Provisioning an HA instance with these services disabled allows NDB to manage HA using its native replication and failover capabilities (e.g., streaming replication), avoiding duplication or interference from the VM’s pre-installed services.

Option A (Provision an HA instance with the services enabled) is incorrect because enabling these services may cause conflicts with NDB’s HA management.

Option B (Disable the services, create a software profile version, and provision an HA instance) is incorrect because disabling services and recreating a profile is unnecessary; the provisioning step can handle service configuration.

Option C (Provision an HA instance with the services disabled) is correct as it ensures NDB’s HA features take precedence without interference.

Option D (Enable the services, create a software profile version, and provision an HA instance) is incorrect due to potential conflicts with NDB’s HA implementation.

Note: The typo "PostqreSQL" is assumed to mean "PostgreSQL."

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Provisioning HA Instances

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

The scenario describes a PostgreSQL HA deployment managed by NDB, where an NDB-managed VLAN (PGSQLVLAN40) restricts database communication to only within VLAN 40. This indicates a network isolation issue, likely due to VLAN segmentation or routing misconfiguration, preventing communication with external networks or other VLANs. Since NDB manages the VLAN and assigns it to the database VMs, the issue lies beyond NDB’s direct control and involves the underlying network infrastructure (e.g., switches, routers, or Prism Element network settings).

Here’s why the other options are insufficient:

A. Use VLAN 1: VLAN 1 is typically a default VLAN and not recommended for production use due to security and isolation concerns. Changing to VLAN 1 does not address the root cause and could introduce further issues.

B. Change the Default Gateway on the PostgreSQL servers and update NDB: While adjusting the default gateway might enable external communication, this is a workaround rather than a fix. NDB manages the network configuration, and manual changes could be overwritten or cause inconsistency. The root issue (VLAN routing) remains unaddressed.

D. Delete the database servers, VLAN name PGSQLVLAN40, and redeploy: This is overly disruptive and unnecessary, as recreating everything under a new VLAN name does not guarantee resolution unless the network configuration is corrected.

The best approach is to engage the networking team to investigate and resolve the issue, such as configuring inter-VLAN routing, updating firewall rules, or adjusting the default gateway at the network level. Going forward, the administrator should collaborate with the networking team during VLAN planning to ensure proper connectivity. Thus, the verified answer is C.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: Troubleshooting NDB, Lesson 4.1: Identifying and Resolving Network Issues.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.2: Resolve Network-Related Issues (applicable to v6.10).

Nutanix NDB Administration Guide: "Networking Considerations for HA Deployments" section.

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 register a PostgreSQL database server VM with a database on NDB, the database data and log files must be located on a separate mount point from the operating system and the binary installation. This is because NDB uses the mount point as the identifier for the database server VM and the database. If the data and log files are on the same mount point as the operating system or the binary installation, NDB will not be able to recognize them as a valid database server VM or database. Therefore, the administrator should create a separate mount point for the data and log files and specify it during the registration process. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [How to Allow Remote Access to PostgreSQL database], [5 Ways to Host PostgreSQL Databases], [Starting the Database Server].

The correct answer is C because it follows the recommended procedure for applying a CU to a SQL Server Software Profile in NDB. By applying the patch to the profile VM, the administrator ensures that the CU is compatible with the existing Software Profile settings and configuration. By creating a new Software Profile version, the administrator preserves the previous version of the Software Profile for rollback purposes and allows the new version to be tested and published. Option A is incorrect because it deletes the existing Software Profile, which may cause data loss and prevent rollback. Option B is incorrect because it does not apply the patch to the profile VM, which may result in errors or inconsistencies in the Software Profile. Option D is incorrect because it creates a new Software Profile instead of a new version, which may cause confusion and duplication.

References: The following sources provide more information about the Software Profile management and patching in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 5: Patching Databases Using NDB, Lesson 5.2: Creating and Modifying Software Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 4 - Operate and Maintain an NDB Environment

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.2: Creating and Modifying Software Profiles

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.3: Testing and Publishing Database Patches

For enabling Multi-Cluster management on an Era installation, the hypervisor version must be supported and port 9440 must be open between the Era VM and clusters. This ensures that the Era VM can communicate with the clusters for management tasks1.

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

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

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

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

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

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

References

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

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

The error message in the exhibit indicates that the operation failed during the “Create and Register Database Server VMs” step because “Provisioning of all the observers simultaneously took more than two hours.” This type of error is associated with MySQL, as it involves observers which are a part of MySQL Group Replication, used for ensuring high availability1. The other options are not related to the error message, as they do not use observers or Group Replication for clustering. References:

1: Nutanix Database Automation (NCP-DB) course, Module 5: Database High Availability, Lesson 5.2: MySQL Group Replication, slide 7

When a quality assurance (QA) team notices a significant change between a cloned database currently in use and one used a week ago, and they have an SQL script to verify differences, the NDB administrator needs to provide a clone reflecting the database state from a week ago. The task "Clone database selecting Point in Time data" allows the administrator to select a specific point-in-time snapshot (e.g., from a week ago) using the Time Machine feature. This creates a new clone with the exact data state at that time, enabling the QA team to compare it with the current clone.

Option A (Replicate a selected snapshot) is incorrect because replication is for HA, not creating a usable clone for QA.

Option B (Create a clone database from a snapshot) is incorrect because it does not specify point-in-time selection, limiting flexibility to the latest snapshot.

Option C (Clone database selecting Point in Time data) is correct as it allows precise selection of the week-old data state.

Option D (Perform a Log Catch Up operation) is incorrect because Log Catch Up applies recent logs, not reverting to a past state.

This approach meets the QA team’s need for historical data comparison.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Cloning with Point-in-Time Data

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

NDB supports Linux OS patching for database server VMs. Linux OS patching is performed by using the yum or apt package managers, depending on the Linux distribution. To exclude Kernel patches for the Linux OS, the administrator can disable or exclude the appropriate repositories on the VM prior to patching. This can be done by editing the yum.conf or apt.conf files, or by using the --disablerepo or --exclude options in the yum or apt commands. This way, the administrator can control which patches are applied to the VM without affecting other VMs or requiring additional scripts or reboots.

References:

Nutanix Database Automation (NCP-DB) Course Details, Section 4.2: NDB Linux OS Patching

Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.2: Perform Linux OS Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.2: NDB Linux OS Patching

Nutanix Database Automation (NCP-DB) User Guide, Section 4.5: Patch Linux OS Software

To add a new Nutanix AHV cluster to the current single default container for database provisioning and enable NDB multi-cluster functionality, the administrator must ensure a unified management framework. Nutanix Prism Central serves as the centralized management platform for multi-cluster environments, allowing NDB to manage multiple clusters (in this case, the existing cluster and the new AHV cluster) under a single instance. Before enabling multi-cluster support in NDB, both clusters must be registered with the same Prism Central instance, and NDB must be confirmed as registered to that instance. This ensures consistent policy enforcement, resource visibility, and database provisioning across clusters using the default container.

Option A (Deploy Nutanix Self Service VM and use blueprints) is incorrect because Nutanix Self Service is an optional tool for end-user provisioning and not a prerequisite for multi-cluster enablement.

Option B (Configure datastore mapping within Prism Element Protection Domains) is incorrect because datastore mapping is a lower-level configuration and not directly required for multi-cluster setup in NDB.

Option C (Enable High Availability for NDB service on the Administration page) is incorrect because HA is a separate configuration for NDB resilience, not a prerequisite for multi-cluster support.

Option D is correct as it aligns with NDB’s requirement for Prism Central integration to manage multiple clusters effectively.

This configuration ensures seamless multi-cluster operation.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Multi-Cluster Configuration

Nutanix Prism Central Administration Guide, Section: Managing Multiple Clusters

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

 NDB SLAs are service level agreements that define the data protection and recovery objectives for NDB-managed databases. NDB SLAs consist of data retention policies that specify how long the snapshots and log backups of a database are kept in the Time Machine. Data retention policies can be customized to meet different business and compliance requirements, such as daily, weekly, monthly, or yearly retention periods. NDB SLAs also determine the frequency and schedule of the snapshots and log backups, as well as the storage location and replication options. An administrator who is tasked with auditing NDB SLAs will be reviewing the data retention policies of each database and Time Machine, as well as the snapshot and log backup history and status. The administrator will also be able to monitor the storage usage and performance of the NDB SLAs, and modify or delete the SLAs as needed. The other options are not part of the NDB SLAs, but rather separate features or concepts of NDB. Snapshot schedules are the intervals at which NDB takes snapshots of the databases, which are determined by the SLAs. Clone management is the process of creating, refreshing, or deleting database clones from the Time Machine. Recovery time objective (RTO) is the maximum acceptable time for restoring a database after a failure, which is influenced by the SLAs, but not defined by them. References:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 5 - Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies

Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: SLA Concepts

Nutanix Database Service (NDB) User Guide, Chapter 6: SLAs, Section: SLA Overview

 Before patching a Linux OS on a database server VM provisioned using NDB, you must configure the repository for the OS updates. This can be done by creating a Repository Profile in NDB and specifying the URL, username, and password for the repository. The Repository Profile can be applied to one or more database server VMs during the provisioning process or later. By configuring the repository, you ensure that NDB can access and download the latest OS patches from a trusted source. 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.

To change the static IP address on the NDB VM, an administrator would need to enter the NDB command line using the cerebro_cli command. The cerebro_cli command is used to access the Cerebro service, which is responsible for managing the NDB instance and its components. The cerebro_cli command can be run from the NDB VM or from any other VM that has network connectivity to the NDB VM. The cerebro_cli command has various subcommands and options to perform different tasks, such as changing the IP address, hostname, password, or certificate of the NDB VM. To change the static IP address, the administrator would need to use the cerebro_cli network update subcommand with the appropriate parameters, such as the new IP address, netmask, gateway, and DNS servers. The cerebro_cli network update subcommand also requires the administrator to provide the current password of the NDB VM for authentication. After changing the IP address, the administrator would need to restart the NDB VM for the changes to take effect. References:

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

Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.2: Configuring NDB, Topic: Changing the IP Address of the NDB VM

Nutanix Database Service (NDB) Command Line Interface Guide, Chapter 2: Cerebro CLI, Section: cerebro_cli network update

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.

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.

In a high availability (HA) Nutanix Database Service (NDB) environment, custom SSL certificates are used to secure communication between clients (e.g., NDB GUI, API calls) and the NDB control plane. The HA Proxy VMs serve as the entry point for all external traffic, load balancing requests across the NDB API server VMs and providing secure SSL termination. When configuring custom SSL certificates, they must be updated on all HA Proxy VMs to ensure consistent and secure communication across the HA environment. Updating only a subset of servers or other components (like API or Repository VMs) would lead to inconsistencies or SSL handshake failures.

Option A (All API server VMs) is incorrect because the API servers do not directly handle external SSL termination; this is managed by the HA Proxy layer.

Option B (All HA Proxy VMs) is correct as these VMs are responsible for SSL termination and load balancing in an HA setup, requiring the custom certificates to be applied uniformly.

Option C (The API and Repository VMs running on the primary cluster) is incorrect because Repository VMs do not handle client-facing traffic, and the API servers rely on HA Proxy for SSL handling.

Option D (The primary API, Repository, and HA Proxy servers) is incorrect because it implies a single "primary" server focus, whereas in an HA setup, all HA Proxy VMs (not just a primary one) must be updated.

This aligns with NDB’s HA architecture, where HA Proxy VMs are the critical components for SSL certificate management.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring High Availability and SSL Certificates

Nutanix Support & Insights, Knowledge Base Article: "Configuring Custom SSL Certificates in NDB HA Environments"

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

 In the Nutanix Database Automation (NCP-DB) process, when a database administrator is tasked with creating a new clone of a running SQL database and there are no authorized servers available, the administrator should click the Action icon to authorize one or more database server VMs1. This is because the Nutanix Database Service (NDB) requires authorized servers to perform operations such as cloning1. The authorization process allows the NDB to manage and perform operations on the database server VMs1.

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

According to the Nutanix Database Automation (NCP-DB) Learning documents12, to clone a source production database to an existing development server, the following actions must be taken:

A. The development server must be registered by Era in order to receive the clone1. This is because Nutanix Era is a database management tool that manages the lifecycle of databases and their copies. Registering the development server with Era allows it to manage the database on that server.

D. The development server must have the IP and credentials provided during cloning2. This is necessary for Era to access the development server and perform the cloning operation. The IP address and credentials are used to establish a connection to the development server. Without these details, Era would not be able to access the server and perform the cloning operation.

In the context of Nutanix Database Automation (NCP-DB), when there are insufficient resources on a development cluster, the administrator can adjust the Compute and Database Parameters profiles to make the copy fit within the available resources1. The Compute profile includes settings related to CPU and memory resources, which can be adjusted to fit within the available resources. The Database Parameters profile includes settings that control the behavior and resource usage of the database, which can also be adjusted to optimize resource usage1.

The correct answer is B because setting VM-Host affinity ensures that the DB Server VMs are not migrated to another host during the LCM upgrade process. This way, the DB Server VMs can continue to serve the database requests without interruption. Option A is incorrect because updating the Nutanix cluster does not prevent the DB Server VMs from being moved to another host. Option C is incorrect because removing the Nutanix cluster from NDB will make the DB Server VMs unmanaged by NDB and lose the benefits of NDB features. Option D is incorrect because unsetting VM-Host affinity will allow the DB Server VMs to be migrated to another host during the LCM upgrade process, which may cause downtime or performance degradation.

References: The following sources provide more information about the LCM upgrades and VM-Host affinity in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 6: Administering an NDB Environment, Lesson 6.3: Performing NDB Software Upgrades

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.3: Performing NDB Software Upgrades

Nutanix Support & Insights, Your guide to the Upgrades, LCM Design

Nutanix Life Cycle Manager Guide, Chapter 3: Upgrading Software and Firmware, Section 3.2: Preparing for an Upgrade, VM-Host Affinity

This is because it allows the database to be refreshed at the exact time specified (9:30 PM) with the most recent data. The other options either perform the snapshot before the desired time or do not specify when the snapshot would occur. Please note that the exact answer might depend on the specific database system and its capabilities. Always refer to the database’s documentation for the most accurate information.

 NDB supports two modes of log backup management for Microsoft SQL databases: NDB-managed and 3rd-party managed. In the NDB-managed mode, NDB takes full control of the log backups and stores them in the Cerebro log location. In the 3rd-party managed mode, NDB allows the use of external backup tools to backup the logs from the database log destination. However, NDB still needs to capture the logs for its own operations, such as point-in-time recovery, clone refresh, and log catch-up. Therefore, NDB will periodically scan the database log destination and copy the logs to the Cerebro log location. This process requires that the log catch-up begins before the logs get backed up by the 3rd-party tool, otherwise NDB will miss some logs and the operations will fail. If the 3rd-party tool grants exclusive access to the logs, then NDB will not be able to capture them at all, and the operations will not be supported. References:

Nutanix Database Management & Automation (NDMA) course, Module 5, Lesson 5.2 - Log Backup Management

Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Log Backup Management

NDB Agents handle log backups for database instances, but storing these backups locally can lead to bottlenecks (e.g., disk I/O, storage capacity). To alleviate this, integrating NDB with Nutanix Objects is the recommended solution. Nutanix Objects is an S3-compatible object storage service within the Nutanix ecosystem, ideal for offloading log backups from NDB Agents to a scalable, centralized storage platform. This reduces local storage pressure, improves performance, and ensures strict SLAs for database recovery by leveraging efficient backup retrieval.

Other options are less effective:

A: Integrating with AWS S3 or Azure Blob is possible but requires external connectivity and introduces latency, complexity, and cost compared to Nutanix Objects.

B: Adding NDB Agent VMs increases management overhead and doesn’t address the root storage bottleneck.

D: Increasing RAM/CPU on NDB Agents may help processing but doesn’t solve storage capacity or I/O issues for log backups.

Thus, C is the verified answer, aligning with Nutanix’s integrated ecosystem approach.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.3: Configuring Log Backup Storage.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.3: Configure Backup Storage Options (applicable to v6.10).

Nutanix NDB Administration Guide: "Integrating NDB with Nutanix Objects for Log Backups" section.

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., 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.

According to the Nutanix Database Automation (NCP-DB) learning documents, an administrator can change the snapshot schedule for a given database by selecting the Time Machine, then under Action, select Update and define an appropriate schedule1. This is because the Time Machine in Nutanix Era allows you to specify the number of backups or snapshots the time machine should take, the time of day it takes those snapshots, and the day of the week it takes weekly or monthly backups1. These options help you build a complete schedule of time machine capture operations1. Even if the Time Machine is in a paused state, the administrator can still update the schedule1. Cloning the Time Machine or the database is not necessary for changing the snapshot schedule1.

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.

Option A: On the Era Dashboard Database Summary Table under Source Database. The dashboard provides a summary of the databases, including their sizes1.

Option B: Under the Capacity widget on the Database Server VMS > List database summary page. While this might provide information about the capacity, it does not specifically provide the size of a Source Database.

Option C: On the Databases > Sources table. This table provides detailed information about the databases, including their sizes1.

Option D: On the Profiles > Database Parameters list for the assigned DB Parameter Profile. This list provides parameters for the database but does not provide the size of a Source Database.

A Compute Profile is a template that defines the CPU, memory, and disk resources for a database server VM. By creating a Compute Profile with the desired number of cores per vCPU, the administrator can easily apply it to multiple VMs during provisioning, ensuring consistent and optimal performance. This also saves time and effort compared to updating the VMs individually or modifying the default profile after provisioning. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, How-to setup number of cores per CPU in a virtual 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

Nutanix Era allows custom metadata to be assigned to entities (clones, time machines, databases, and database servers) by using Tags. Tags are a component of Nutanix Era that allows users to assign custom metadata to various entities, enhancing the ability to organize, search, and manage these entities within the Era platform1.

To migrate an existing Microsoft SQL Server (MSSQL) database to NDB, the recommended approach is to:

Provision a new database server VM and database: Use the NDB interface to provision a new VM and configure an MSSQL database instance on the Nutanix platform. This leverages NDB’s automated provisioning capabilities to ensure compatibility with Nutanix infrastructure.

Migrate the data: Transfer the data from the existing MSSQL database to the newly provisioned database. This can be achieved using native MSSQL tools (e.g., backup/restore, log shipping, or replication) or NDB’s data migration features, such as cloning or restoring from a backup, depending on the source environment.

Other options are incorrect or incomplete:

A. Use Nutanix Move to migrate the database server VM: Nutanix Move is designed for VM migration between platforms, not for database-specific migrations within NDB, which requires data migration to a new instance.

C. Create a new database server VM and database then register it with NDB: Registering an existing VM with NDB does not handle data migration from the source MSSQL database.

D. Backup your database VM and import it into Nutanix: Backing up the entire VM and importing it does not integrate the database with NDB’s management framework, and data migration would still be required separately.

Thus, the verified answer is B, providing a structured migration process tailored to NDB’s capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.5: Migrating Databases to NDB.

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

Nutanix NDB Administration Guide: "Migrating MSSQL Databases to NDB" section, outlining provisioning and data migration steps.

In the context of Nutanix Era, the term “Brownfield Database” is used to refer to an existing database that is registered with Era1. This process allows Era to bring Database as a Service (DBaaS) capabilities to your existing database2. It’s important to note that before you register a database with Era, certain prerequisites must be met3.

 To increase storage for a MongoDB database provisioned using NDB, the administrator needs to use the extend_storage parameter in the input file for the NDB CLI. This parameter specifies the amount of additional storage to be added to the database server VM in GB. For example, if the current storage size is 100 GB and the administrator wants to increase it to 150 GB, the input file should contain the following line:

extend_storage: 50

The other parameters are not relevant for this operation. The update parameter is used to update the database software version, the database parameter is used to specify the database name, and the data_percent parameter is used to specify the percentage of data to be copied during a clone operation. 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].

The NDB GUI allows an administrator to set the schedule interval for a database log catch up, which is the process of collecting transaction logs periodically from the source databases and storing them in the time machine. The shortest possible value for this interval is 15 minutes, as per the NDB documentation1. This means that the NDB time machine will capture the database logs every 15 minutes and use them for backup, restore, clone, and refresh operations. References: Nutanix Database Management & Automation (NDMA), page 29; Nutanix Support & Insights, section “Log Catch-up”

The correct answer is B and D because these are the two status values that can be set within the Alerts Dashboard in NDB. Resolved means that the alert has been fixed and no longer requires attention. Acknowledged means that the alert has been seen and is being worked on. Option A is incorrect because Auto is not a status value, but a mode that automatically resolves alerts based on predefined rules. Option C is incorrect because Data Resiliency is not a status value, but a feature that ensures the availability and integrity of the data in NDB.

References: The following sources provide more information about the Alerts Dashboard and its status values in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 3: Monitoring Alerts and Storage Usage Within an NDB Implementation, Lesson 3.1: Monitoring Alerts

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 3 - Monitor Alerts and Storage Usage Within an NDB Implementation

Nutanix Database Service (NDB) User Guide, Chapter 3: Monitoring Alerts and Storage Usage Within an NDB Implementation, Section 3.1: Monitoring Alerts

[Nutanix Support & Insights], Resolving All Alerts Related to a Database or Database Server VM in NDB

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.

The administrator should perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, to accomplish the task of patching a MongoDB server cluster within an NDB environment. A rolling upgrade is a method of applying patches or updates to a cluster without downtime or interruption of service. The administrator can use the NDB patching feature to perform a rolling upgrade on a MongoDB server cluster, which consists of a primary member and one or more secondary members that form a replica set. The NDB patching feature allows the administrator to select the software profile version, the database parameters profile, and the network profile for the patching operation. The NDB patching feature also automates the steps of the rolling upgrade, such as:

Step 1: The administrator initiates the patching operation on the NDB instance, and selects the MongoDB server cluster to be patched.

Step 2: The NDB instance verifies the prerequisites and compatibility of the patching operation, and creates a pre-patch snapshot of the MongoDB server cluster.

Step 3: The NDB instance applies the patch to the first secondary member of the MongoDB server cluster, and waits for the patching to complete successfully.

Step 4: The NDB instance verifies the status and functionality of the patched secondary member, and repeats the patching process for the remaining secondary members of the MongoDB server cluster, one at a time.

Step 5: The NDB instance performs a failover of the primary member to one of the patched secondary members, and applies the patch to the original primary member.

Step 6: The NDB instance verifies the status and functionality of the patched primary member, and performs a failback of the primary member to the original primary member, if desired.

Step 7: The NDB instance creates a post-patch snapshot of the MongoDB server cluster, and completes the patching operation.

Performing a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, is the recommended and best practice method of patching a MongoDB server cluster within an NDB environment, as it ensures the high availability, consistency, and performance of the MongoDB server cluster and the databases.

Performing a rolling upgrade, applying the patch to the primary member first, followed by the secondary members, is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to the primary member first would disrupt the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to restore the MongoDB server cluster to a functional state.

Applying the patch to all nodes at once is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to all nodes at once would require shutting down the entire MongoDB server cluster, and would expose the MongoDB server cluster and the databases to potential errors, failures, and corruption during the patching process.

Disabling the replica set while patching is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Disabling the replica set while patching would break the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to re-enable the replica set and restore the MongoDB server cluster to a functional state.

References:

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 11-12, 15-16.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.3: Nutanix Era Patching, slides 5-9.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.4: Nutanix Era Patching Lab, slides 5-10.

Nutanix Database Management & Automation Training Course, Module 7: Nutanix Era Troubleshooting, Lesson 7.1: Nutanix Era Troubleshooting, slide 6.

In an NDB environment, the repository VM stores metadata and configuration data but is not a critical runtime component for service availability. If the team powers off the repository VM during maintenance, and it is neither the primary nor a synchronized copy node, the NDB service will continue to operate without interruption. NDB’s high availability (HA) architecture, managed by HAProxy and other components, ensures redundancy and failover capabilities, allowing the system to rely on the primary and synchronized nodes. The repository VM’s downtime only affects metadata access, which can be restored post-maintenance without impacting ongoing database operations.

Option A (The HAProxy VMs will failover instead) is incorrect because HAProxy failover is triggered by primary service node failures, not repository VM power-off.

Option B (There will be no service interruption) is correct as the HA design tolerates a non-primary, non-synchronized repository VM being offline.

Option C (Manual interaction will be required to restore service) is incorrect because no service restoration is needed during this scenario.

Option D (NDB services will fail over immediately) is incorrect because failover is not triggered by a non-critical repository VM power-off.

This reflects NDB’s robust HA implementation.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: High Availability Architecture

Nutanix Support & Insights, Knowledge Base Article: "Impact of Repository VM Maintenance in NDB"

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

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 optimal path to restore the table back with minimum data loss is to use the point in time restore feature of NDB, which allows the administrator to restore the database to a specific point in time based on the available snapshots and logs1. By restoring using point in time till 10:42pm, the administrator can recover the table just before it was dropped by the user, and minimize the data loss to the least possible amount1. The other options are not optimal, as they either involve restoring an older snapshot, which may result in more data loss, or restoring a non-existent snapshot, which is not possible. References:

1: Nutanix Database Automation (NCP-DB) course, Module 6: Database Recovery, Lesson 6.2: Point in Time Restore, slide 5

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.

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

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

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

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

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

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

Official Nutanix Database Automation References

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

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

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

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.

References:

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

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.

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 registering a new Nutanix Cluster with Era, the Era Agent is installed on the target Nutanix cluster via the Register Nutanix Cluster workflow1. This agent is crucial for the functioning of the Nutanix Database Service (NDB) as it helps in managing and optimizing database workloads2. It also enables the application of procedural concepts to add Nutanix clusters to NDB2.

Before updating Oracle Database software, you need to download the Patch Set Update (PSU) from Oracle support. A PSU is a collection of critical and security patches for Oracle products. You need to have a valid Oracle account and access to the My Oracle Support portal to download the PSU. You also need to check the compatibility and prerequisites of the PSU before applying it to your Oracle Database software. NDB uses out-of-place patching for Oracle, which means you need to create a new software profile version with the patched Oracle software and use it to update your existing databases. References:

Patch Oracle Database Software, Nutanix Support & Insights

Nutanix Certified Professional - Database Automation (NCP-DB), Section 4 - Operate and Maintain an NDB Environment

Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.4 - Patching Databases

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”

There are two ways to upgrade an NDB Server: one-click upgrade and offline upgrade. One-click upgrade is the recommended method, as it automatically downloads and installs the latest NDB software version from the Nutanix portal. Offline upgrade is an alternative method, which requires you to manually download the NDB software bundle and upload it to the NDB Server VM. Both methods require you to have a valid Nutanix account and an internet connection. References:

Nutanix Certified Professional - Database Automation (NCP-DB), Section 6 - Administer an NDB Environment

Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 10, Objective 6.2

Nutanix Database Management & Automation (NDMA) course, Module 6, Lesson 6.1 - NDB Software Upgrade

 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.

The correct answer is D because it allows the administrator to make the profile available to all users without requiring any additional permissions or roles. A profile is a collection of settings that define how NDB manages a database server or a database. By default, a profile is only available to the user who created it and the Database Admin role. To make a profile available to all users, the administrator can update the profile and set the available state to All. This will enable all users to view and use the profile for their database operations. The other options are not correct because they either require additional steps or do not achieve the desired outcome. Option A is not correct because creating an Access Control role with the Create Profile right and assigning it to all users will only allow them to create their own profiles, not use the existing one. Option B is not correct because creating an Access Control group with the desired users and granting it the Database Admin role will only make the profile available to those users, not all users. Option C is not correct because updating the profile and setting the status to Published will not change the availability of the profile, only the state of the profile. A published profile is a profile that has been tested and verified by the administrator and is ready for use. A draft profile is a profile that is still under development or testing and is not ready for use. 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

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.

 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

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

 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

For restoring a database provisioned on Storage Spaces, especially when virtual disks are shared among multiple databases, the supported method is a copy-based restore via the NDB GUI. This method allows for a precise and controlled restoration process suitable for shared storage environments.References: Nutanix Database Automation documentation, specifically in the section on database restoration methods and storage spaces.

When running the Linux prerequisites script for NDB, the -t argument is a required parameter that specifies the timeout interval. This argument defines the maximum time (in seconds) the script will wait for certain operations (e.g., connectivity checks, package installations) to complete before timing out. This is critical during the preinstallation phase to ensure the environment is properly configured and responsive, avoiding indefinite hangs. Other options are not associated with -t:

A. Operating System type: This is not a typical argument for the prerequisites script.

C. NDB server IP: This would be specified separately (e.g., via -s or a similar flag).

D. Database engine: This is irrelevant to the prerequisites script, which focuses on system setup.

Thus, the verified answer is B, aligning with the script’s purpose of managing execution timeouts.

Official Nutanix Database Automation References

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

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: "Running the Linux Prerequisites Script" section, detailing -t usage.

The provided exhibit shows the "Enable Multi-Cluster" configuration wizard in NDB, where the VLAN dropdown is empty with a "Nothing found" message, indicating that no VLANs are available for selection. This issue arises because NDB requires a network profile to be created before provisioning the NDB Agent VM and enabling multi-cluster support. A network profile defines the static VLANs managed by NDB, which are essential for network configuration during multi-cluster setup. The warning in the exhibit ("An NDB managed static vLAN is required to provision the NDB Agent VM. Add an NDB managed static vLAN using the Networks page to continue.") reinforces that the administrator must create a network profile via the Networks page to populate the VLAN dropdown.

Option A (A network profile must be created first) is correct as it addresses the root cause by ensuring VLANs are defined in a network profile.

Option B (Verify if subnet leverages advanced network control) is incorrect because advanced network control is not a prerequisite for VLAN selection in this context.

Option C (IP address pool must be managed in NDB) is incorrect because IP address pools are managed separately and not required for VLAN selection at this stage.

Option D (VLAN subnet must use IP address management) is incorrect because IP address management is not a direct requirement for enabling VLAN selection in the wizard.

After creating the network profile, the administrator can proceed with the multi-cluster enablement.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring Network Profiles for Multi-Cluster

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting VLAN Issues in NDB Multi-Cluster Setup"

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

To capture database transaction logs in NDB, the Log Catch-up operation within the Time Machine is used. Log Catch-up retrieves and applies transaction logs (e.g., PostgreSQL WAL, SQL Server logs) to a snapshot, ensuring the database can be restored to a specific point in time. This operation bridges gaps between snapshots by incorporating log data, maintaining a continuous recovery chain.

Other options are incorrect:

A. Write-Ahead Logging: A database feature (e.g., in PostgreSQL), not an NDB Time Machine operation.

B. Log Flush: Refers to writing logs to disk, not capturing them for recovery.

D. Snapshots: Capture the database state but do not handle transaction logs specifically.

Thus, the verified answer is C, aligning with NDB’s log management.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Time Machines.

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

Nutanix NDB Administration Guide: "Log Catch-up Operation" section.

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) v6.5 Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.1: Configure HA for Supported Databases (applicable to v6.10).

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

To enable multi-cluster setup for NDB High Availability (HA), the administrator must configure the NDB Agent with a Network Profile. A Network Profile defines the networking settings (e.g., VLANs, IP ranges) that the NDB Agent uses to communicate across clusters. This is critical for multi-cluster HA, as it ensures consistent network configuration for replication, failover, and data synchronization between clusters. The Network Profile must be properly configured to handle inter-cluster traffic and latency requirements (e.g., <25ms RTT).

Other options are irrelevant:

A. Name Prefix: Used for naming conventions, not network configuration.

C. Static VLAN: A component of a Network Profile, but not the full configuration needed.

D. Compute Profile: Defines VM resources (CPU, memory), not networking for HA.

Thus, the verified answer is B, aligning with multi-cluster HA networking needs.

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: "Configuring Network Profiles for Multi-Cluster HA" section.

NDB sends notifications when alerts are generated via email. The email notifications can be configured to send to one or more recipients, and can be customized to include the alert severity, category, description, and resolution steps. The email notifications help to inform the database administrator and other stakeholders about the status and issues of the NDB-managed databases and operations.

NDB does not send notifications via SNMP, APIs, or Pulse. SNMP is a protocol for collecting and organizing information about managed devices on a network. APIs are interfaces for communicating and exchanging data between different applications or systems. Pulse is a feature of the Nutanix cluster that collects and sends diagnostic and usage data to Nutanix for analysis and support.

References:

Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment, Lesson 3.2: Nutanix Era Deployment, slide 11.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slide 6.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.2: Nutanix Era Alerts and Notifications, slides 5-7.

An NDB Software Profile is a template of the OS and database engine that you can use to provision or clone database server VMs using NDB. To create a software profile, you need to upload an installer package for the database software that you want to use, such as SQL Server or Oracle. The installer package must be compatible with the OS image that you have registered with Prism Element. You do not need a database server VM registered with NDB, a patch file for the installed databases, or an OS image registered with Prism Element to create a software profile. Those are required for other tasks, such as creating a software profile version, registering a database server VM, or provisioning a database server VM.

References: Nutanix Benefit 8: Integrated Self-service Database Management, Nutanix Support & Insights, section “NDB Software”

In Nutanix Database Automation (NCP-DB), the Time Machine feature is used for protecting databases and creating database clones. To create a database clone using the Era Interface, an administrator should select Time Machines, select a source database, and then choose Create Clone12. This process allows the administrator to create a copy of the source database at a specific point in time1.

To assign the minimum permissions required for provisioning new databases in an NDB deployment, the IT manager should assign the Database Administrator role. This role provides the necessary privileges to provision, configure, and manage database instances within NDB, including creating new databases using software profiles and registering database servers. It is designed for database-specific tasks without granting broader infrastructure or administrative control, making it the least privileged role suited for this purpose.

Other options exceed the minimum requirements:

A. Infrastructure Administrator: Manages cluster infrastructure (e.g., storage, networking), which is more than needed for database provisioning.

B. Super Administrator: Grants full control over NDB, including user management and system configuration, far beyond provisioning.

C. Database Infrastructure Administrator: Includes infrastructure management in addition to database tasks, exceeding the minimum scope.

Thus, the verified answer is D, aligning with the principle of least privilege.

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 Database Administrator role.

NDB allows creating and refreshing clones to a point in time using two primary methods:

B. Snapshots: NDB uses storage snapshots (e.g., via Nutanix Volumes or AHV) to capture the database state at a specific point. These snapshots can be used to create or refresh clones, providing a consistent recovery point.

D. Transaction logs: Transaction logs (e.g., PostgreSQL WAL, SQL Server logs) enable point-in-time recovery (PITR) by applying logs to a snapshot, allowing clones to be refreshed to a precise moment.

Other options are not supported for this purpose:

A. Full backups: Full backups are used for complete restores but are not optimized for frequent clone refreshes.

C. VM snapshots: VM-level snapshots (e.g., AHV snapshots) are not managed by NDB for database cloning, as they lack database consistency.

Thus, the verified answers are B and D, reflecting NDB’s clone refresh capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Time Machines and Clones.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Clones (applicable to v6.10).

Nutanix NDB Administration Guide: "Clone Creation and Refresh" section.

When an administrator changes the NDB language settings from English to Spanish, but the language reverts to English when accessing NDB from a different workstation, it indicates that the language settings are tied to the web browser on the original workstation rather than being globally applied. NDB’s language settings are typically stored locally in the browser’s cache or preferences (e.g., via cookies or browser locale settings), meaning they do not persist across different devices or browsers unless explicitly synchronized (e.g., via user profile settings, which NDB does not universally enforce).

Other options are incorrect:

B. The language settings match workstation regional settings: This would depend on the OS locale, not the observed behavior of reverting to English.

C. The language settings revert to English after logoff: NDB does not reset language settings upon logoff; the issue is device-specific.

D. The language settings are bound to NDB users: If this were true, the language would persist across workstations for the same user, which is not the case here.

Thus, the verified answer is A, reflecting browser-local language management.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.3: User Interface Customization.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.2: Navigate the NDB UI (applicable to v6.10).

Nutanix NDB User Guide: "Customizing Language Settings" section, noting browser dependency.

In Nutanix Database Service (NDB), a Network Profile is used to define networking configurations for database VMs, including VLAN assignments and IP address ranges. The correct procedure to create a Network Profile that assigns a VLAN and provides IP addresses to a database VM is as follows:

Create Network Profile: Start by initiating the creation of a new Network Profile within NDB. This is done from the NDB interface under the "Network" or "Profiles" section.

Select the VLAN: During the Network Profile creation process, you specify the VLAN that the database VM will use. This involves selecting an existing VLAN configured in the Nutanix cluster (e.g., via Prism Element) or defining a new VLAN ID if applicable.

Define IP Range: Finally, you define the IP address range (e.g., a subnet or specific IPs) that will be assigned to the database VM(s) within the selected VLAN. This ensures the VM receives a valid IP address for communication.

The sequence in option B aligns with the NDB workflow, where the Network Profile is created first, followed by associating it with a VLAN and then defining the IP allocation. Other options are incorrect:

A: "Add the VLAN" is vague and does not specify where the VLAN is added, disrupting the logical flow.

C: Adding a VLAN before creating the profile is not the standard NDB process, as VLANs are associated during profile creation.

D: Defining an IP range before creating the profile is out of sequence, as the profile must exist to hold the configuration.

Thus, the verified answer is B. Create Network Profile, Select the VLAN, Define IP Range.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.2: Configuring Network Profiles.

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

Nutanix NDB Administration Guide: "Network Profiles" section, detailing VLAN and IP configuration steps.

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.

To leverage the Oracle restore feature within Nutanix Database Service (NDB) for a Real Application Clusters (RAC) database, the administrator must ensure that the database is registered with NDB prior to initiating the restoration operation. Registration allows NDB to recognize the RAC database, manage its metadata, and perform operations like restore using Time Machine snapshots or backups. Without registration, NDB cannot access the necessary configuration details or protection data, rendering the restore feature unavailable.

Option A (Ensure the database is in a Down state) is incorrect because the database state (Up or Down) is not a prerequisite for initiating a restore; the process handles state transitions.

Option B (Ensure the database is registered with NDB) is correct as registration is the foundational requirement for NDB to manage and restore the RAC database.

Option C (Ensure the database is in an Up state) is incorrect because an Up state is not required; restore can proceed regardless of the current state.

Option D (Ensure more than one node of the RAC is reachable) is incorrect because while RAC node availability is important for HA, it is not a mandatory prerequisite for the restore operation itself.

This ensures the restore process can proceed with the necessary NDB oversight.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring RAC Databases

Nutanix Support & Insights, Knowledge Base Article: "Preparing Oracle RAC for Restore in NDB"

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

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.

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