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

When configuring an SMTP server for sending alert notifications via email in NDB, the two security options available are SSL and TLS. These protocols encrypt the email communication between NDB and the SMTP server, ensuring the confidentiality and integrity of alert notifications. NDB supports both options to accommodate different SMTP server configurations, with TLS being the more modern standard and SSL as a legacy option.

Other options are not applicable:

B. S/MIME: This is used for email content encryption, not SMTP server configuration.

C. DKIM: This is a domain authentication method, not a security protocol for SMTP.

Thus, the verified answers are A and D, reflecting NDB’s SMTP security features.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "Configuring SMTP for Alerts" section, listing SSL and TLS options.

Before patching several Nutanix database server VMs using the "Patch OS now" feature in NDB, the administrator must configure a Repository. A repository (e.g., a custom patch repository or Nutanix-provided source) contains the OS updates or patches (e.g., for Windows or Red Hat-based systems). NDB requires this repository to be specified to fetch and apply the patches, ensuring the database VMs are updated from a validated source.

Other options are unrelated to patching:

B. Active Directory Access: Used for authentication, not patching.

C. pulse: Refers to Nutanix Pulse for support, not patch configuration.

D. An SMTP Server: Configured for alerts, not patching.

Thus, the verified answer is A, reflecting the patching prerequisite.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.3: Creating Maintenance Plans.

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

Nutanix NDB Administration Guide: "Configuring Patch Repositories" section.

The NDB alert retention feature allows the database administrator to configure the duration for which the NDB alerts are stored and displayed in the NDB instance. The NDB alert retention feature supports alert retention globally, meaning that the same retention period applies to all the alerts generated by the NDB instance, regardless of the source cluster, policy, or operation. The database administrator can set the alert retention period from 1 day to 365 days, or choose to retain the alerts indefinitely. The NDB alert retention feature helps to manage the storage space and the visibility of the NDB alerts.

The NDB alert retention feature does not support retention at the individual policy, grouped policy, or registered cluster level. The NDB alert retention feature applies to all the alerts uniformly, and does not allow the database administrator to specify different retention periods for different policies or clusters.

References:

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

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

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

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

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

 In Nutanix Database Automation (NCP-DB), the Database Parameters profile is used to manage database-specific settings, including the maximum number of database connections. This profile would be the appropriate choice when an administrator needs to change these settings during the cloning workflow1.

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

References:

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

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

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

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

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

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

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

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

 According to the Nutanix Database Automation (NCP-DB) learning documents, when dealing with an Availability Group (AG) database, the database should be registered as an Availability database1. This is because the AG database is hosted on replicas with different named instances, and registering it as an Availability database allows for Copy Data Management operations to be performed across all instances. This is particularly important when services such as the Analytics service running on SQLAGN3\DW require real-time data1.

The Global Service Level Agreement (SLA) feature of Era allows an administrator to create Time Machine policies in a Multi-Cluster configuration1. This feature provides a unified way to manage and enforce backup and replication policies across multiple clusters, ensuring consistent data protection and recovery across the entire environment1.

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) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.2: Register and Manage DB Server VMs (applicable to v6.10).

Nutanix NDB Administration Guide: "Registering a Database Server VM" section.

When using the "Patch OS now" feature in NDB to apply updates to a Red Hat-based operating system, the administrator can limit updates to security patches only by leveraging the Advanced Options. Under the "Custom commands" section of the operating system patching command window, entering yum update --security instructs the package manager to install only security-related updates. This ensures the system remains secure without applying all available updates, which could introduce instability.

Other options are incorrect or incomplete:

A. Point the database VM to a custom patch repository and enter yum update --security command: This requires manual intervention outside NDB’s patching framework.

B. Check Advanced Options and under Pre-post commands, enter yum update security in the pre-operating system patching command window: Pre-post commands are for pre/post actions, not the main patching process, and the syntax lacks the --security flag.

