The correct answer is C because it follows the recommended procedure for applying a CU to a SQL Server Software Profile in NDB. By applying the patch to the profile VM, the administrator ensures that the CU is compatible with the existing Software Profile settings and configuration. By creating a new Software Profile version, the administrator preserves the previous version of the Software Profile for rollback purposes and allows the new version to be tested and published. Option A is incorrect because it deletes the existing Software Profile, which may cause data loss and prevent rollback. Option B is incorrect because it does not apply the patch to the profile VM, which may result in errors or inconsistencies in the Software Profile.
Option D is incorrect because it creates a new Software Profile instead of a new version, which may cause confusion and duplication.
References: The following sources provide more information about the Software Profile management and patching in NDB:
* Nutanix Database Management & Automation (NDMA) course, Module 5: Patching Databases Using NDB, Lesson 5.2: Creating and Modifying Software Profiles
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section
4 - Operate and Maintain an NDB Environment
* Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.2:
Creating and Modifying Software Profiles
* Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.3:
Testing and Publishing Database Patches

The error message in the exhibit indicates that the operation failed during the "Create and Register Database Server VMs" step because "Provisioning of all the observers simultaneously took more than two hours." This type of error is associated with MySQL, as it involves observers which are a part of MySQL Group Replication, used for ensuring high availability1. The other options are not related to the error message, as they do not use observers or Group Replication for clustering. References:
* 1: Nutanix Database Automation (NCP-DB) course, Module 5: Database High Availability, Lesson 5.2:
MySQL Group Replication, slide 7

NDB SLAs are service level agreements that define the data protection and recovery objectives for NDB-managed databases. NDB SLAs consist of data retention policies that specify how long the snapshots and log backups of a database are kept in the Time Machine. Data retention policies can be customized to meet different business and compliance requirements, such as daily, weekly, monthly, or yearly retention periods.NDB SLAs also determine the frequency and schedule of the snapshots and log backups, as well as the storage location and replication options. An administrator who is tasked with auditing NDB SLAs will be reviewing the data retention policies of each database and Time Machine, as well as the snapshot and log backup history and status. The administrator will also be able to monitor the storage usage and performance of the NDB SLAs, and modify or delete the SLAs as needed. The other options are not part of the NDB SLAs, but rather separate features or concepts of NDB. Snapshot schedules are the intervals at which NDB takes snapshots of the databases, which are determined by the SLAs. Clone management is the process of creating, refreshing, or deleting database clones from the Time Machine. Recovery time objective (RTO) is the maximum acceptable time for restoring a database after a failure, which is influenced by the SLAs, but not defined by them. 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: SLA Concepts
* Nutanix Database Service (NDB) User Guide, Chapter 6: SLAs, Section: SLA Overview

When an administrator needs to scale the size of an Oracle database running on Nutanix NDB and originally configured using ASMLib (Automatic Storage Management Library), the most efficient approach is to use NDB's built-in scaling ability to resize existing vDisks. NDB supports dynamic resizing of virtual disks (vDisks) associated with database VMs, allowing the administrator to increase storage capacity without disrupting the database or requiring complex migrations. This method leverages Nutanix's storage integration, resizing the underlying vDisks and updating the ASMLib configuration to reflect the new size, ensuring seamless operation.
* Option A (Leverage the scaling ability built into NDB to resize existing vDisks) is correct as it is the most efficient, native NDB feature for scaling storage.
* Option B (Extend the size by adding new vDisks) is incorrect because adding new vDisks requires additional configuration (e.g., ASM disk group adjustments), making it less efficient than resizing.
* Option C (Create a new, larger database and migrate) is incorrect because migration is time- consuming and unnecessary when resizing is supported.
* Option D (Mount an iSCSI LUN and extend the database onto the new LUN) is incorrect because iSCSI LUNs are not the preferred method in NDB, and resizing vDisks is more integrated.
This approach minimizes downtime and complexity.
References
* Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Scaling Storage for Databases
* Nutanix Support & Insights, Knowledge Base Article: "Resizing vDisks for Oracle Databases in NDB"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Servers

NDB can leverage snapshots and transaction logs to refresh a database clone to the latest state of the source database. Snapshots are point-in-time copies of the database that are stored on the Nutanix cluster. Transaction logs are records of the changes made to the database after the snapshot was taken. NDB can use either snapshots or transaction logs, or a combination of both, to refresh a database clone. Cerebro logs and templates are not used for refreshing database clones. Cerebro logs are used for log catch-up operations, which are different from refresh operations. Templates are used for provisioning new databases, not for refreshing existing ones. References:
* Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.3 - Refreshing Clones
* Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Clone Database Management