Nutanix NCP-DB Based on Real Exam Environment

Patroni continuously monitors PostgreSQL HA members and can promote a standby when it determines that the leader has failed. During an in-place point-in-time restore, NDB intentionally stops normal cluster automation: it pauses Patroni monitoring and places the cluster in maintenance mode while the database state is rewound. This prevents Patroni from interpreting controlled shutdowns or role changes as failures and initiating an unwanted promotion. After recovery and cluster validation, normal Patroni management can resume. Nutanix documents Patroni as the component responsible for monitoring PostgreSQL instances and performing automated failover, which explains why its automation must be suspended during this coordinated recovery operation. NDB neither promotes every node nor deletes and rebuilds the Patroni configuration. Therefore, option C is correct. Nutanix Patroni overview

This is because it allows the database to be refreshed at the exact time specified (9:30 PM) with the most recent data. The other options either perform the snapshot before the desired time or do not specify when the snapshot would occur. Please note that the exact answer might depend on the specific database system and its capabilities. Always refer to the database’s documentation for the most accurate information.

To add a new Nutanix AHV cluster to the current single default container for database provisioning and enable NDB multi-cluster functionality, the administrator must ensure a unified management framework. Nutanix Prism Central serves as the centralized management platform for multi-cluster environments, allowing NDB to manage multiple clusters (in this case, the existing cluster and the new AHV cluster) under a single instance. Before enabling multi-cluster support in NDB, both clusters must be registered with the same Prism Central instance, and NDB must be confirmed as registered to that instance. This ensures consistent policy enforcement, resource visibility, and database provisioning across clusters using the default container.

Option A (Deploy Nutanix Self Service VM and use blueprints) is incorrect because Nutanix Self Service is an optional tool for end-user provisioning and not a prerequisite for multi-cluster enablement.

Option B (Configure datastore mapping within Prism Element Protection Domains) is incorrect because datastore mapping is a lower-level configuration and not directly required for multi-cluster setup in NDB.

Option C (Enable High Availability for NDB service on the Administration page) is incorrect because HA is a separate configuration for NDB resilience, not a prerequisite for multi-cluster support.

Option D is correct as it aligns with NDB’s requirement for Prism Central integration to manage multiple clusters effectively.

This configuration ensures seamless multi-cluster operation.

References

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

Nutanix Prism Central Administration Guide, Section: Managing Multiple Clusters

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

NDB diagnostic collection gathers relevant logs from the NDB control plane and the database server VMs participating in the failed operation. For a Linux database server, the NDB agent collects applicable operating-system information, database-engine logs, work-driver output, and operation-specific diagnostic data. These files are packaged into a downloadable compressed bundle associated with the failed operation, allowing administrators or Nutanix Support to examine the complete execution context. NDB does not copy the active database data directory, create a runtime memory dump, or use a hypervisor snapshot of the log directory. Time Machine protects database data through snapshots and transaction logs; it is not the mechanism used to assemble support bundles. The official Nutanix instructions for viewing operation logs and downloading diagnostic bundles describe the collected and compressed diagnostic information.