C. Point the database VM to a custom patch repository before using the Patch OS now feature: This sets up a repository but doesn’t specify security-only updates within NDB’s interface.

Thus, the verified answer is D, aligning with NDB’s patching customization.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.3: Creating Maintenance Plans.

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

Nutanix NDB Administration Guide: "Patch OS Now with Custom Commands" section.

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

Other options are incorrect:

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

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

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

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

Official Nutanix Database Automation References

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

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

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

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

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

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

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

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

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

References

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

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

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

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

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.

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

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

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

When an administrator enables NDB Multi-cluster functionality, certain components are deployed or reconfigured to support the distributed environment. HAProxy (High Availability Proxy) is a critical component that manages load balancing and secure communication across clusters. In a multi-cluster setup, HAProxy is deployed on a dedicated VM to ensure efficient traffic distribution and high availability for NDB services, such as API calls and GUI access, across the clusters. This dedicated deployment enhances scalability and resilience.

Option A (Agent VM) is incorrect because Agent VMs are typically deployed on managed database VMs, not as dedicated NDB service components in multi-cluster setups.

Option B (HAProxy) is correct as it is specifically deployed on a dedicated VM to handle load balancing in a multi-cluster NDB environment.

Option C (Repository DB) is incorrect because the Repository DB is part of the NDB control plane and not necessarily deployed on a separate VM for multi-cluster purposes.

Option D (APIVM) is incorrect because the API VM is part of the core NDB infrastructure but not specifically deployed as a dedicated VM for multi-cluster enablement.

References

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

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

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

Here’s why the other options are insufficient:

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

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

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

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

Official Nutanix Database Automation References

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

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

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

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

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

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

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

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

Official Nutanix Database Automation References

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

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

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

In NDB, publishing a software profile update for Microsoft SQL Server makes it available for broader use within the NDB environment. When an administrator creates and publishes an updated software profile (e.g., with a new SQL Server patch or version), this action allows all authorized NDB users to leverage that profile to patch or update the database software on their managed VMs. This is a key feature of NDB’s software profile management, enabling centralized control and distribution of standardized database configurations.

Option A is correct because publishing a profile democratizes access, allowing all users to apply the update to their database VMs, aligning with NDB’s collaborative administration model.

Option B is incorrect because it suggests the profile patches itself, which is not the intent; publishing enables usage, not self-application.

Option C is incorrect because publishing does not automatically deprecate older profiles; deprecation is a separate administrative decision.

Option D is incorrect because publishing facilitates patching, not stalls it.

This process enhances efficiency and consistency in managing SQL Server updates across an organization.

References

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

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

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

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

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

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

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.3: Performing NDB Software Upgrades

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

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

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

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

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

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

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

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

References

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

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

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

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

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

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

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

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

References

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

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

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

The Nutanix Era API documentation is available on the Nutanix.dev API Reference page12. This documentation outlines the operations that are possible with the Era APIs2. In addition to the API reference, the NutanixDev code samples repo provides working code that implements the practices shown in the documentation1. The Era API Explorer is another resource that provides a comprehensive view of the available APIs, allowing users to interactively explore and test the APIs. However, there is no mention of a specific “Era GitHub API Repository” or the “Nutanix Support Portal” being used as a reference resource for Nutanix Era APIs in the provided resources. Therefore, the correct answers are B. Nutanix.dev API Reference and C. Era API Explorer.

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) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

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

 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

 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.

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

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.

References:

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

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.

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

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

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

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

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

This reflects NDB’s robust HA implementation.

References

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

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

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

In an NDB high availability (HA) environment spanning multiple Nutanix clusters, with two clusters running VMware ESXi and one running Nutanix AHV, cross-hypervisor compatibility becomes essential to manage the heterogeneous environment effectively. Nutanix Prism Central is the centralized management platform that provides a unified interface and orchestration capabilities across multiple clusters, regardless of the underlying hypervisor (ESXi or AHV). For NDB HA to function seamlessly across these clusters, Prism Central is required to coordinate cluster operations, manage resources, and ensure consistent policy enforcement, including VM placement, failover, and database management tasks. It abstracts the differences between hypervisors, enabling NDB to operate in a mixed environment.

