An NDB Software Profile is a template of the OS and database engine that you can use to provision or clone database server VMs using NDB. To create a software profile, you need to upload an installer package for the database software that you want to use, such as SQL Server or Oracle. The installer package must be compatible with the OS image that you have registered with Prism Element. You do not need a database server VM registered with NDB, a patch file for the installed databases, or an OS image registered with Prism Element to create a software profile. Those are required for other tasks, such as creating a software profile version, registering a database server VM, or provisioning a database server VM.
Nutanix Benefit 8: Integrated Self-service Database Management, Nutanix Support & Insights, section "NDB Software"

Before registering a SQL Server Single Node Database Server VM with NDB, it is necessary that the login account provided for this task must be a member of the sysadmin role. This ensures the necessary permissions are in place for managing and administering the SQL Server instance.
References: Nutanix Database Automation documentation, under SQL Server database registration and permission requirements.

To create a software profile version for a newly-released Oracle ISc patch, an administrator should follow these steps:
* Download the required patch from MyOracle Support1. This is because Oracle patches are typically available from MyOracle Support, not Microsoft Support.
* Apply the patch to the Oracle Home/Grid Home on a cloned VM of the gold image using OPatchAuto1.
OPatchAuto is a utility provided by Oracle that automates the process of applying patches to a database.
* Ensure success of patch application1. It's important to verify that the patch has been applied successfully to avoid any issues down the line.
* Create a new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era GUI1. This step is necessary to ensure that the new patch is included in the software profile.
* Mark the original patch profile as hidden1. This step is optional but can be useful for keeping the software profile clean and organized.
Please note that these answers are based on the information available as of my last update in 2021 and may need to be verified with the most recent Nutanix Database Automation (NCP-DB) documentation or resources.

The exhibit shows the configuration of unencrypted Active Directory (AD) access in NDB, with the "Primary URL" set to ldap:// (indicating LDAP rather than LDAPS). Unencrypted LDAP communication uses port 389 by default. For NDB to communicate with Active Directory, this port must be allowed through the firewall to enable the NDB server to perform authentication and directory lookups using the specified service account (e.
g., administrator).
Other options are incorrect in this context:
* B. 636: This is the default port for LDAPS (LDAP over SSL/TLS), which is encrypted and not applicable since the configuration uses unencrypted LDAP.
* C. 2009: This is not a standard port for LDAP or AD communication and is unrelated to NDB's AD integration.
* D. 9440: This is associated with Prism Element's HTTPS management interface, not AD access.
Thus, the verified answer is A. 389, ensuring unencrypted LDAP communication between NDB and Active Directory.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.5: Configuring Active Directory Integration.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
2: Deploy and Configure an NDB Solution, Objective 2.4: Configure AD Access (applicable to v6.10).
* Nutanix NDB Administration Guide: "Active Directory Integration" section, detailing LDAP port requirements.

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 shouldbe 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