When running the Linux prerequisites script for NDB, the -t argument is a required parameter that specifies the timeout interval . This argument defines the maximum time (in seconds) the script will wait for certain operations (e.g., connectivity checks, package installations) to complete before timing out. This is critical during the preinstallation phase to ensure the environment is properly configured and responsive, avoiding indefinite hangs. Other options are not associated with -t:

A. Operating System type : This is not a typical argument for the prerequisites script.

C. NDB server IP : This would be specified separately (e.g., via -s or a similar flag).

D. Database engine : This is irrelevant to the prerequisites script, which focuses on system setup.

Thus, the verified answer is B , aligning with the script’s purpose of managing execution timeouts.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.1: Running Prerequisites Scripts.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v6.10).

Nutanix NDB Installation Guide: " Running the Linux Prerequisites Script " section, detailing -t usage.

In the context of Nutanix Database Automation (NCP-DB), when there are insufficient resources on a development cluster, the administrator can adjust the  Compute  and  Database Parameters  profiles to make the copy fit within the available resources 1 . The Compute profile includes settings related to CPU and memory resources, which can be adjusted to fit within the available resources.  The Database Parameters profile includes settings that control the behavior and resource usage of the database, which can also be adjusted to optimize resource usage 1 .

When registering a Nutanix cluster with NDB, a manual storage mapping between the remote container and the NDB provisioning container is required if the NDB Server container and NDB Provisioning container are separate . This separation occurs when the storage containers used by the NDB server (for its own operations) and the provisioning container (for database VMs) are distinct, either due to multi-cluster setups or custom configurations. Manual mapping ensures NDB can correctly allocate storage resources and manage database provisioning across these containers.

Other conditions do not necessitate manual mapping:

B. Disaster Recovery Network Segmentation is enabled on the cluster : This affects networking, not storage mapping.

C. Nutanix Database Service High Availability is enabled on the cluster : HA configurations handle replication, not container mapping.

D. DB VMs are stored in the NDB Server or NDB Provisioning container : This is a typical setup and does not require manual mapping unless containers differ.

Thus, the verified answer is A , addressing storage container separation.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix Cluster (applicable to v6.10).

Nutanix NDB Administration Guide: " Storage Container Mapping " section.

To add Time Machine data access to a Nutanix cluster, the first step is to register the cluster in NDB. This will allow NDB to discover and manage the databases and snapshots on the cluster. You can register multiple Nutanix clusters in NDB using the Add Cluster option in the NDB settings page. You can also specify the cluster role, such as source, target, or both, depending on the data access and replication needs. Enabling or disabling multi-cluster in NDB is not the first step, as this is a global setting that affects the entire NDB instance. Deleting the TM data from the source database is not the first step, as this will remove the data protection and availability of the database.  References :

Nutanix Database Management & Automation Training Course , Module 6: Managing NDB Multi-Cluster, Lesson 1: NDB Multi-Cluster Overview, Slide 5: Registering Nutanix Clusters

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam , Section 6: Administer an NDB Environment, Objective 6.4: Apply procedural concepts to add Nutanix clusters to NDB

The provided exhibit shows the NDB Time Machine restore interface for October 31, 2024, with a Point-in-Time (PIT) restore option selected at 21:50. However, the restore option is unavailable, as indicated by the question. The exhibit includes a warning: " Logs to Backup: The database may contain additional logs. Backup any remaining logs before restore or they will be lost. " This suggests that PIT restore requires continuous log retention, and if logs since the last snapshot (at 01:10:00) are not backed up, the restore to 21:50 cannot proceed. Running the " Logs to Backup " operation ensures all transaction logs are captured, enabling PIT restore by allowing NDB to replay logs to the desired point.

Option A (Point in time must be within the most recent range) is incorrect because the selected 21:50 is within the log retention period shown (up to the current time), but logs need to be backed up.

Option B (Selected Restore time is not available) is incorrect because 21:50 is a valid time within the log range, but log backup is the issue.

Option C (Change to snapshot option) is incorrect because switching to a snapshot limits the restore to the snapshot time (01:10:00), not 21:50.

Option D (Logs to Backup must be run first) is correct as the warning indicates that backing up remaining logs is necessary for PIT restore.

After running the backup, the administrator can proceed with the PIT restore.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Point-in-Time Restore Requirements

Nutanix Support & Insights, Knowledge Base Article: " Troubleshooting PIT Restore Issues in NDB "

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

To assign the minimum permissions required for provisioning new databases in an NDB deployment, the IT manager should assign the Database Administrator role. This role provides the necessary privileges to provision, configure, and manage database instances within NDB, including creating new databases using software profiles and registering database servers. It is designed for database-specific tasks without granting broader infrastructure or administrative control, making it the least privileged role suited for this purpose.

Other options exceed the minimum requirements:

A. Infrastructure Administrator : Manages cluster infrastructure (e.g., storage, networking), which is more than needed for database provisioning.

B. Super Administrator : Grants full control over NDB, including user management and system configuration, far beyond provisioning.

C. Database Infrastructure Administrator : Includes infrastructure management in addition to database tasks, exceeding the minimum scope.

Thus, the verified answer is D , aligning with the principle of least privilege.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.4: Managing Users and Roles.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.3: Manage User Permissions (applicable to v6.10).

Nutanix NDB Administration Guide: " Role-Based Access Control (RBAC) " section, detailing Database Administrator role.

A " dark site " refers to an environment with no internet connectivity, requiring manual processes for software updates. For Nutanix Database Service (NDB) in such a setup, updates cannot be downloaded automatically from the internet. The correct procedure is to:

Download the upgrade bundle : Access the Nutanix Support Portal from a system with internet access and download the NDB upgrade bundle specific to the version (e.g., v6.10 or later).

Manually upload it to the NDB server : Transfer the bundle to the NDB server (e.g., via SCP or USB) and upload it through the NDB interface under the " Software Updates " or " Maintenance " section.

Other options are incorrect in a dark site context:

B : The " Administrator > Maintenance " section allows initiating updates, but it cannot download files without internet access.

C : Changing the network to access https://download.nutanix.com defeats the dark site’s isolation and is impractical.

D : Uploading to Prism Element > Images is for VM images or other Prism-specific content, not NDB software updates.

Thus, the verified answer is A , aligning with Nutanix’s documented process for dark site updates.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Updating NDB in Dark Sites.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.3: Perform NDB Updates (applicable to v6.10).

Nutanix NDB Administration Guide: " Updating NDB in a Dark Site Environment " section.

In NDB, publishing a software profile update for Microsoft SQL Server makes it available for broader use within the NDB environment. When an administrator creates and publishes an updated software profile (e.g., with a new SQL Server patch or version), this action allows all authorized NDB users to leverage that profile to patch or update the database software on their managed VMs. This is a key feature of NDB’s software profile management, enabling centralized control and distribution of standardized database configurations.

Option A is correct because publishing a profile democratizes access, allowing all users to apply the update to their database VMs, aligning with NDB’s collaborative administration model.

Option B is incorrect because it suggests the profile patches itself, which is not the intent; publishing enables usage, not self-application.

Option C is incorrect because publishing does not automatically deprecate older profiles; deprecation is a separate administrative decision.

Option D is incorrect because publishing facilitates patching, not stalls it.

This process enhances efficiency and consistency in managing SQL Server updates across an organization.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Creating and Publishing Software Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles

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 command  upload upgrade_bundle  with the  path  parameter 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 the  upgrade  command to perform the upgrade.  References :  Nutanix Support & Insights ,  Cisco Nexus Data Broker Deployment Guide, Release 3.10.x