Option A (Stretched VLANs for all nodes) is incorrect because stretched VLANs address network connectivity, not hypervisor compatibility or NDB HA management.

Option B (NGT - Nutanix Guest Tools) is incorrect as NGT enhances guest VM functionality (e.g., drivers, backups) but does not facilitate cross-hypervisor orchestration for NDB HA.

Option C (Nutanix Prism Central) is correct because it provides the necessary multi-cluster management and compatibility layer for NDB HA across ESXi and AHV.

Option D (VirtlO) is incorrect as VirtIO refers to paravirtualized drivers for VMs, not a component for NDB HA or cross-hypervisor support.

Prism Central’s role ensures that NDB can manage database workloads across diverse hypervisor platforms efficiently.

References

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

Nutanix Prism Central Administration Guide, Section: Managing Mixed Hypervisor Environments

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

According to the Nutanix Database Automation (NCP-DB) learning documents, before using Era to provision a MSSQL AG cluster, an administrator must configure a private network in Era for the heartbeat traffic1. This is because the heartbeat traffic is crucial for maintaining the health and status of the MSSQL AG cluster. The heartbeat traffic is used by the nodes in the cluster to communicate with each other and check the status of the other nodes. If a node does not receive a heartbeat from another node within a certain time frame, it assumes that the other node has failed and takes appropriate action234.

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

Other options exceed the minimum requirements:

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

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

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

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

Official Nutanix Database Automation References

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

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

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

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

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

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

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

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

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

References

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

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

The Database Agent is used to temporarily store the transaction logs of the source database before they are copied to the log. This is a critical component for ensuring data consistency and recovery in database operations.References: Nutanix Database Automation documentation, focusing on database agents and their roles in transaction log management.

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

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

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

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

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

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

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

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

 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.

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

For supported Linux-based database VMs managed by NDB, keeping software profiles updated for provisioning new database VMs requires a structured process. The administrator must first apply the necessary patches (e.g., OS updates and database engine patches) to an existing database VM for each supported database engine (e.g., PostgreSQL, Oracle). Then, a new software profile version must be created using the updated VM as the source. This new version captures the patched configuration and can be used to provision new VMs, ensuring they are deployed with the latest updates.

Option A (Create a Maintenance window under the policy menu, then under Database VM, add the database VMs to that maintenance window and check both Database and Operating system updates) is incorrect because a Maintenance Window schedules updates for existing VMs, not for updating software profiles for new provisions.

Option B (Apply patches to a database VM for each supported database engine, then create a new software profile version for each supported database VM for each one using the updated database VM as the source) is correct as it follows the standard NDB process for profile updates.

Option C (Associate the newly provisioned database VMs with a maintenance window so they are kept updated) is incorrect because this applies to ongoing maintenance, not initial profile updates for provisioning.

Option D (In the Administrator menu drop down, go the Maintenance tab and choose Download Upgrade) is incorrect because downloading upgrades is part of the patch process, not the profile creation step.

This method ensures new VMs are provisioned with the latest software configurations.

References

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

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

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

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

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

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

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

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

Official Nutanix Database Automation References

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

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

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

Before registering a database server VM to NDB, an administrator must verify that all required software (e.g., database engine, OS dependencies) and configuration settings (e.g., WinRM for Windows, SSH for Linux) are in place. NDB provides a prerequisites script, which can be run on the target VM to check these dependencies automatically. This script ensures compatibility and readiness, reducing registration failures.

Option A (LCM - Lifecycle Manager) is incorrect because LCM is used for cluster upgrades, not VM prerequisite checks.

