Free and Premium Nutanix NCP-DB Dumps Questions Answers

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) v7.5Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v7.5).

Nutanix NDB Administration Guide: "Configuring Network Profiles for Multi-Cluster HA" section.

In Nutanix Database Service (NDB), alert retention is a configurable setting that determines how long alerts (e.g., system issues, performance warnings, or database events) are stored in the system for review and analysis. Based on NDB’s design and administrative policies, the maximum number of days allowed for alert retention is 180 days. This duration allows administrators to maintain a reasonable historical view of system health while preventing excessive data accumulation that could impact performance. This value is typically set as a default maximum in the NDB settings or via Prism Central integration, and administrators can adjust retention periods within this limit based on organizational needs.

Option A (90) is incorrect as it represents a shorter retention period, which may be a configurable minimum or intermediate value but not the maximum.

Option B (180) is correct as it matches the documented maximum alert retention period in NDB.

Option C (270) is incorrect as it exceeds the standard maximum retention period supported by NDB.

Option D (306) is incorrect as it is not a supported retention limit in NDB’s configuration options.

Administrators should verify this setting in the NDB UI under alert management or consult Nutanix support for custom configurations.

References

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

Nutanix Support & Insights, Technical Note: "Alert Retention and Management in NDB"

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

 Nutanix Database Service (NDB) supports automated minor version upgrades for PostgreSQL1. Before applying the patch, the administrator should create a new software profile2. This is because the software profile contains the database engine binaries and other software required to run the database engine2. Therefore, to apply a minor version upgrade, a new software profile with the updated binaries needs to be created2. Once the new software profile is created, it can be used to patch the PostgreSQL database2.

NDB patches MongoDB replica sets through a rolling workflow designed to minimize database unavailability. It first applies the selected patch to available secondary members one at a time. After the secondary members are successfully patched and validated, NDB performs the required replica-set role transitions and patches the primary member last. This order preserves service availability and avoids simultaneously taking every voting member offline. Nutanix explicitly documents rolling upgrades for MongoDB replica sets; NDB does not patch all members in parallel, and the primary is not the first member patched. Current NDB documentation also lists patching and upgrading MongoDB sharded clusters as unsupported. Therefore, the verified positive statement about the supported patching workflow is that rolling patching is available for replica sets. Nutanix MongoDB cluster-patching documentation

 According to the Nutanix Database Automation (NCP-DB) learning documents, to refresh an existing DB Clone, a developer with RBAC privileges in Era needs to navigate to Databases > Clones. From there, they select the appropriate clone from the table, click Refresh, select the desired Point In Time or Snapshot, and then click Refresh12. This process allows the developer to update the cloned database3.

When an administrator is creating a Windows Domain profile in Era, the SQL Service Startup Account is an optional field that can be skipped and provided during the provisioning process. This account is used to start the SQL Server service when the server starts up. If this field is not provided during the creation of the Windows Domain profile, it can be provided later during the provisioning process1.

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.

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.

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.

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.

To register an Oracle Database Server VM to Era in Nutanix Database Automation (NCP-DB), certain dependencies must be met. One of these is that SUDO NOPASS access is required1. This allows the Era service to perform necessary operations on the Oracle Database Server VM. As for assigning a static IP address to the Era VM on ESXi, you can use the vSphere Client to configure static IP settings2. However, this is not directly related to the registration of an Oracle Database Server VM to Era. 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.

 An Infrastructure Administrator is a role in NDB that has the permission to manage network and storage resources, such as VLANs, IP Pools, and Storage Containers. This role is suitable for the engineer who needs to add new VLANs or IP Pools in NDB. The other roles have either more or less privileges than required for this task. A Database Administrator can manage databases and database server VMs, but not network and storage resources. A Super Administrator can manage all aspects of NDB, but this is more than the least-privilege access needed. A Database Infrastructure Administrator can manage both databases and network and storage resources, but this is also more than the least-privilege access needed.

 Nutanix Support & Insights, section “NDB Roles and Permissions”

Every Nutanix cluster that will host NDB-provisioned databases must first be registered with the NDB control plane. Registration provides NDB with the Prism Element endpoint, credentials, storage-container information, and network context required to create and manage database server VMs on that target. A single NDB deployment can manage multiple registered Nutanix clusters; deploying another NDB appliance for every cluster is unnecessary. Database HA on the original cluster does not make an additional cluster available, and a protection domain is a data-protection construct rather than the NDB onboarding mechanism. Nutanix’s cluster-registration documentation explicitly requires registering the target cluster before databases can be provisioned there. Therefore, option C is the required preparatory action. Nutanix cluster-registration documentation

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.

Nutanix Era leverages the Nutanix time-efficient snapshots to create the clones1. These database clones are highly space-efficient, consuming near-zero bytes by having only the further writes constituting to its size1. Therefore, an administrator would find the total space being used by all Era clones for a specific database under the Cloning widget on the Databases > Clones database summary page. The other options do not specifically provide information about the total space used by all Era clones for a specific database. Therefore, the correct answer is A. Under the Cloning widget on the Databases > Clones database summary page.

