When an administrator creates a new SQL Server software profile version to apply the latest cumulative update, they should update the software profile version and set the status to Published1. This makes the new profile version available to all users. NDB will show available updates for any database server using the software profile as soon as the new profile version is published1.

In Nutanix Database Service (NDB), alert retention is a configurable setting that determines how long alerts (e.g., system issues, performance warnings, or database events) are stored in the system for review and analysis. Based on NDB's design and administrative policies, the maximum number of days allowed for alert retention is 180 days. This duration allows administrators to maintain a reasonable historical view of system health while preventing excessive data accumulation that could impact performance. This value is typically set as a default maximum in the NDB settings or via Prism Central integration, and administrators can adjust retention periods within this limit based on organizational needs.
Option A (90) is incorrect as it represents a shorter retention period, which may be a configurable minimum or intermediate value but not the maximum.
Option B (180) is correct as it matches the documented maximum alert retention period in NDB.
Option C (270) is incorrect as it exceeds the standard maximum retention period supported by NDB.
Option D (306) is incorrect as it is not a supported retention limit in NDB's configuration options.
Administrators should verify this setting in the NDB UI under alert management or consult Nutanix support for custom configurations.
References
Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section:
Configuring Alert Settings
Nutanix Support & Insights, Technical Note: "Alert Retention and Management in NDB" Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 6: Administer an NDB Environment

When configuring an SMTP server for sending alert notifications via email in NDB, the two security options available are SSL and TLS. These protocols encrypt the email communication between NDB and the SMTP server, ensuring the confidentiality and integrity of alert notifications. NDB supports both options to accommodate different SMTP server configurations, with TLS being the more modern standard and SSL as a legacy option.
Other options are not applicable:
* B. S/MIME: This is used for email content encryption, not SMTP server configuration.
* C. DKIM: This is a domain authentication method, not a security protocol for SMTP.
Thus, the verified answers are A and D, reflecting NDB's SMTP security features.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.1: Configuring Alert Notifications.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
6: Optimize NDB Solutions, Objective 6.2: Manage Alerts (applicable to v6.10).
* Nutanix NDB Administration Guide: "Configuring SMTP for Alerts" section, listing SSL and TLS options.

To apply patches to Microsoft SQL Server databases in an NDB environment, the administrator should follow a structured process:
* Create a new software profile version: Download the latest cumulative update (CU) or patch from Microsoft and use it to create a new version of the existing SQL Server Software Profile in NDB. This ensures the patch is integrated into NDB's management framework.
* Publish the updated software profile: Promote the new version to "Published" status, making it available for use across the environment.
* Apply the update: Navigate to the "Database VM Menu" for each database server, select the updated software profile, and apply the patch. This automates the patching process while maintaining database consistency and allowing rollback if needed.
Other options are incorrect or incomplete:
* A. Create a Maintenance window schedule and associate the SQL server with that maintenance window in the Database VM Menu: Maintenance windows manage downtime, not patch application for databases.
* B. Apply the patch to the database VM then create a new software profile using that updated VM as the source: This manual approach bypasses NDB's structured patching and lacks version control.
* C. Apply the patch to the database VM, then create a new software profile version using that updated database VM as the source, publish the updated software profile then apply that patch under the database VM Menu for each database server: This is overly complex and risky, as manually patching a VM first can lead to inconsistencies.
Thus, the verified answer is D, aligning with NDB's best practices for database patching.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.2: Patching SQL Server Databases.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v6.10).
* Nutanix NDB Administration Guide: "Patching Microsoft SQL Server" section.

In the context of Nutanix Database Automation (NCP-DB), when provisioning a new Oracle SIHA DB & VM, if only ASMFD is available in the ASM Driver drop-down, it indicates that ASMLIB is not included in the current software profile. To provision the requested SIHA DB and DB VM with ASMLIB, it's essential to update the software profile to include the ASMLIB driver. This action will enable ASMLIB as an option in the ASM Driver drop-down during the provisioning workflow.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 2.3: Provisioning Oracle Databases
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.3: Provision Oracle Databases
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.3: Provisioning Oracle Databases
* [Nutanix Database Automation (NCP-DB) User Guide], Section 2.3: Provision Oracle Databases