When an administrator no longer wants to use a software profile version, what happens when it is deprecated?

In Nutanix Database Service (NDB), when an administrator deprecates a software profile version, it is

marked as obsolete and restricted from certain operations. Specifically, a deprecated software profile

version can no longer be used for provisioning new database instances or VMs. This ensures that only

current, supported versions are utilized for new deployments, maintaining consistency and security.

Existing database servers using the deprecated profile can continue to operate and may still be

patched (if updates are compatible), but the profile itself is excluded from future provisioning tasks.

Option A is correct because deprecation explicitly prevents the profile version from being selected

for new provisioning, aligning with NDB’s lifecycle management.

Option B (It can be used in provisioning) is incorrect as this contradicts the purpose of deprecation.

Option C (Any database server using that profile will be updated to the latest software profile) is

incorrect because deprecation does not automatically update existing servers; it only affects new

provisioning.

Option D (Any database server using that software profile can no longer be patched) is incorrect

because patching existing servers is still possible if compatible updates exist, independent of the

profile’s deprecated status.

Deprecation is a deliberate administrative action to phase out outdated profiles while preserving

existing deployments.

Reference:

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section:

Deprecating Software Profile Versions

Nutanix Support & Insights, Knowledge Base Article: "Software Profile Management in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage

Database Software Profiles