Selecting Group Database with One Time Machine associates multiple SQL Server databases with one protection construct rather than separate Time Machines. Nutanix explicitly recommends grouping databases when they share protection requirements because the arrangement provides optimized RPO and improved performance. It also lets the group be protected, cloned, and recovered consistently under one SLA and one snapshot and log-catch-up schedule. Reduced storage consumption may occur as a secondary operational effect, but it is not the documented key architectural benefit. Faster provisioning is likewise not the principal reason for creating a database group, and independent recovery contradicts the group model because the databases share the same Time Machine. Therefore, optimized RPO and performance is the only option that matches Nutanix’s documented guidance for database groups.

Nutanix Database Automation (NCP-DB) simplifies database provisioning using predefined profiles customized to your environment. Software profiles, which are templates of the OS and database engine, allow you to maintain consistent software versions1. You then use additional profiles to customize that deployment1.

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) v7.5Blueprint, 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.

To create a Microsoft SQL Server software profile for each of the three Nutanix clusters in an NDB environment, a key requirement is that each cluster must host at least one VM with the Microsoft SQL Server database engine installed. NDB uses these VMs to discover, validate, and generate software profiles tailored to the specific SQL Server versions and configurations present on each cluster. This ensures that the profiles are compatible with the cluster’s environment and can be used for provisioning or patching.

Option A (Compute profile must be created first on every cluster) is incorrect because compute profiles are optional and not a prerequisite for creating software profiles.

Option B (Enable Multi-cluster capabilities for NDB) is incorrect as multi-cluster support is already implied by the deployment across three clusters, but it’s not a specific requirement for profile creation.

Option C (Enable High Availability for the current NDB Service) is incorrect because HA is a separate configuration and not required to create software profiles.

Option D (Each cluster must host a VM with the DB engine) is correct as it aligns with NDB’s requirement to have a reference VM for profile generation.

This setup ensures accurate and cluster-specific software profile creation.

References

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

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

For a point-in-time SQL Server database-group clone, NDB treats the selected databases as one coordinated recovery set. It uses the group’s Time Machine and transaction-log backups to recover every member to the same requested timestamp. Applying a common recovery boundary preserves cross-database point-in-time consistency; each database represents the group at that moment rather than at a separately selected time. Nutanix documents that full or partial SQL Server database-group clones can be created to a point in time by using transaction logs. NDB does not merge databases into one MDF file, require a deliberate delay between clones, or rely solely on quiescing all members for this point-in-time workflow. Therefore, option C is correct. Nutanix SQL Server database-group clone documentation

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

The "Savings over traditional cloning" metric in the Data Usage widget on the NDB dashboard reflects the efficiency of NDB’s cloning technology compared to traditional full-copy cloning methods. NDB leverages Nutanix’s near-zero byte cloning capability, which creates lightweight clones by sharing base data and only storing changes (deltas). This metric specifically quantifies the disk space saved by using these efficient clones instead of duplicating entire datasets, as would occur in traditional cloning. It highlights NDB’s storage optimization for database provisioning and management.

Option A is correct as it directly ties to NDB’s near-zero byte cloning technology, a core feature for space efficiency.

Option B (Compression) is incorrect because compression is a separate storage optimization technique not specifically tied to cloning savings.

Option C (Shadow clones) is incorrect because shadow clones are a Nutanix feature for caching, not the cloning mechanism used by NDB Time Machines.

Option D (Deduplication) is incorrect as deduplication, while related to storage savings, is not the primary mechanism reflected in this cloning-specific metric.

This metric helps administrators quantify the benefits of NDB’s cloning approach in terms of storage utilization.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Introduction to NDB, Section: Understanding Cloning and Storage Efficiency

Nutanix Support & Insights, Technical Note: "Interpreting NDB Dashboard Metrics"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 1: NDB Concepts and Architecture

When restoring a PostgreSQL HA instance in NDB, if the standby node fails to restore but the primary node is successfully restored and ready to serve application traffic, NDB considers the database operational from the perspective of the primary node. In this scenario, NDB leaves the database in an "ONLINE" state, reflecting that the primary node is functional and capable of handling requests, even though the HA configuration is not fully intact due to the standby failure. The administrator would need to address the standby node separately (e.g., by re-provisioning or troubleshooting), but the database’s state is determined by the primary node’s readiness.

Option A (PAKFIAL.READY) appears to be a typo and is not a valid NDB state.

Option B (OFFLINE) is incorrect because the primary node is operational, so the database is not offline.

Option C (ONLINE) is correct as it reflects the primary node’s ability to serve traffic.

Option D (RECOVERY PENDING) is incorrect because the primary node has completed recovery and is active, not pending.

This behavior aligns with NDB’s focus on maintaining service availability where possible.

References

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

Nutanix Support & Insights, Knowledge Base Article: "Handling Partial Restore Failures in PostgreSQL HA"

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

