To apply the latest OS security patches on a Windows server managed by NDB, the user should create and apply a Maintenance Plan within the NDB interface. NDB provides a Maintenance Plan feature that allows administrators to schedule and automate OS patching for database server VMs, ensuring patches are applied in a controlled manner without disrupting database operations. This includes validating the patch process, rolling back if needed, and maintaining compliance with security standards. The plan can be configured to target the specific Windows server and include the latest security updates from Microsoft.
Other options are incorrect or insufficient:
* A. Reboot the system: A reboot alone does not apply patches; it may only activate previously installed updates.
* C. Update the database: This focuses on database software, not OS security patches.
* D. Use update functionality directly on the VM: Manual updates bypass NDB's control, risking inconsistency and potential downtime without proper validation.
Thus, the verified answer is B, leveraging NDB's centralized maintenance capabilities.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.3: Creating Maintenance Plans.
* 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: "Maintenance Plans for OS Patching" section.

When an administrator enables NDB Multi-cluster functionality, certain components are deployed or reconfigured to support the distributed environment. HAProxy (High Availability Proxy) is a critical component that manages load balancing and secure communication across clusters. In a multi-cluster setup, HAProxy is deployed on a dedicated VM to ensure efficient traffic distribution and high availability for NDB services, such as API calls and GUI access, across the clusters. This dedicated deployment enhances scalability and resilience.
Option A (Agent VM) is incorrect because Agent VMs are typically deployed on managed database VMs, not as dedicated NDB service components in multi-cluster setups.
Option B (HAProxy) is correct as it is specifically deployed on a dedicated VM to handle load balancing in a multi-cluster NDB environment.
Option C (Repository DB) is incorrect because the Repository DB is part of the NDB control plane and not necessarily deployed on a separate VM for multi-cluster purposes.
Option D (APIVM) is incorrect because the API VM is part of the core NDB infrastructure but not specifically deployed as a dedicated VM for multi-cluster enablement.
References
Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Multi- Cluster Configuration Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 3: Configure an NDB Environment

When an administrator schedules the removal of an existing database clone to minimize user impact (e.g., during weekend hours), the "Update Removal Schedule" feature in NDB allows for planning the operation.
Among the options, the "Delete supporting snapshot from NDB" is pre-selected as a non-optional action. This ensures that the snapshot data associated with the clone is removed along with the clone itself, maintaining storage efficiency and consistency in the Time Machine framework. Other options may be selectable but are not mandatory by default.
* Option A (Create an alert before removal) is incorrect because alerts are optional notifications, not a required action.
* Option B (Delete supporting snapshot from NDB) is correct as it is a default, non-optional step to clean up snapshot data.
* Option C (Unregister the database clone from NDB) is incorrect because unregistration is an optional administrative step, not pre-selected.
* Option D (Delete the database clone from the VM) is incorrect because the clone deletion itself is the primary action, but snapshot deletion is the non-optional supporting task.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Clone Removal
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

NDB uses Oracle out-of-place patching for Oracle database software. Instead of modifying the actively used Oracle home directly, NDB prepares or uses a separate Oracle home containing the required patched software and then moves the database to that home through an orchestrated workflow. This method keeps the original Oracle home available and reduces the risks associated with changing production binaries in place. It also supports more predictable patching and recovery procedures because the old and new software homes remain logically separated. Binary synchronization and in-memory synchronization are not Oracle patching methods used by NDB. In-place patching would directly modify the existing Oracle home and therefore does not describe the documented NDB workflow. Nutanix explicitly states that NDB uses out-of-place patching in its official Oracle database patching documentation.

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