When a database administrator creates a clone removal schedule in NDB, the system automates the cleanup of cloned databases based on the defined schedule (e.g., after a set retention period). The two default actions taken on the cloned database are:
A. NDB deletes the cloned database: The clone’s data is removed from storage to free up space.
B. NDB de-registers the cloned database: The clone is removed from NDB’s management inventory, ensuring it no longer appears in the GUI or is tracked.
Other options are not default actions:
C. NDB marks the cloned database as offline: This is a temporary state, not a removal action.
D. NDB deletes the cloned database VM: Deleting the VM is not automatic; it depends on the clone type (e.g., linked clones retain the VM).
Thus, the verified answers are A and B, aligning with NDB’s clone management.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Clones and Removal Schedules.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Clone Removal (applicable to v7.5).
Nutanix NDB Administration Guide: "Clone Removal Schedule Actions" section.
