Nutanix NCP-DB Exam With Confidence Using Practice Dumps

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

 Nutanix Era enables you to clone your source databases (running on Nutanix clusters) and refresh the database clones by using snapshots or transaction logs1. Era uses storage-efficient and time-efficient Nutanix snapshots, thus lowering the cost of managing multiple copies of your databases1. In this case, the administrator should create a clone from the July 31st snapshot in Time Machine to provide the legal team with the specific banking transaction event data they need for their audit1.

When upgrading NDB and the upgrade includes updates to out-of-the-box (OOB) software profiles (e.g., predefined profiles for database software like PostgreSQL, SQL Server, etc.), NDB manages older versions of these profiles based on their usage. If the older OOB software profiles are not actively in use by any database VMs, NDB automatically deletes all versions of those profiles from its metadata and associated protection domains during the upgrade process. This cleanup mechanism helps maintain a lean and efficient system by removing obsolete profiles that are no longer relevant or required.

Option A is incorrect because the condition about Time Machines and snapshots in the last 24 hours is not a documented criterion for profile deletion during an NDB upgrade.

Option B is correct as it reflects NDB’s behavior of removing unused OOB software profiles during upgrades to optimize resource usage and metadata.

Option C is incorrect because shutting down database VMs does not trigger automatic deletion of software profiles; the key factor is whether the profiles are in use.

Option D is incorrect because the concept of a "base version" is not relevant here; deletion depends solely on whether the profiles are unused, not on versioning specifics.

This behavior ensures that only active and necessary profiles persist post-upgrade, streamlining administration.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Upgrading NDB, Section: Handling Software Profile Updates

Nutanix Support & Insights, Technical Note: "NDB Upgrade Process and Software Profile Management"

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