The correct answer is A and D because these are the two Time Machine options that are available when creating a database clone in NDB. Point in time allows the user to specify a date and time to create a clone from a specific point in the database history. Snapshot allows the user to select a previously taken snapshot to create a clone from a consistent state of the database. Option B is incorrect because Restore point is not a Time Machine option, but a feature that allows the user to restore a source database to a previous point in time. Option C is incorrect because Backup is not a Time Machine option, but a feature that allows the user to backup a database to a remote location.
The following sources provide more information about the Time Machine options and cloning features in NDB:
Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases Using Time Machine, Lesson 4.2: Cloning Databases Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 5 - Protect NDB-managed Databases Using Time Machine Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section
6.2: Cloning Databases
[Nutanix Support & Insights], NDB Time Machine Under the Hood

The database parameters profile is used to define the initialization variables for different types of database engines and workloads, such as OLTP and DW. The database parameters profile allows the database administrator to customize the configuration settings for each database engine, such as Oracle, SQL Server, PostgreSQL, and MySQL. The database parameters profile can also be applied to different database operations, such as provisioning, cloning, and patching. The database parameters profile helps to optimize the performance and functionality of the databases according to the specific requirements and best practices of each database engine and workload.
The software profile version is used to define the software version and edition for each database engine, such as Oracle 19c Enterprise Edition or SQL Server 2019 Standard Edition. The software profile version is required for provisioning new databases and patching existing databases. The software profile version helps to ensure the compatibility and compliance of the databases with the supported software versions and editions.
The network profile is used to define the network configuration and security settings for the database server VMs and the databases, such as the IP address, subnet mask, gateway, DNS, firewall rules, and SSL certificates. The network profile is required for registering new database server VMs and provisioning new databases. The network profile helps to ensure the connectivity and protection of the database server VMs and the databases within the network environment.
The compute profile is used to define the compute resources and storage policies for the database server VMs and the databases, such as the CPU, memory, disk size, disk type, compression, deduplication, and replication factor. The compute profile is required for provisioning new databases and cloning existing databases. The compute profile helps to ensure the availability and efficiency of the database server VMs and the databases within the Nutanix cluster.
Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slides 6-9.
Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson
5.1: Nutanix Era Operations, slides 5-8, 11-12, 15-16.

Page files are temporary files that Windows uses to store data that does not fit in the physical memory. Page files can interfere with the registration of a database server VM with NDB, as they can cause errors or performance issues. Therefore, page files should be located in a separate drive or partition from the C:\ drive, where the NDB agent and other files are installed. System, database, and backup files do not prevent the registration of a database server VM with NDB, as long as they are not corrupted or incompatible with the NDB requirements. References:
Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2: Configuring an NDB Instance, Slide 13: Registering Database Server VMs Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.1: Apply procedural concepts to register database server VMs and databases

When registering a Nutanix cluster with the Nutanix Database Service (NDB), the Prism Element user account used for registration must have sufficient privileges to perform cluster-level operations. The recommended role for this task is Cluster Admin. The Cluster Admin role in Prism Element provides the necessary permissions to manage cluster resources, including storage, networking, and integration with external services like NDB. This role is required because registering a cluster with NDB involves tasks such as establishing connectivity, validating configurations (e.g., Data Services IP), and ensuring that NDB can interact with the cluster's Controller VMs and storage infrastructure.
The default administrative account in Prism Element (typically "admin") often serves as the initial Cluster Admin user. However, if an administrator needs to remove or replace this default account for NDB operations, a new user with the Cluster Admin role must be created and used instead. Other roles listed have different purposes:
Super Admin: This is not a standard role in Prism Element; it may refer to elevated privileges in other contexts but is not specifically defined for Nutanix cluster registration.
User Admin: This role is limited to managing users and permissions, lacking the broader cluster management capabilities needed for NDB registration.
Backup Admin: This role is specific to backup-related tasks and does not encompass the full scope of cluster management required for NDB integration.
Therefore, the Cluster Admin role is the recommended and verified choice for registering a Nutanix cluster with NDB, ensuring seamless operation and management.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster with NDB.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2:
Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix cluster in NDB (applicable to v7.5 with no significant role changes documented).
Nutanix Prism Element Guide: "Role-Based Access Control (RBAC)" section, detailing Cluster Admin privileges.

NDB Multi-Cluster is a feature that allows multiple Nutanix clusters to share a common NDB service for database management and automation. NDB service consists of two components: NDB Server and NDB Agent. NDB Server is the central component that provides the web UI, REST API, and database orchestration logic. NDB Agent is the component that runs on each Nutanix cluster and communicates with the NDB Server to perform database operations.
When NDB Multi-Cluster is enabled on Cluster A, it becomes the primary cluster that hosts the NDB Server VM. Cluster B, which is registered with NDB, becomes a secondary cluster that hosts only the NDB Agent VM. Therefore, Cluster A has both NDB Server and NDB Agent, while Cluster B has only NDB Agent. This configuration allows Cluster B to leverage the NDB service running on Cluster A for database management and automation.
Nutanix Database Automation (NCP-DB) Course Details, Section 3.1: NDB Multi-Cluster Overview Nutanix Database Automation (NCP-DB) Certification Details, Objective 3.1: Configure NDB Multi-Cluster Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 3.1: NDB Multi-Cluster Overview