Nutanix Certified Professional (NCP) NCP-DB Syllabus Exam Questions Answers

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

Nutanix Database Automation (NCP-DB) allows administrators to manage Service Level Agreements (SLAs) for databases. These SLAs define the data protection policies for databases. In this case, to minimize storage usage for a test database, the administrator should select the built-in NONE SLA. This SLA is configured for no snapshot or log backup, thus minimizing storage usage1.

 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.

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

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

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