NDB deployments on NC2 use overlay networking created with Nutanix Flow Virtual Networking. Consequently, an appropriate Flow overlay subnet must be created for NDB and the database server VMs that it will manage. A floating IP address must also be created or assigned to the NDB VM so that the NDB interface and services are reachable through the cloud networking environment. A Flow underlay subnet is not the supported network type for this deployment. Although an NC2 environment ultimately operates within AWS networking infrastructure, creating a native AWS VPC is not the NDB-specific deployment step requested by the question. Nutanix’s NC2 networking documentation identifies Flow-created overlay networks, while the Flow integration guidance describes assigning a floating IP address to the NDB VM.

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) v7.5Blueprint, Section 3: Configure an NDB Environment

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) v7.5Blueprint, Section 3: Configure an NDB Environment

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.

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.

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) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.3: Configure Backup Storage Options (applicable to v7.5).

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

 The database parameters profile is used to define the initialization variables for different types of database engines and workloads, such as OLTP and DW. The database parameters profile allows the database administrator to customize the configuration settings for each database engine, such as Oracle, SQL Server, PostgreSQL, and MySQL. The database parameters profile can also be applied to different database operations, such as provisioning, cloning, and patching. The database parameters profile helps to optimize the performance and functionality of the databases according to the specific requirements and best practices of each database engine and workload.

The software profile version is used to define the software version and edition for each database engine, such as Oracle 19c Enterprise Edition or SQL Server 2019 Standard Edition. The software profile version is required for provisioning new databases and patching existing databases. The software profile version helps to ensure the compatibility and compliance of the databases with the supported software versions and editions.

The network profile is used to define the network configuration and security settings for the database server VMs and the databases, such as the IP address, subnet mask, gateway, DNS, firewall rules, and SSL certificates. The network profile is required for registering new database server VMs and provisioning new databases. The network profile helps to ensure the connectivity and protection of the database server VMs and the databases within the network environment.

The compute profile is used to define the compute resources and storage policies for the database server VMs and the databases, such as the CPU, memory, disk size, disk type, compression, deduplication, and replication factor. The compute profile is required for provisioning new databases and cloning existing databases. The compute profile helps to ensure the availability and efficiency of the database server VMs and the databases within the Nutanix cluster.

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

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

To deploy Nutanix Database Service (NDB) in Prism Element, the minimum account access level required is Cluster Administrator. This role provides the necessary permissions to manage cluster resources (e.g., storage, networking, and VMs) required for NDB deployment, including registering the cluster with NDB, configuring storage containers, and deploying NDB components. Lower roles like Viewer or Backup Administrator lack the scope to perform these tasks, and User Administrator is focused on user management, not deployment.

Other options are insufficient:

A. User Administrator: Manages users and roles, not cluster operations.

C. Viewer: Read-only access, inadequate for deployment.

D. Backup Administrator: Limited to backup tasks, not deployment.

Thus, the verified answer is B, aligning with NDB deployment prerequisites.

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.

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

Nutanix NDB Installation Guide: "Prism Element Role Requirements" section.

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

The exhibit shows the "Create Snapshot" interface in NDB, where the administrator can select Nutanix clusters where the snapshot should be made available. However, only a single cluster appears despite multiple clusters in the environment. The most likely reason is that NDB Multi-cluster has not been enabled. Multi-cluster support in NDB requires explicit configuration to enable snapshot replication and data availability across remote clusters (e.g., via Prism Central and network profiles). Without this, NDB restricts snapshot operations to the local cluster where the database resides.

Other options are less likely:

A. The remote clusters are running ESXi: NDB supports ESXi clusters, so this alone wouldn’t limit visibility unless multi-cluster is disabled.

B. The snapshot will be too big to replicate to a remote cluster: Size is a consideration during replication, but it doesn’t prevent cluster visibility in the UI.

D. The remote clusters have an older version of AOS installed: Version compatibility might affect replication, but it wouldn’t hide clusters from the list unless multi-cluster setup is incomplete.

Thus, the verified answer is C, pointing to the need for multi-cluster configuration.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "Enabling Multi-Cluster Snapshot Replication" section.

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.

A Time Machine is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention. When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de-registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze. 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: Time Machine Concepts

Nutanix Support & Insights, TN-2101: Nutanix Database Service Time Machine Under the Hood, Section: Time Machine States and Transitions

An administrator needs to provision multiple database clones from the same source database for different purposes (e.g., QA and Test/Development) while avoiding resource starvation by differentiating VM resources for each department. The most efficient way to achieve this is by creating multiple Compute profiles in NDB. Compute profiles define CPU, memory, and other resource allocations for VMs, allowing the administrator to tailor resource limits (e.g., higher resources for QA, lower for Development) and apply them during clone provisioning. This approach is built into NDB, ensuring consistent resource management without manual adjustments.

Option A (Create multiple Compute profiles) is correct as it provides a scalable and efficient way to allocate resources per department.

Option B (Leverage NCM Self Service to deploy database clones) is incorrect because Nutanix Cluster Management (NCM) Self Service is for end-user provisioning, not resource differentiation.

Option C (Use a VM Template for each department) is incorrect because VM templates are less flexible and not natively integrated with NDB clone provisioning.

Option D (Generate a playbook to resize database VMs when released) is incorrect because playbooks are for automation, not initial resource allocation, and resizing post-provisioning is less efficient.

This method optimizes resource use across departments.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Configuring Compute Profiles

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

NDB requires the administrator to verify the Active Directory configuration before enabling the Save action. After entering the directory server, domain, service-account credentials, and related configuration information, the administrator must click Verify. NDB then tests whether it can connect to the Active Directory server and authenticate using the supplied service account. The Save button becomes available only after this verification succeeds. This prevents an unreachable server, invalid credential, incorrect domain, or connectivity problem from being stored as the active authentication configuration. SMTP alerting is a separate notification feature and has no dependency on Active Directory configuration. A secondary URL is not a mandatory field, and providing a domain IP address alone does not replace the connectivity-verification step. Nutanix documents this sequence explicitly in its official procedure for configuring Active Directory access.

In this scenario, a PostgreSQL instance managed by NDB on a Linux VM is malfunctioning after a manual OS update, and a new Linux DB server VM has been prepared to host the data. To migrate the data to the new VM, the administrator must integrate the new VM into NDB’s management framework. The correct action is to register the new DB Server VM in NDB, which allows NDB to recognize and manage the VM as a database server. Once registered, the administrator can use NDB’s features (e.g., cloning, restoring, or reprovisioning) to migrate the data from the broken instance to the new VM.

Here’s why the other options are incorrect:

A. Provision a new PostgreSQL instance from the Databases page: This creates a fresh instance without migrating existing data, losing the broken instance’s data unless separately restored.

B. From The Machine policy, Authorize Database Server VMs: Machine policies in NDB define rules for VM management, but authorizing VMs is not a direct migration action and assumes prior registration.

C. Follow the Provision a PostgreSQL Instance wizard: Similar to A, this provisions a new instance rather than migrating data to an existing prepared VM.

Registering the new VM in NDB (via the "Database Server VMs" section) enables the administrator to associate it with the existing PostgreSQL instance’s configuration and perform a data migration (e.g., using a snapshot or backup). This aligns with NDB’s workflow for replacing a broken server. Thus, the verified answer is D.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.3: Registering and Managing Database Server VMs.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.2: Register and Manage DB Server VMs (applicable to v7.5).

Nutanix NDB Administration Guide: "Registering a Database Server VM" 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) v7.5Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v7.5).

Nutanix NDB Administration Guide: "Patching Microsoft SQL Server" section.

NDB supports centralized drive-letter customization for SQL Server through the NDB server CLI global configuration. Nutanix documents this as the supported method for setting the database, log, backup, and TempDB drive letters used by NDB-managed provisioning and clone workflows. After the administrator changes the global values, NDB applies those assignments when it prepares eligible SQL Server database server VMs. The drive letters are not supplied interactively during each provisioning operation, stored in a Windows Domain Profile, or introduced merely by adding disks to a Software Profile. Therefore, option A is correct. The candidate file’s supplied answer B conflicts with the documented NDB configuration method and has been corrected. Nutanix SQL Server limitations

Nutanix Database Service (NDB) supports high availability (HA) instances for certain relational database management systems (RDBMS). Among the listed options, NDB natively supports Oracle and PostgreSQL for HA configurations, enabling features like replication and failover. These databases are well-integrated with NDB’s Time Machine and HA frameworks.

Option A (MongoDB) is incorrect because MongoDB is a NoSQL database, not an RDBMS, and is not supported for HA instances in NDB.

Option B (MariaDB) is incorrect because, while MariaDB is an RDBMS, it is not currently supported for HA instances in NDB v7.5.

Option C (Oracle) is correct as NDB supports Oracle in HA mode with features like Data Guard integration.

Option D (PostgreSQL) is correct as NDB supports PostgreSQL HA with streaming replication.

Note: The typo "PostgreSGL" in the question is assumed to mean "PostgreSQL" based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Supported RDBMS for HA

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

In NDB, a Time Machine manages snapshots and log catch-up operations for database protection and recovery. The scenario describes a Time Machine where automatic snapshot and log catch-up activities (both automatic and manual) are halted, and manual snapshots cannot be created. This indicates the Time Machine is in a PAUSED state.

In NDB, the Time Machine states are:

FROZEN: A temporary state during specific operations (e.g., cloning), but it doesn’t halt all activities permanently.

OFFLINE: Indicates the Time Machine is unavailable or not operational, often due to connectivity or configuration issues, but this typically prevents access rather than just halting operations.

PAUSED: Explicitly stops all scheduled and manual snapshot/log activities, often manually triggered by an administrator or due to an error condition (e.g., resource constraints). Operations resume when unpaused.

READY: The normal operational state where snapshots and log catch-ups occur as scheduled.

Given the inability to create manual snapshots alongside halted automatic operations, PAUSED is the most fitting status, as it reflects an intentional or enforced suspension of activities.

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) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Time Machine States (applicable to v7.5).

Nutanix NDB Administration Guide: "Time Machine Statuses and Operations" section.

NDB supports patching for PostgreSQL database instances. Patching for PostgreSQL is validated on VMs provisioned by NDB (greenfield deployments). To patch PostgreSQL database server VMs, you must create a software profile version by uploading the PostgreSQL update file in NDB. You can then use the PostgreSQL update to patch other database server VMs or provision a new database server VM with the updated software profile. The first step in the NDB patching workflow is to create a software profile version with the desired PostgreSQL version.

Nutanix Database Automation (NCP-DB) Course Details, Section 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.1: Perform Database Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) User Guide, Section 4.4: Patch PostgreSQL Database Software

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.

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.

A Log Catchup gap in Nutanix Database Service (NDB) occurs when transaction logs are missing or corrupted, disrupting point-in-time restore (PITR) operations for cloning or database restoration via Time Machine. The NDB Time Machine Heal Snapshot feature addresses this by repairing snapshots to resolve such gaps.

