A quality assurance team noticed a significant change between a cloned database they are currently using versus the one used one week ago. They…

When a quality assurance (QA) team notices a significant change between a cloned database

currently in use and one used a week ago, and they have an SQL script to verify differences, the NDB

administrator needs to provide a clone reflecting the database state from a week ago. The task

"Clone database selecting Point in Time data" allows the administrator to select a specific point-in-

time snapshot (e.g., from a week ago) using the Time Machine feature. This creates a new clone with

the exact data state at that time, enabling the QA team to compare it with the current clone.

Option A (Replicate a selected snapshot) is incorrect because replication is for HA, not creating a

usable clone for QA.

Option B (Create a clone database from a snapshot) is incorrect because it does not specify point-in-

time selection, limiting flexibility to the latest snapshot.

Option C (Clone database selecting Point in Time data) is correct as it allows precise selection of the

week-old data state.

Option D (Perform a Log Catch Up operation) is incorrect because Log Catch Up applies recent logs,

not reverting to a past state.

This approach meets the QA team’s need for historical data comparison.

Reference:

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

with Point-in-Time Data

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

Databases Using Time Machine