A Log Catchup gap in Nutanix Database Service (NDB) occurs when transaction logs are missing or corrupted, disrupting point-in-time restore (PITR) operations for cloning or database restoration via Time Machine. The NDB Time Machine Heal Snapshot feature addresses this by repairing snapshots to resolve such gaps.
* Option A (By default the time machine auto-heal feature is enabled) is incorrect because the auto- heal feature is not enabled by default; it requires explicit configuration or manual invocation.
* Option B (Manual Heal is only used when gaps in Log Catchup are detected once the operation has begun failing) is incorrect because manual heal can be initiated proactively or reactively, not solely after failure detection.
* Option C is correct because a successful Time Machine Heal process restores the snapshot integrity, allowing PITR to span the previously gapped period.
* Option D is correct as the auto-heal process, when enabled, runs every 5 minutes to detect and address healable conditions, aligning with NDB's automated maintenance schedule.
Together, C and D reflect the operational mechanics of the Heal Snapshot feature.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Healing Snapshot Gaps
* Nutanix Support & Insights, Knowledge Base Article: "Resolving Log Catchup Gaps with Time Machine Heal"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

When an administrator needs to scale the size of an Oracle database running on Nutanix NDB and originally configured using ASMLib (Automatic Storage Management Library), the most efficient approach is to use NDB's built-in scaling ability to resize existing vDisks. NDB supports dynamic resizing of virtual disks (vDisks) associated with database VMs, allowing the administrator to increase storage capacity without disrupting the database or requiring complex migrations. This method leverages Nutanix's storage integration, resizing the underlying vDisks and updating the ASMLib configuration to reflect the new size, ensuring seamless operation.
Option A (Leverage the scaling ability built into NDB to resize existing vDisks) is correct as it is the most efficient, native NDB feature for scaling storage.
Option B (Extend the size by adding new vDisks) is incorrect because adding new vDisks requires additional configuration (e.g., ASM disk group adjustments), making it less efficient than resizing.
Option C (Create a new, larger database and migrate) is incorrect because migration is time-consuming and unnecessary when resizing is supported.
Option D (Mount an iSCSI LUN and extend the database onto the new LUN) is incorrect because iSCSI LUNs are not the preferred method in NDB, and resizing vDisks is more integrated.
This approach minimizes downtime and complexity.
References
Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Scaling Storage for Databases Nutanix Support & Insights, Knowledge Base Article: "Resizing vDisks for Oracle Databases in NDB" Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Servers

To replicate database snapshots to remote Nutanix clusters, the administrator needs to add Data Access to each Nutanix cluster and assign a Data Availability Management (DAM) policy. Data Access is a feature of NDB that enables cross-cluster data mobility and protection. A DAM policy defines the replication frequency, retention period, and priority of the database snapshots across the clusters. By adding Data Access to each Nutanix cluster and assigning a DAM policy, the administrator can manage the Time Machine data availability across all registered Nutanix clusters in NDB.
Nutanix Support & Insights, section "NDB Data Access"

After a DBA's script corrupts an Oracle DB managed by NDB, the administrator needs to restore a clean copy using the latest available snapshot. The most straightforward action is to use the NDB Time Machine feature to select the most recent uncorrupted snapshot and create a new clone. This clone can serve as a restored version of the database, bypassing the corrupted data while leveraging existing snapshots for efficiency.
Option A (Fail the Oracle cluster over to a surviving RAC node) is incorrect because RAC failover is for HA, not corruption recovery via snapshots.
Option B is correct as it uses Time Machine to create a clone from a valid snapshot, addressing the corruption.
Option C (Use Time Machine to create a clone from file-level database backup) is incorrect because NDB primarily uses snapshots, not file-level backups, for cloning.
Option D (Provision a new Oracle DB and perform log catch-up) is incorrect because provisioning a new DB is more complex and unnecessary when a snapshot-based clone suffices.
This method ensures rapid recovery with minimal disruption.
References
Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring and Cloning from Snapshots Nutanix Support & Insights, Knowledge Base Article: "Recovering from Database Corruption in NDB" Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 5: Protect Databases Using Time Machine

The exhibit shows the "Create Snapshot" interface in NDB, where the administrator can select Nutanix clusters where the snapshot should be made available. However, only a single cluster appears despite multiple clusters in the environment. The most likely reason is that NDB Multi-cluster has not been enabled. Multi- cluster support in NDB requires explicit configuration to enable snapshot replication and data availability across remote clusters (e.g., via Prism Central and network profiles). Without this, NDB restricts snapshot operations to the local cluster where the database resides.
Other options are less likely:
A). The remote clusters are running ESXi: NDB supports ESXi clusters, so this alone wouldn't limit visibility unless multi-cluster is disabled.
B). The snapshot will be too big to replicate to a remote cluster: Size is a consideration during replication, but it doesn't prevent cluster visibility in the UI.
D). The remote clusters have an older version of AOS installed: Version compatibility might affect replication, but it wouldn't hide clusters from the list unless multi-cluster setup is incomplete.
Thus, the verified answer is C, pointing to the need for multi-cluster configuration.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.2: Configuring Multi-Cluster HA.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 4:
Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v7.5).
Nutanix NDB Administration Guide: "Enabling Multi-Cluster Snapshot Replication" section.