Option A (By default the time machine auto-heal feature is enabled) is incorrect because the auto-heal feature is not enabled by default; it requires explicit configuration or manual invocation.

Option B (Manual Heal is only used when gaps in Log Catchup are detected once the operation has begun failing) is incorrect because manual heal can be initiated proactively or reactively, not solely after failure detection.

Option C is correct because a successful Time Machine Heal process restores the snapshot integrity, allowing PITR to span the previously gapped period.

Option D is correct as the auto-heal process, when enabled, runs every 5 minutes to detect and address healable conditions, aligning with NDB’s automated maintenance schedule.

Together, C and D reflect the operational mechanics of the Heal Snapshot feature.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Healing Snapshot Gaps

Nutanix Support & Insights, Knowledge Base Article: "Resolving Log Catchup Gaps with Time Machine Heal"

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

The image provided shows the "Register Database Server VM" interface in NDB, which includes fields for registering a database server, including options for Windows and SQL Server credentials. When an administrator wants to register a database using a SQL Server User (instead of Windows credentials), the appropriate place to specify this user is in the "Connect to SQL Server Login" section. The interface includes a "User Name" field under this section, which becomes relevant after selecting the option to use a SQL Server User (typically indicated by a radio button or dropdown, though not fully visible in the image). This allows NDB to authenticate and manage the SQL Server instance using database-specific credentials rather than relying solely on Windows Administrator credentials.

Option A (In the Windows Administrator Name field) is incorrect because this field is intended for Windows OS-level credentials, not SQL Server-specific login credentials.

Option B (In the Login field after selecting SQL Server User) is correct as it aligns with the "Connect to SQL Server Login" section in the interface, where the SQL Server User can be specified after the appropriate option is selected.

Option C (Only via the command line registration option) is incorrect because the GUI provides a direct method to specify SQL Server credentials, as shown in the image.

Option D (By modifying the code in the API Equivalent section) is incorrect because the API Equivalent section is for reference and does not allow real-time modification; it’s meant to guide API-based automation, not manual registration.

The image confirms the presence of a "User Name" field under "Connect to SQL Server Login," supporting the use of a SQL Server User for registration.

References

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

Nutanix Support & Insights, Knowledge Base Article: "Registering SQL Server VMs with NDB Credentials"

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

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.

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

Nutanix Era offers Role-Based Access Control capabilities by organically embedding them in the product. It provides the ability to add and remove users from Era, create and assign roles to users, and associate various privileges with a role1. The default roles available within Era for Role-Based Access Control are:

prism Admin

Era Super Admin

Era Database Admin

Era Infrastructure Admin1 These roles allow for the management of both physical resources like IP addresses and VLANs along with database entities like databases, time-machines, clones, and so on1.

NDB supports database and database server VM deployment on NC2 on Azure by using overlay networks created through Nutanix Flow Virtual Networking. A Flow overlay subnet provides the logical network used by the NDB-managed database server VMs while allowing the networking configuration to operate consistently within the NC2 environment. Flow underlay subnets are not the supported choice for this NDB deployment model. AHV IP Address Management is associated with AHV-managed networks and does not represent the required NC2 on Azure networking type. Azure-native networking exists beneath the NC2 infrastructure, but NDB-managed database provisioning uses the Flow overlay network exposed within NC2 rather than directly attaching database VMs to a native Azure network. Nutanix’s official NDB on NC2 documentation confirms support for Flow Virtual Networking overlay networks on NC2 environments.

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

Creating a point-in-time clone is the correct nondisruptive recovery action. NDB Time Machine combines snapshots with captured Oracle archive logs to construct a database at a selected recoverable timestamp. Choosing 2:10 PM replays the available logs only through that moment, which precedes the 2:15 PM DROP TABLE. Because the result is a separate clone, the production database remains online and unchanged while the administrator extracts and returns the missing table data. A restore would rewind the source database itself and could interrupt or overwrite its current state. Refresh applies to an existing clone rather than creating the required recovery copy, while a Software Profile defines database software instead of transactional content. Nutanix’s Oracle cloning guidance therefore supports option D. Nutanix Oracle clone documentation

When an administrator needs to restore databases provisioned with a shared disk configuration on Windows Storage Spaces in Nutanix Database Service (NDB), the restore operation focuses on the disks associated with the database. Windows Storage Spaces provides a virtualized storage layer, and NDB manages the restoration by reverting or recovering the specific disks that host the database files and logs. This ensures that the database is restored to its previous state using the snapshot or backup data, while preserving the shared disk configuration integrity. NDB does not replace the source volume or perform additional operations like tail log backups unless explicitly configured.

Option A (NDB restores the disk that are associated with the database) is correct as it accurately describes NDB’s restore behavior for shared disk setups.

Option B (NDB copies the DB files to be restored to the source volume) is incorrect because NDB restores the entire disk state, not just copying files to the source.

Option C (NDB replaces the source volume with the snapshot volume) is incorrect because NDB restores data to the existing volume, not replacing it entirely.

Option D (NDB performs Tail Log backup to backup any remaining logs) is incorrect because tail log backups are not automatically part of the restore process unless specified for point-in-time recovery.

