A Time Machine is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention.When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de-registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 5 - Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies
* Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: Time Machine Concepts
* Nutanix Support & Insights, TN-2101: Nutanix Database Service Time Machine Under the Hood, Section: Time Machine States and Transitions

The optimal path to restore the table back with minimum data loss is to use the point in time restore feature of NDB, which allows the administrator to restore the database to a specific point in time based on the available snapshots and logs1. By restoring using point in time till 10:42pm, the administrator can recover the table just before it was dropped by the user, and minimize the data loss to the least possible amount1. The other options are not optimal, as they either involve restoring an older snapshot, which may result in more data loss, or restoring a non-existent snapshot, which is not possible. References:
* 1: Nutanix Database Automation (NCP-DB) course, Module 6: Database Recovery, Lesson 6.2: Point in Time Restore, slide 5

NDB High Availability distributes control-plane components across three Nutanix clusters so that a single cluster or site does not become the sole failure domain. For deployments spanning separate data centers or sites, the supported round-trip time between the selected clusters must be less than 25 milliseconds. A two- cluster topology is not supported because the cluster hosting two API servers and two repository servers would remain a single point of failure. Option C is also too restrictive: the three clusters may use AHV or ESXi; they are not required to be three AHV clusters. Consequently, option A is correct. The List B answer of D, which states less than 5 milliseconds, conflicts with Nutanix's documented HA requirement and has been corrected. Nutanix NDB HA architecture

To configure a database with a Time Machine protection mode that includes the Log Catchup operation in NDB, the most essential component is a Service Level Agreement (SLA) that supports continuous log retention. The Log Catchup operation enables point-in-time recovery (PITR) by replaying transaction logs from a specified point, ensuring minimal data loss and meeting Recovery Point Objective (RPO) requirements. This functionality depends on the Time Machine being configured with an SLA that includes the "Continuous Log Retention" option, which ensures transaction logs are captured and retained continuously alongside snapshots.
* Option A is incorrect because a daily snapshot alone is insufficient without log retention to enable Log Catchup.
* Option B is incorrect because an SLA retention schedule for daily snapshots does not inherently include continuous log capture, which is required for Log Catchup.
* Option C is correct as it specifies the Continuous Log Retention option, the critical feature for enabling Log Catchup in a Time Machine SLA.
* Option D is incorrect because while frequency settings are important, they are secondary to selecting an SLA with continuous log retention as the foundational requirement.
This configuration ensures robust data protection and recovery capabilities tailored to the database's needs.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Setting Up SLAs with Log Catchup
* Nutanix Support & Insights, Knowledge Base Article: "Configuring Time Machine with Log Catchup in NDB"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

The correct answer is B because it allows the administrator to create a custom role with the specific privileges that the Jr DBA user needs, and then assign that role to the user. This way, the administrator can control the access level of the Jr DBA user without affecting the existing roles or users in NDB. Option A is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then adding more privileges, which is unnecessary and redundant. Option C is incorrect because it involves creating a user for the Jr DBA, but not assigning a role to the user, which means the user will not have any privileges in NDB. Option D is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then removing some of the privileges, which is inefficient and risky.
References: The following sources provide more information about the user roles and privileges in NDB:
* Nutanix Database Management & Automation (NDMA) course, Module 8: Administering an NDB Environment, Lesson 8.6: Managing Access Controls in NDB
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section
6 - Administer an NDB Environment
* Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section
8.6: Managing Access Controls in NDB