A Development team requesting updated data for a cloned MongoDB instance used as source data for a script needs the latest snapshot or point-in-time data. In NDB, the "Clone Refresh" task updates an existing clone with the most recent data from the source database, ensuring the development team has access to current information without recreating the clone. This is the most efficient approach for maintaining an updated clone.
Option A (Clone the DB from the latest point in time data) is incorrect because it creates a new clone, duplicating effort instead of refreshing the existing one.
Option B (Execute a clone update) is incorrect as "clone update" is not a standard NDB task; refresh is the correct term.
Option C (Provision a MongoDB instance) is incorrect because it provisions a new instance, not an update to the clone.
Option D is correct as Clone Refresh syncs the clone with the latest source data.
References
Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Clones and Refresh
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 5: Protect Databases Using Time Machine