This approach ensures compatibility with Windows Storage Spaces configurations.

References

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

Nutanix Support & Insights, Knowledge Base Article: "Restoring Windows Storage Spaces in NDB"

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

 Nutanix Database Automation (NCP-DB) introduces the concept of MS SQL Server database groups, which allows multiple databases running in the same database instance to be grouped as one Time Machine entity1. This applies to both single DB Server VM setups, standalone databases, as well as to Availability Group databases1. However, it does not support Point In Time Recovery (PITR)-based Service Level Agreements (SLAs) for database groups containing mixed Recovery Models. This means that if the databases within the group have different recovery models, PITR-based SLAs cannot be applied to the group as a whole.

During MySQL HA provisioning, NDB creates the database or schema identified by the Database Name supplied in the provisioning workflow. In MySQL terminology, CREATE DATABASE and CREATE SCHEMA are equivalent, so using the intended default schema as the database name gives developers the required schema as part of the managed deployment. A post-create script could create additional objects, but it is unnecessary for the initial default schema and adds avoidable custom automation. The provisioning workflow does not require uploading a SQL file, and a software profile packages database software and operating-system binaries rather than application schemas. Therefore, the default schema should be defined as the database name. This keeps schema creation within NDB’s declarative provisioning workflow and makes the resulting database manageable as part of the MySQL HA instance. Nutanix uses the Database Name field for this purpose.

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.

 In Nutanix Era, the ability to add a new VLAN or IP Pool is typically associated with the role of an Infrastructure Administrator12. This role has the necessary permissions to manage network configurations, including the creation of VLANs and IP Pools12. It’s important to note that the exact permissions may vary depending on the specific configuration and policies of your organization12.

NDB Time Machine protects Microsoft SQL Server databases through application-consistent snapshots and a continuous sequence of transaction-log backups captured by Log Catch-up operations. When the latest protected time is selected, NDB uses the appropriate snapshot as the baseline and applies the required transaction logs through the most recent available recovery point. This produces a transactionally consistent clone rather than a crash-consistent VM copy. NDB does not need to leave the source database in read-only mode, and Volume Shadow Copy Service alone cannot provide the transaction-log replay required for granular point-in-time cloning. “Latest Time” means the latest point covered by the valid Time Machine snapshot and log chain, not an unprotected wall-clock instant after the last log capture. Nutanix’s Database Log Backup Management documentation explains that Log Catch-up captures database transaction logs for point-in-time cloning.

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

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

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

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

 NDB supports 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

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

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

When creating a Network Profile for NDB HA VMs (e.g., NDB API and Repository VMs) spread across three Nutanix clusters, the required type is PostgreSQL HA instance managed outside NDB. NDB HA relies on a PostgreSQL database for its control plane, and in a multi-cluster HA setup, this PostgreSQL instance must be configured for high availability (e.g., using streaming replication) outside NDB’s management. The Network Profile must support this external HA instance’s networking requirements (e.g., VLANs, IP ranges) to ensure connectivity across clusters.

Other options are incorrect:

A. PostgreSQL HA instance managed in NDB: NDB manages database instances, not its own HA control plane database.

B. PostgreSQL single instance managed in NDB: A single instance lacks HA, unsuitable for multi-cluster.

D. PostgreSQL single instance managed outside NDB: Lacks HA, insufficient for NDB HA VMs.

Thus, the verified answer is C, aligning with NDB HA architecture.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "Network Profile Configuration for HA VMs" section.

When completing the NDB (Nutanix Database Service) Wizard for initial setup or configuration, certain steps are mandatory to ensure the environment is properly configured, while others are optional based on specific needs. Network Segmentation is an optional step that allows for advanced network isolation and configuration, but it is not required for basic NDB deployment. Mandatory steps include specifying the NDB Cluster Name, selecting a Storage Container, and configuring Services (e.g., database services), as these are essential for NDB to function and manage databases.

Option A (Network Segmentation) is correct as it is an optional feature for advanced networking, not a required step in the wizard.

Option B (NDB Cluster Name) is incorrect because assigning a cluster name is a mandatory step to identify the NDB instance.

Option C (Storage Container) is incorrect because selecting a storage container is required for data storage and protection.

Option D (Services) is incorrect because configuring services (e.g., database engines) is a core requirement for NDB operation.

Note: The question mentions "NDE Wizard," which is assumed to be a typo for "NDB Wizard" based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Deploying NDB, Section: Completing the NDB Wizard

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

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) v7.5Blueprint, Section 4: Manage Database Engines

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.

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

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.

NDB can leverage snapshots and transaction logs to refresh a database clone to the latest state of the source database. Snapshots are point-in-time copies of the database that are stored on the Nutanix cluster. Transaction logs are records of the changes made to the database after the snapshot was taken. NDB can use either snapshots or transaction logs, or a combination of both, to refresh a database clone. Cerebro logs and templates are not used for refreshing database clones. Cerebro logs are used for log catch-up operations, which are different from refresh operations. Templates are used for provisioning new databases, not for refreshing existing ones. References:

Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.3 - Refreshing Clones

Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Clone Database Management

