A database is de-registered without removing the associated Time Machine.

When a database is de-registered from NDB without removing the associated Time Machine, the Time Machine enters a "Frozen" state. In this state, the Time Machine retains all existing snapshots and protection data but ceases to perform new snapshot captures or log catch-up operations. This allows the administrator to preserve the historical data for potential future use (e.g., auditing or recovery) while halting active management. The Frozen state prevents further modifications until the database is re-registered or the Time Machine is explicitly deleted.

Option A (Ready) is incorrect because "Ready" implies the Time Machine is active and prepared for new operations, which is not the case post-de-registration.

Option B (Frozen) is correct as it reflects the paused protection state after de-registration without removal.

Option C (Paused) is incorrect because "Paused" is not a formal Time Machine state in NDB; "Frozen" is the specific term.

Option D (Active) is incorrect because the Time Machine cannot remain active without an associated registered database.

This state provides flexibility for data retention without ongoing resource use.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Time Machine States

Nutanix Support & Insights, Knowledge Base Article: "Understanding Time Machine States After De-registration"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine