The exhibit shows an error during the provisioning of NDB from the Prism Central Marketplace, with a failure reason stating "IP not found" in the "EraService - Substrate Create" step. This indicates that the provisioning process could not assign or detect an IP address for the NDB instance, likely due to an unconfigured or missing IP address during deployment. To prevent this issue, the administrator should configure an IP address when deploying the application. This involves specifying a static IP or ensuring IP Address Management (IPAM) is properly set up to allocate an IP during the Prism Central Marketplace deployment wizard.
Other options are less directly relevant:
* B. Import the proper image in the Prism Central: This ensures the correct NDB image is available but does not address the IP assignment issue.
* C. Provide a subnet with IP Address Management: While useful, this is a broader configuration step and not the specific action needed during deployment.
* D. Register NDB using the correct IP address: Registration occurs after deployment and does not prevent the initial IP assignment failure.
Thus, the verified answer is A, as configuring the IP address during deployment directly addresses the "IP not found" error.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.2: Deploying NDB from Prism Central.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
2: Deploy and Configure an NDB Solution, Objective 2.2: Deploy NDB (applicable to v6.10).
* Nutanix NDB Installation Guide: "Deploying NDB via Prism Central Marketplace" section, emphasizing IP configuration.

To deploy Microsoft SQL Servers in an Active Directory (AD) environment and select a specific service account to start up the database, the administrator must configure a Windows domain profile in NDB. A Windows domain profile defines the AD integration settings, including the service account credentials (e.g., username and password) that NDB uses to authenticate and manage the SQL Server instances. This configuration ensures the database starts and runs under the specified AD service account, aligning with enterprise security policies.
Option A (Compute profile) is incorrect because a compute profile defines VM resources (CPU, memory), not AD or service account settings.
Option B (Sysprep Windows image) is incorrect because Sysprep is for generalizing Windows images, not configuring AD service accounts.
Option C (Windows domain profile) is correct as it is the specific NDB feature for AD integration and service account management.
Option D (Database parameters) is incorrect because database parameters tune database settings, not AD authentication.
This configuration ensures secure and compliant SQL Server deployment.
References
Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Configuring Windows Domain Profiles Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 2: Deploy and Configure an NDB Solution

The NDB alert retention feature allows the database administrator to configure the duration for which the NDB alerts are stored and displayed in the NDB instance. The NDB alert retention feature supports alert retention globally, meaning that the same retention period applies to all the alerts generated by the NDB instance, regardless of the source cluster, policy, or operation. The database administrator can set the alert retention period from 1 day to 365 days, or choose to retain the alerts indefinitely. The NDB alert retention feature helps to manage the storage space and the visibility of the NDB alerts.
The NDB alert retention feature does not support retention at the individual policy, grouped policy, or registered cluster level. The NDB alert retention feature applies to all the alerts uniformly, and does not allow the database administrator to specify different retention periods for different policies or clusters.
Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment, Lesson
3.2: Nutanix Era Deployment, slide 11.
Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson
5.1: Nutanix Era Operations, slide 6.

Time Machine data access is a feature of Nutanix Database Service (NDB) that allows you to access a point-in-time snapshot of a database without restoring it. To use this feature, you need to create a Data Access Management (DAM) policy that defines the access mode, the source database, the destination cluster, and the storage container mapping. The storage container mapping is needed when the source database and the NDB Server containers are different, because NDB needs to know where to store the metadata and the clone of the source database. If the source database and the NDB Server containers are the same, then NDB will use the same container for both the metadata and the clone. References:
* Nutanix Certified Professional - Database Automation (NCP-DB), Section 5 - Protect NDB-managed Databases Using Time Machine
* Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 9, Objective 5.6
* Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.2 - Data Access Management