For supported Linux-based database VMs managed by NDB, keeping software profiles updated for provisioning new database VMs requires a structured process. The administrator must first apply the necessary patches (e.g., OS updates and database engine patches) to an existing database VM for each supported database engine (e.g., PostgreSQL, Oracle). Then, a new software profile version must be created using the updated VM as the source. This new version captures the patched configuration and can be used to provision new VMs, ensuring they are deployed with the latest updates.
Option A (Create a Maintenance window under the policy menu, then under Database VM, add the database VMs to that maintenance window and check both Database and Operating system updates) is incorrect because a Maintenance Window schedules updates for existing VMs, not for updating software profiles for new provisions.
Option B (Apply patches to a database VM for each supported database engine, then create a new software profile version for each supported database VM for each one using the updated database VM as the source) is correct as it follows the standard NDB process for profile updates.
Option C (Associate the newly provisioned database VMs with a maintenance window so they are kept updated) is incorrect because this applies to ongoing maintenance, not initial profile updates for provisioning.
Option D (In the Administrator menu drop down, go the Maintenance tab and choose Download Upgrade) is incorrect because downloading upgrades is part of the patch process, not the profile creation step.
This method ensures new VMs are provisioned with the latest software configurations.
References
Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Updating Software Profiles
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Software Profiles