Option B (Upgrade Software) is incorrect as it applies to updating existing software, not initial dependency verification.

Option C (Prerequisites script) is correct as it is the designated tool for pre-registration validation.

Option D (NCC - Nutanix Cluster Check) is incorrect because NCC checks cluster health, not VM-specific software dependencies.

References

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

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

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

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

The correct answer is A because the Windows Domain profile is the profile that includes information related to the SQL service startup account and the NDB worker service account. A Windows Domain profile is a collection of settings that define how NDB manages Windows-based database servers and databases. It contains the following information:

The domain name and credentials to join the database server VMs to the domain

The SQL service startup account and password to run the SQL Server service on the database server VMs

The NDB worker service account and password to run the NDB Database Agent service on the database server VMs

The SQL Server authentication mode to use for the databases

By using a Windows Domain profile, the administrator can simplify the database provisioning process by applying the same settings to multiple database server VMs and databases, without having to manually enter them each time. The other options are not correct because they describe different types of profiles that do not include information related to the SQL service startup account and the NDB worker service account. Option B is not correct because the Network profile is a profile that defines the network settings for the database server VMs, such as the IP address, subnet mask, gateway, DNS, and VLAN. Option C is not correct because the Database Parameter profile is a profile that defines the database parameters for the databases, such as the memory, CPU, storage, and performance settings. Option D is not correct because the Software profile is a profile that defines the software settings for the database server VMs and databases, such as the database engine version, edition, and features. 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 Database Services: Database modernization with Era - Now available

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

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

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

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

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

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

References:

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

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

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

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

In the Nutanix Era management interface, an administrator should perform an upgrade under the Administration > Maintenance section1. As part of the upgrade process, the Era server is upgraded first, followed by all the Era cluster agents and database server agents in parallel1. The Dashboard displays the current version and an option to upgrade the Era server to a latest version when a new version is available for upgrade1. This ensures that the Nutanix Era environment is always up-to-date with the latest features and security updates1.

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

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

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.

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

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.

According to the Nutanix Database Automation (NCP-DB) learning documents, Era provides out-of-band patching of databases to eliminate database configuration sprawl1. The two Oracle software components that Era patches are:

A. Grid home2 B. Oracle home2

These components are crucial for the operation of Oracle databases and keeping them updated ensures data security and efficient validation of critical database updates1. Please refer to the official Nutanix documentation and training materials for more detailed information2.

The Time Machine Heal function in NDB is designed to address inconsistencies or gaps in the Time Machine’s restore point chain, ensuring a continuous and reliable recovery history. It identifies and repairs missing log backups or snapshots that may have been skipped due to failures (e.g., network issues or agent errors), thereby removing gaps in the restore capability. This function does not patch software, refresh clones, or restore from malware but focuses on maintaining the integrity of the Time Machine’s data protection timeline.

Other options are incorrect:

A. Patches a Time Machine to the latest NDB levels: This is a software update, not a heal function’s purpose.

C. Refreshes a database clone in Time Machine: Clone refresh is a separate operation, not related to healing.

D. Restores a Time Machine from snapshot in the event of malware: Restoration is a distinct action, while heal addresses data gaps.

Thus, the verified answer is B, reflecting the heal function’s role in restore continuity.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "Time Machine Heal Function" section.

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.

Page files are temporary files that Windows uses to store data that does not fit in the physical memory. Page files can interfere with the registration of a database server VM with NDB, as they can cause errors or performance issues. Therefore, page files should be located in a separate drive or partition from the C:\ drive, where the NDB agent and other files are installed. System, database, and backup files do not prevent the registration of a database server VM with NDB, as long as they are not corrupted or incompatible with the NDB requirements. References:

Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2: Configuring an NDB Instance, Slide 13: Registering Database Server VMs

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.1: Apply procedural concepts to register database server VMs and databases

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

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

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

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

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

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

References

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

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

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

