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”

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.

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

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.

In Nutanix Database Service (NDB), the Time Machine (TM) feature allows restores, including Point-in-Time (PIT) restores, which require continuous log retention to replay transaction logs to a specific moment. If the option to restore data to a Point in Time is unavailable, it indicates that the current Time Machine Service Level Agreement (SLA) does not support continuous log retention. NDB SLAs are categorized (e.g., BRONZE, SILVER, GOLD), with BRONZE or higher levels required to enable PIT restore by including continuous log retention. The administrator must update the TM SLA to at least BRONZE to enable this feature, ensuring logs are retained for PIT operations.

Option A (Restore Source DB using a snapshot) is incorrect because a snapshot-only restore does not support PIT; it restores to the snapshot time only.

Option B (Update TM SLA to BRONZE or higher) is correct as it enables continuous log retention necessary for PIT restores.

Option C (Create DB clone using a snapshot) is incorrect because cloning from a snapshot does not provide PIT capability without log retention.

Option D (Update TM SLA to BRASS or lower) is incorrect because "BRASS" is not a valid SLA tier, and lowering the SLA would not enable PIT.

This adjustment ensures PIT restore functionality.

References

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

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

The command era-server > era server set ip=ip_address gateway=gateway_address netmask=ip_netmask nameserver=ns1 ntp_server=ntp1 is used to assign a static IP address to the NDB VM via the era-server CLI. This command requires core network parameters (ip, gateway, and netmask) to configure the VM’s network interface correctly. However, optional parameters like nameserver (DNS server) and ntp_server (Network Time Protocol server) can be omitted if the administrator relies on default or externally configured DNS and NTP settings (e.g., via DHCP or another management system). These optional parameters enhance functionality but are not mandatory for the basic static IP configuration.

Option A (ntp_server) is correct as it is optional and can be configured separately or omitted if NTP is managed externally.

Option B (netmask) is incorrect because the netmask is a required parameter to define the subnet for the IP address.

Option C (gateway) is incorrect because the gateway is a required parameter to specify the network route.

Option D (nameserver) is correct as it is optional and can be omitted if DNS is handled outside NDB.

Note: The typos in the question (gatevay_address, ip_J2etmas^c, narnesetver, ntpl) are assumed to be gateway_address, ip_netmask, nameserver, and ntp1 based on context.

References

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

Nutanix Support & Insights, Knowledge Base Article: "Configuring Static IP for NDB VM"

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

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

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

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

Impact of other options:

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

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

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

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

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "High Availability Configuration Requirements" section, specifying latency limits.

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

NDB supports PostgreSQL HA software profiles for provisioning PostgreSQL databases with high availability. PostgreSQL HA software profiles consist of three components: etcd, HAProxy, and Patroni.

etcd is a distributed key-value store that provides a reliable way to store configuration data across a cluster of machines. etcd is used by Patroni to store and synchronize the cluster state and configuration.

HAProxy is a load balancer that distributes incoming requests to the PostgreSQL nodes. HAProxy is used to expose a single endpoint for database connections even as the roles of the individual nodes change.

Patroni is a template for PostgreSQL high availability. Patroni is responsible for managing the state of the cluster and handling failover. Patroni uses etcd as the distributed configuration store and relies on HAProxy for load balancing.

Therefore, the software component that manages the state of the cluster and handles failover is Patroni.

Nutanix Database Automation (NCP-DB) Course Details, Section 2.4: Provisioning PostgreSQL Databases

Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.4: Provision PostgreSQL Databases

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.4: Provisioning PostgreSQL Databases

[Nutanix Database Automation (NCP-DB) User Guide], Section 2.4: Provision PostgreSQL Databases

[PostgreSQL High Availability: Under the Hood – Nutanix.dev]