Nutanix Updated NCP-DB Exam Questions and Answers by amalia

When an administrator needs to restore databases provisioned with a shared disk configuration on Windows Storage Spaces in Nutanix Database Service (NDB), the restore operation focuses on the disks associated with the database. Windows Storage Spaces provides a virtualized storage layer, and NDB manages the restoration by reverting or recovering the specific disks that host the database files and logs. This ensures that the database is restored to its previous state using the snapshot or backup data, while preserving the shared disk configuration integrity. NDB does not replace the source volume or perform additional operations like tail log backups unless explicitly configured.

Option A (NDB restores the disk that are associated with the database) is correct as it accurately describes NDB’s restore behavior for shared disk setups.

Option B (NDB copies the DB files to be restored to the source volume) is incorrect because NDB restores the entire disk state, not just copying files to the source.

Option C (NDB replaces the source volume with the snapshot volume) is incorrect because NDB restores data to the existing volume, not replacing it entirely.

Option D (NDB performs Tail Log backup to backup any remaining logs) is incorrect because tail log backups are not automatically part of the restore process unless specified for point-in-time recovery.

This approach ensures compatibility with Windows Storage Spaces configurations.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring Databases with Shared Disks

Nutanix Support & Insights, Knowledge Base Article: "Restoring Windows Storage Spaces in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

Nutanix Era enables you to clone your source databases and refresh the database clones by using snapshots or transaction logs1. For an online retail application that requires data to be synchronized between multiple SQL Server databases, having all the databases present in the same Database Virtual Machine (DBVM) and registering them in Era with Multiple Databases as a Group with one Time Machine would be the most efficient way to fulfill this requirement1. This approach allows for clearer reporting from multiple databases at the same time for consistency at the end of each business day1.

When cloning an SQL database with Transparent Data Encryption (TDE) enabled in NDB, the target server must handle the encryption keys to ensure the cloned database remains functional and secure. TDE uses a keystore (e.g., a bundle file containing the master key and certificate) to encrypt data. Two steps are required: (1) The administrator must back up the keystore bundle file from the source database server VM and transfer it to the target server, ensuring the clone can decrypt the data. (2) After the clone is created, the administrator must run the post-clone command script, which configures the TDE keys on the target server, completes the encryption setup, and activates the cloned database.

Option A (Backup the .cer and .pvk files from the source database server VM) is incorrect because TDE in SQL Server typically uses a keystore bundle, not separate .cer and .pvk files.

Option B (Backup the keystore bundle file from the source database server VM) is correct as it ensures the encryption keys are available on the target.

Option C (Run the pre-clone command script) is incorrect because pre-clone scripts are for preparation, not TDE-specific post-clone setup.

Option D (Run the post-clone command script) is correct as it finalizes the TDE configuration on the target server.

These steps ensure a successful TDE-enabled clone.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Cloning TDE-Enabled Databases

Nutanix Support & Insights, Knowledge Base Article: "Cloning SQL Server with TDE in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

The log frequency in the Era IJI for log catchup operation can be configured to as low as 5 minutes. This allows the system to capture changes to the database at a high frequency, enabling more precise point-in-time recovery options. However, it’s important to note that a higher frequency of log catchup operations can lead to increased system load. Therefore, the optimal frequency may vary depending on the specific requirements and capabilities of your system12. Please refer to the Nutanix Database Automation (NCP-DB) Learning documents for more detailed information.