When registering a Nutanix cluster with NDB, a manual storage mapping between the remote container and the NDB provisioning container is required if the NDB Server container and NDB Provisioning container are separate. This separation occurs when the storage containers used by the NDB server (for its own operations) and the provisioning container (for database VMs) are distinct, either due to multi-cluster setups or custom configurations. Manual mapping ensures NDB can correctly allocate storage resources and manage database provisioning across these containers.

Other conditions do not necessitate manual mapping:

B. Disaster Recovery Network Segmentation is enabled on the cluster: This affects networking, not storage mapping.

C. Nutanix Database Service High Availability is enabled on the cluster: HA configurations handle replication, not container mapping.

D. DB VMs are stored in the NDB Server or NDB Provisioning container: This is a typical setup and does not require manual mapping unless containers differ.

Thus, the verified answer is A, addressing storage container separation.

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.

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

Nutanix NDB Administration Guide: "Storage Container Mapping" section.

The first NDB management-plane VM on an AHV-based Nutanix cluster is deployed from the NDB QCOW2 disk image. The administrator downloads the QCOW2 image from the Nutanix Support portal, configures it through the Prism Element Image Service, and then creates the NDB VM from that image. QCOW2 is the appropriate virtual-disk format for AHV because AHV uses the KVM virtualization stack. VMDK is principally associated with VMware virtual disks, VHDX is used by Microsoft Hyper-V, and VDI is associated primarily with Oracle VirtualBox. Those formats are not used for the initial NDB VM deployment on a dedicated AHV cluster. Consequently, option C is correct. The VM must subsequently receive the required compute, network, and static-IP configuration before NDB initial setup is completed. NDB User Guide—Installing NDB on AHV

================

The correct answer is B because the Time Machine feature of NDB collects logs and snapshots from databases and stores them in a distributed file system. The Time Machine enables the administrator to protect, clone, and restore databases using the SLA policies and the NDB UI or API. The Time Machine also manages the replication of database snapshots in an NDB multicluster environment. The other options are not correct because they describe different features or functions of NDB. Option A is not correct because Database Restore is an operation that uses the Time Machine to restore a source database or a clone to a previous point in time. Option C is not correct because SLA is a policy that defines the frequency and retention of database snapshots and logs. Option D is not correct because One-click Patching is a feature that allows the administrator to test, publish, and apply database patches using the NDB UI or API. 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.

To apply the latest OS security patches on a Windows server managed by NDB, the user should create and apply a Maintenance Plan within the NDB interface. NDB provides a Maintenance Plan feature that allows administrators to schedule and automate OS patching for database server VMs, ensuring patches are applied in a controlled manner without disrupting database operations. This includes validating the patch process, rolling back if needed, and maintaining compliance with security standards. The plan can be configured to target the specific Windows server and include the latest security updates from Microsoft.

Other options are incorrect or insufficient:

A. Reboot the system: A reboot alone does not apply patches; it may only activate previously installed updates.

C. Update the database: This focuses on database software, not OS security patches.

D. Use update functionality directly on the VM: Manual updates bypass NDB’s control, risking inconsistency and potential downtime without proper validation.

Thus, the verified answer is B, leveraging NDB’s centralized maintenance capabilities.

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) v7.5Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v7.5).

Nutanix NDB Administration Guide: "Maintenance Plans for OS Patching" section.

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) v7.5Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Configure Network Profiles (applicable to v7.5).

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

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

Other options are incorrect:

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

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

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

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

Official Nutanix Database Automation References

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

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

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

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

Nutanix NDB Installation Guide: "Running the Linux Prerequisites Script" section, detailing -t usage.

A SQL Server Database Group in NDB is a logical protection construct for databases that have common recovery-point and retention requirements. The databases are managed by one collective Time Machine and SLA, allowing NDB to coordinate snapshots and log backups and reduce Time Machine sprawl. However, grouping does not merge all database files into one common virtual-disk set. Each database retains its own set of storage disks while participating in the group-level protection workflow. The group also does not force databases onto different Always On Availability Group nodes, and it does not prevent an administrator from restoring or cloning an individual database. Those facts eliminate A, B, and C. Option D correctly describes separate per-database storage combined with centralized Time Machine management. Nutanix NDB Database Groups

A new web application with up to 200 concurrent connections to a PostgreSQL database requires a robust and scalable configuration. Provisioning a PostgreSQL HA (High Availability) instance in NDB is the most effective action to achieve this goal. An HA instance leverages replication (e.g., streaming replication) to distribute load and ensure availability, accommodating high concurrency by allowing multiple nodes to handle traffic. This approach simplifies configuration compared to manual scripting or parameter adjustments.

Option A (Use Post Create Command when provisioning the DB) is incorrect because post-create commands are for custom scripts, not optimal for handling concurrent connections.

Option B (Create a new Database Parameters profile) is incorrect because while it can tune settings, it’s less efficient than HA for scaling concurrency.

Option C (Edit the API equivalent shell script) is incorrect as it’s a manual and error-prone method compared to HA provisioning.

Option D is correct because a PostgreSQL HA instance natively supports high concurrency and availability.

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) v7.5Blueprint, Section 4: Manage Database Engines

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) v7.5Blueprint, Section 4: Manage Database Software Profiles

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.

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.

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

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) v7.5Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.2: Navigate the NDB UI (applicable to v7.5).

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

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