NDB sends alert notifications using configurations auto-populated from the cluster during the initial setup, typically relying on default SMTP settings. If a dedicated SMTP server is required (e.g., for security or compliance), the administrator must change the SMTP Server configuration in NDB Service. This is configured under the NDB Admin Center, where the administrator can specify the dedicated SMTP server’s details (e.g., hostname, port, credentials, and security settings like TLS/SSL).

Other options are incorrect:

A. IDP configuration in Admin Center IAM page: Identity Provider (IDP) settings are for authentication, not email alerts.

B. Alert Email configuration in Prism Element: Prism Element manages cluster alerts, not NDB-specific email settings.

D. SNMP configuration in Prism Central: SNMP is for network monitoring, not email notifications.

Thus, the verified answer is C, reflecting NDB’s alert notification setup.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "Configuring SMTP for Alerts" section.

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

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

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

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

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

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

References

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

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

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

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

Other options are less appropriate:

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

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

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

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

Official Nutanix Database Automation References

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

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

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

The provided exhibit shows the NDB Time Machine restore interface for October 31, 2024, with a Point-in-Time (PIT) restore option selected at 21:50. However, the restore option is unavailable, as indicated by the question. The exhibit includes a warning: "Logs to Backup: The database may contain additional logs. Backup any remaining logs before restore or they will be lost." This suggests that PIT restore requires continuous log retention, and if logs since the last snapshot (at 01:10:00) are not backed up, the restore to 21:50 cannot proceed. Running the "Logs to Backup" operation ensures all transaction logs are captured, enabling PIT restore by allowing NDB to replay logs to the desired point.

Option A (Point in time must be within the most recent range) is incorrect because the selected 21:50 is within the log retention period shown (up to the current time), but logs need to be backed up.

Option B (Selected Restore time is not available) is incorrect because 21:50 is a valid time within the log range, but log backup is the issue.

Option C (Change to snapshot option) is incorrect because switching to a snapshot limits the restore to the snapshot time (01:10:00), not 21:50.

Option D (Logs to Backup must be run first) is correct as the warning indicates that backing up remaining logs is necessary for PIT restore.

After running the backup, the administrator can proceed with the PIT restore.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Point-in-Time Restore Requirements

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting PIT Restore Issues in NDB"

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

In a Nutanix Era setup where Multi-Cluster is enabled and the Era Server storage container and Era provisioning container are different on the Era cluster, the administrator should configure a storage mapping between the Era server container and the remote container that is used for provisioning databases1. This is because Nutanix Era uses the storage container specified during the registration of the Nutanix cluster for provisioning databases1. Therefore, a storage mapping needs to be established between the Era server container and the remote container used for provisioning to ensure that the databases are provisioned correctly1.

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.

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

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

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

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

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

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

References

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

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

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

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

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

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

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

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

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

References

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

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

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

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

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

To ensure an NDB server can send periodic telemetry data to the central Nutanix repository, the server must be able to communicate with the Nutanix Insights platform over port 443 (HTTPS). The insights.nutanix.com site is the designated endpoint for telemetry data, which includes usage statistics, health metrics, and other operational data sent to Nutanix for support and analytics purposes. This connectivity is a standard requirement for NDB to comply with Nutanix’s telemetry and support framework, and port 443 is used for secure transmission.

Option A (download.nutanix.com) is incorrect because this site is used for downloading software updates, not telemetry data.

Option B (developers.nutanix.com) is incorrect as it is a resource for developers, not a telemetry endpoint.

Option C (portal.nutanix.com) is incorrect because this is the Nutanix customer portal for account management, not telemetry submission.

Option D (insights.nutanix.com) is correct as it is the specific site for sending telemetry data.

The administrator should ensure network policies allow outbound traffic to this site on port 443.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Telemetry and Connectivity Requirements

Nutanix Support & Insights, Knowledge Base Article: "Configuring Telemetry for NDB"

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