An NDB administrator is looking to free up some space consumption in the container that NDB uses to manage a database landscape. Where are two of the…

To free up space in the NDB-managed container, the administrator needs to identify storage

consumption sources. Two key locations in NDB provide actionable insights:

C . Clone Database table: This displays all clone databases, including their Size (current storage

usage) and Last Refresh (indicating age or staleness). Clones often consume significant space, and

older or unused ones can be deleted to reclaim storage.

D . Snapshot table in Time Machine: This shows snapshots with details like Reclaimable Space (space

recoverable by deletion) and Age (how long snapshots have existed). Old or unnecessary snapshots

are prime candidates for reclamation.

Why not the other options?

A . NDB Dashboard (Clone Data Age): While it provides a high-level view, it lacks granular details

(e.g., size per clone) needed for targeted reclamation.

B . Source Database grid: This shows registered databases’ size and status but doesn’t focus on

derivative objects (clones/snapshots) that typically consume more space.

Thus, C and D are the best locations for detailed storage analysis and reclamation research.

Official Nutanix Database Automation Reference:

Nutanix Database Management & Automation (NDMA) course, Module 6: Storage and Resource

Management, Lesson 6.2: Monitoring and Reclaiming Storage.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section

6: Optimize NDB Solutions, Objective 6.1: Manage Storage Consumption (applicable to v6.10).

Nutanix NDB Administration Guide: "Clone Database Table" and "Time Machine Snapshot Table"

sections.