NDB Agents handle log backups for database instances, but storing these backups locally can lead to bottlenecks (e.g., disk I/O, storage capacity). To alleviate this, integrating NDB with Nutanix Objects is the recommended solution. Nutanix Objects is an S3-compatible object storage service within the Nutanix ecosystem, ideal for offloading log backups from NDB Agents to a scalable, centralized storage platform.
This reduces local storage pressure, improves performance, and ensures strict SLAs for database recovery by leveraging efficient backup retrieval.
Other options are less effective:
* A: Integrating with AWS S3 or Azure Blob is possible but requires external connectivity and introduces latency, complexity, and cost compared to Nutanix Objects.
* B: Adding NDB Agent VMs increases management overhead and doesn't address the root storage bottleneck.
* D: Increasing RAM/CPU on NDB Agents may help processing but doesn't solve storage capacity or I
/O issues for log backups.
Thus, C is the verified answer, aligning with Nutanix's integrated ecosystem approach.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.3: Configuring Log Backup Storage.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
5: Protect Databases Using NDB, Objective 5.3: Configure Backup Storage Options (applicable to v6.
10).
* Nutanix NDB Administration Guide: "Integrating NDB with Nutanix Objects for Log Backups" section.

When an administrator is asked to add a database to a PostgreSQL instance already managed by NDB, the most appropriate task is to add a new database to the existing source database. In NDB, a PostgreSQL instance refers to a managed database server or cluster, and adding a new database involves creating it within the existing instance using NDB's database management capabilities. This can be done through the NDB GUI or CLI by selecting the source database and adding the new database, leveraging the current configuration and resources without requiring new VM provisioning.
Option A (Add a new database to a source DB) is correct as it directly addresses adding a database to an existing managed instance.
Option B (Register a new DB VM to add the DB) is incorrect because a new VM registration is unnecessary when the instance is already managed.
Option C (Provision a new DB server VM and add the new DB) is incorrect because provisioning a new VM is overkill for adding a database to an existing instance.
Option D (Update a database clone to add a new DB) is incorrect because clones are read-only copies, not suitable for adding new databases.
This approach ensures efficiency and leverages the existing NDB-managed infrastructure.
References
Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Managing Databases in an Instance Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Engines

An administrator can configure a custom SSL certificate for Era through the Era User Interface (UI)1. This can be done by logging into the Nutanix Console and selecting SSL Certificates from the drop-down list inside the gear icon23. In the SSL Certificate dialog box, the administrator can click Replace Certificate, then select the Import Key and Certificate radio button23. This process ensures secure communication within the Nutanix Era environment4.

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

When provisioning a PostgreSQL HA Instance using NDB, the minimum and maximum number of DB server VMs that can be deployed in a cluster are 2 and 4, respectively. A PostgreSQL HA Instance is a database instance that provides high availability and fault tolerance for PostgreSQL databases using the Patroni framework. Patroni is a Python-based tool that manages PostgreSQL configuration and performs automatic failover and switchover operations. Patroni relies on a distributed consensus store, such as etcd, Consul, or ZooKeeper, to store and synchronize the cluster state and leader information. NDB supports etcd as the consensus store for PostgreSQL HA Instances. NDB allows the administrator to provision PostgreSQL HA Instances with different sizes and configurations, such as small, medium, large, or custom. The size of the PostgreSQL HA Instance determines the number of DB server VMs, the number of etcd nodes, the CPU, memory, and disk resources, and the replication factor of the database. The minimum number of DB server VMs for a PostgreSQL HA Instance is 2, which corresponds to a small size instance. This configuration provides one leader and one follower DB server VM, and one etcd node. The maximum number of DB server VMs for a PostgreSQL HA Instance is 4, which corresponds to a large size instance. This configuration provides one leader and three follower DB server VMs, and three etcd nodes. The other options are not valid for a PostgreSQL HA Instance, as they either do not provide enough redundancy or exceed the supported limit of DB server VMs. References:
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.2: Configure an NDB Instance Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.2: Configuring NDB, Topic: Provisioning PostgreSQL HA Instances Nutanix Database Service (NDB) User Guide, Chapter 4: Provisioning Databases, Section: Provisioning PostgreSQL HA Instances
[PostgreSQL High Availability: Under the Hood - Nutanix.dev], Section: PostgreSQL HA Architecture and Components