Nutanix NCP-DB Exam With Confidence Using Practice Dumps

This is because it allows the database to be refreshed at the exact time specified (9:30 PM) with the most recent data. The other options either perform the snapshot before the desired time or do not specify when the snapshot would occur. Please note that the exact answer might depend on the specific database system and its capabilities. Always refer to the database’s documentation for the most accurate information.

The size of a database Time Machine in Nutanix Era is defined by the size of all snapshots and/or transaction logs maintained by Era1. The Time Machine leverages Nutanix’s efficient snapshot technology to capture the state of the database at different points in time1. These snapshots, along with transaction logs that record changes between snapshots, constitute the data maintained by the Time Machine1. Therefore, the size of the Time Machine is determined by the total size of these snapshots and transaction logs1.

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) v7.5Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v7.5).

Nutanix NDB Administration Guide: "Patching Microsoft SQL Server" section.