The Storage Usage widget on the NDB dashboard provides the required entity-level storage information. It displays the percentage of storage consumed by registered Nutanix clusters and NDB entities, including source databases, database clones, and Time Machines. Administrators can use this information to distinguish production database capacity from space consumed by protected copies and downstream clones. NDB periodically collects and stores historical usage information, which also supports storage-trend analysis and capacity forecasting. Prism Element and Prism Central provide infrastructure-level capacity information, but they do not present the same NDB-aware classification of source databases, clones, and Time Machines. NCM reporting is therefore unnecessary for this specific requirement. The official NDB Dashboard reference identifies Storage Usage as the dashboard widget that reports consumption for clusters, data sources, clones, and Time Machines.

The administrator should begin with the NDB dashboard because its Storage Usage information provides a consolidated view of capacity consumed by registered clusters and NDB-managed entities. The dashboard distinguishes consumption associated with source databases, clones, and Time Machines, making it the fastest location for identifying the largest storage consumers before investigating an individual entity. Database Server Details focuses on a selected server and does not provide the same environment-wide comparison. Time Machine Properties applies only to a particular protection entity, while Software Profile Management concerns database software images and versions rather than database storage consumption. NDB also records historical storage information, enabling administrators to assess trends and determine whether capacity pressure is increasing. Nutanix’s official NDB Dashboard documentation confirms that the Storage Usage view reports consumption for data sources, clones, Time Machines, and registered Nutanix clusters.

When provisioning a PostgreSQL HA Instance using NDB, the minimum and maximum number of DB server VMs that can be deployed in a cluster are 2 and 4, respectively. A PostgreSQL HA Instance is a database instance that provides high availability and fault tolerance for PostgreSQL databases using the Patroni framework. Patroni is a Python-based tool that manages PostgreSQL configuration and performs automatic failover and switchover operations. Patroni relies on a distributed consensus store, such as etcd, Consul, or ZooKeeper, to store and synchronize the cluster state and leader information. NDB supports etcd as the consensus store for PostgreSQL HA Instances. NDB allows the administrator to provision PostgreSQL HA Instances with different sizes and configurations, such as small, medium, large, or custom. The size of the PostgreSQL HA Instance determines the number of DB server VMs, the number of etcd nodes, the CPU, memory, and disk resources, and the replication factor of the database. The minimum number of DB server VMs for a PostgreSQL HA Instance is 2, which corresponds to a small size instance. This configuration provides one leader and one follower DB server VM, and one etcd node. The maximum number of DB server VMs for a PostgreSQL HA Instance is 4, which corresponds to a large size instance. This configuration provides one leader and three follower DB server VMs, and three etcd nodes. The other options are not valid for a PostgreSQL HA Instance, as they either do not provide enough redundancy or exceed the supported limit of DB server VMs. 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: Provisioning PostgreSQL HA Instances

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

[PostgreSQL High Availability: Under the Hood – Nutanix.dev], Section: PostgreSQL HA Architecture and Components

NDB requires management and storage connectivity to a registered Nutanix cluster. TCP 9440 carries Prism REST API communication between NDB components and the Nutanix cluster. TCP 3205 and 3260 support iSCSI redirection/data and standard iSCSI control traffic used when NDB attaches Volume Group disks. Therefore, both option B and option D must be allowed through the segmented network. Port 443 is used for HTTPS communication in other NDB paths, but it is not the required Prism/CVM port represented by this question. Ports 1433 and 5432 are database listener ports for Microsoft SQL Server and PostgreSQL, respectively, rather than NDB-to-CVM infrastructure ports. The source answer “D” is incomplete; the verified answer is B and D. Nutanix port reference

================

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

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

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

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

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

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

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

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

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

 The 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

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.

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

NDB supports email-based alert notifications through a configured Simple Mail Transfer Protocol server. Administrators provide the SMTP server and sender information in NDB and then configure notification policies or recipient addresses for applicable alerts. This enables operational events, failures, and warning conditions to be delivered directly to administrators without requiring them to continuously monitor the NDB console. ServiceNow, Microsoft Teams, and PagerDuty are not identified as the native notification destination represented by this question. Such platforms may be connected indirectly through external automation, email ingestion, APIs, or webhook-based integrations, but those approaches are distinct from NDB’s built-in email notification capability. The official Nutanix documentation for configuring alert notifications specifically describes configuring an SMTP server so that NDB can send notifications by email.

 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 allow a non-administrative NDB user to provision an Oracle database using a Software Profile created by an administrator, the administrator must promote the Software Profile to Published. In NDB, Software Profiles define the database software version and configuration (e.g., Oracle binaries). By default, a newly created profile is in a draft or private state. Promoting it to "Published" makes it available for use by other NDB users, including non-administrative ones, within the access control framework. This ensures the profile is validated and accessible without requiring individual user assignments.

Other options are incorrect:

A. Ensure that specified users have access to the Software Profile using Access Control: Access Control manages user permissions but does not make the profile available unless it is published.

B. Replicate the Software Profile to other Nutanix clusters: Replication is for HA or disaster recovery, not user access.

C. Ensure that the Software Profile has been properly versioned to the latest release of Oracle: Versioning ensures compatibility but does not grant user access.

Thus, the verified answer is D, aligning with NDB’s profile management workflow.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "Publishing Software Profiles" section.