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
