Nutanix NCP-DB Practice Test - Questions Answers

According to the Nutanix Database Automation (NCP-DB) course, the Pre-Post Commands section allows the administrator to specify custom scripts that can be executed before or after the clone operation1.The masking script can be created on any of the VMs that have access to the source database, such as the source DB VM, the Dev VM, or the SW Profile VM2.The script should contain the commands to mask the sensitive data in the Finance database, such as replacing the real values with dummy values or encrypting the data2.The administrator can then create the clone from the Time Machine and define the post-clone option with the full path and name of the masking script1.This will ensure that the script is executed after the clone is created, and the data is masked before it is available for the development team1. The other options are not correct, as they either use the wrong field (pre-clone instead of post-clone), or do not specify where to create or store the masking script.Reference::

1: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 5

2: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 7

NDB supports two modes of log backup management for Microsoft SQL databases: NDB-managed and 3rd-party managed. In the NDB-managed mode, NDB takes full control of the log backups and stores them in the Cerebro log location. In the 3rd-party managed mode, NDB allows the use of external backup tools to backup the logs from the database log destination. However, NDB still needs to capture the logs for its own operations, such as point-in-time recovery, clone refresh, and log catch-up. Therefore, NDB will periodically scan the database log destination and copy the logs to the Cerebro log location. This process requires that the log catch-up begins before the logs get backed up by the 3rd-party tool, otherwise NDB will miss some logs and the operations will fail. If the 3rd-party tool grants exclusive access to the logs, then NDB will not be able to capture them at all, and the operations will not be supported.Reference::

Nutanix Database Management & Automation (NDMA) course, Module 5, Lesson 5.2 - Log Backup Management

Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Log Backup Management

For an NDB offline upgrade, you need to download the upgrade bundle from the Nutanix Support Portal and copy it to the NDB server. Then, you need to use the NDB CLI commandupload upgrade_bundlewith thepathparameter to specify the location of the upgrade bundle file. This command will upload the upgrade bundle to the NDB server and verify its integrity. After uploading the upgrade bundle, you can use theupgradecommand to perform the upgrade.Reference::Nutanix Support & Insights,Cisco Nexus Data Broker Deployment Guide, Release 3.10.x

The Database Agent is used to temporarily store the transaction logs of the source database before they are copied to the log. This is a critical component for ensuring data consistency and recovery in database operations.

Reference:: Nutanix Database Automation documentation, focusing on database agents and their roles in transaction log management.

When patching an Oracle Database Server VM, it's important to ensure that there is sufficient storage space allocated for the Grid home. A minimum of 10GB space is required for this purpose to accommodate the patching process without storage constraints.

Reference:: Nutanix Database Automation documentation, particularly in the sections discussing Oracle database server VM management and patching requirements.

Before registering a SQL Server Single Node Database Server VM with NDB, it is necessary that the login account provided for this task must be a member of the sysadmin role. This ensures the necessary permissions are in place for managing and administering the SQL Server instance.

Reference:: Nutanix Database Automation documentation, under SQL Server database registration and permission requirements.

For restoring a database provisioned on Storage Spaces, especially when virtual disks are shared among multiple databases, the supported method is a copy-based restore via the NDB GUI. This method allows for a precise and controlled restoration process suitable for shared storage environments.

Reference:: Nutanix Database Automation documentation, specifically in the section on database restoration methods and storage spaces.

To create an NDB Software Profile Version for PostgreSQL, it is required to have an installer package for the database software. This package forms the basis of the software profile, enabling the deployment and management of PostgreSQL instances.

Reference:: Nutanix Database Automation documentation, particularly in the area of software profile creation and management for PostgreSQL.

The minimum frequency configurable for the NDB Log Catch-up operation is 15 minutes. This setting determines how frequently the log catch-up process runs, which is crucial for maintaining data integrity and ensuring up-to-date database states.

Reference:: Nutanix Database Automation documentation, focusing on log management and catch-up operation settings.