Pass the Nutanix Nutanix Certified Professional (NCP) NCP-DB Questions and answers with CertsForce

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) v7.5Blueprint, Section 4: Manage Database Software Profiles

When an administrator encounters an error provisioning a new Oracle database VM in NDB, the best action to provide Nutanix support with the most complete picture is to select the failed job in the Operations menu and choose Generate Bundle from the lower right. The "Generate Bundle" option creates a comprehensive diagnostic package, including logs, configuration details, and error traces specific to the failed operation. This bundle is ideal for troubleshooting and can be uploaded to Nutanix Support for analysis.

Other options are less comprehensive:

A. From the Administration section of NDB, go to the Diagnostics section and choose Generate Bundle: This generates a general diagnostic bundle, not specific to the failed job.

B. Copy the error message from the Operations menu: This provides limited context compared to a full bundle.

D. Take a screenshot of the error in the Operations menu: A screenshot lacks detailed logs and system data needed for support.

Thus, the verified answer is C, ensuring detailed support data.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.4: Troubleshooting and Support.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.4: Generate Support Bundles (applicable to v7.5).

Nutanix NDB Administration Guide: "Generating Support Bundles for Failed Operations" section.

An NDB Software Profile is a template of the OS and database engine that you can use to provision or clone database server VMs using NDB. To create a software profile, you need to upload an installer package for the database software that you want to use, such as SQL Server or Oracle. The installer package must be compatible with the OS image that you have registered with Prism Element. You do not need a database server VM registered with NDB, a patch file for the installed databases, or an OS image registered with Prism Element to create a software profile. Those are required for other tasks, such as creating a software profile version, registering a database server VM, or provisioning a database server VM.

 Nutanix Benefit 8: Integrated Self-service Database Management, Nutanix Support & Insights, section “NDB Software”

To roll back an Oracle patch on a database server VM using NDB, the patch must have been applied using NDB in the first place. This is because NDB maintains a patch inventory and history for each database server VM and database that it manages. NDB uses this information to determine which patches can be rolled back and how to revert the changes made by the patch. If the patch was applied outside of NDB, NDB would not have the patch information and would not be able to roll back the patch. Therefore, the patch must have been applied using NDB for the rollback action to be successful. The other options are not required for the rollback action. The database does not need to be shut down or in read-only mode, as NDB can perform the rollback operation online. The patch does not need to be applied on Grid home only, as NDB can roll back patches applied on both Grid home and Database home. References:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 4 - Operate and Maintain an NDB Environment, Objective 4.4: Determine the correct method to apply Linux OS patches

Nutanix Database Management & Automation (NDMA) Course, Module 5: Nutanix Database Service (NDB) Patching, Lesson 5.1: Patching Overview, Topic: Patching Concepts

[Nutanix Database Service (NDB) User Guide], Chapter 7: Patching, Section: Rolling Back a Patch

NDB supports Linux OS patching for database server VMs. Linux OS patching is performed by using the yum or apt package managers, depending on the Linux distribution. To exclude Kernel patches for the Linux OS, the administrator can disable or exclude the appropriate repositories on the VM prior to patching. This can be done by editing the yum.conf or apt.conf files, or by using the --disablerepo or --exclude options in the yum or apt commands. This way, the administrator can control which patches are applied to the VM without affecting other VMs or requiring additional scripts or reboots.

Nutanix Database Automation (NCP-DB) Course Details, Section 4.2: NDB Linux OS Patching

Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.2: Perform Linux OS Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.2: NDB Linux OS Patching

Nutanix Database Automation (NCP-DB) User Guide, Section 4.5: Patch Linux OS Software

A Network Profile is a collection of network settings that are used to provision database server VMs in NDB. A Network Profile can include one or more VLANs, IP ranges, and DNS servers. To make new VLANs available when provisioning an Oracle cluster database, you need to update the Network Profile to include the new VLANs. You can do this by editing the existing Network Profile or creating a new one with the new VLANs. You do not need to create or update the VLANs in Prism Element, as NDB can discover the VLANs configured in AHV1. References:

Nutanix Database Management & Automation (NDMA) course, Module 2, Lesson 2.4 - Network Profiles

Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Network Profiles

Nutanix Certified Professional - Database Automation (NCP-DB), Section 2 - Deploy and Configure an NDB Solution

NDB High Availability uses multiple API Server VMs to provide the user interface and REST API services. The platform can automatically tolerate the failure of up to two service VMs, but if every API Server VM is offline, the API service becomes completely unavailable and manual intervention is required. Recovery requires bringing at least one API Server VM back online. Once an API Server is running, the NDB API service can restart and the remaining HA components can rejoin or recover through the normal resiliency mechanisms. Restarting HAProxy first cannot restore an API service when no API Server is available. Repository VMs should not be recreated because they contain NDB metadata, and registered Nutanix clusters do not need to be registered again. Therefore, the correct answer is A. NDB HA failure and recovery scenarios

================

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) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v7.5).

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

 According to the Nutanix Database Automation (NCP-DB) learning documents, when dealing with an Availability Group (AG) database, the database should be registered as an Availability database1. This is because the AG database is hosted on replicas with different named instances, and registering it as an Availability database allows for Copy Data Management operations to be performed across all instances. This is particularly important when services such as the Analytics service running on SQLAGN3\DW require real-time data1.

When using the "Patch OS now" feature in NDB to apply updates to a Red Hat-based operating system, the administrator can limit updates to security patches only by leveraging the Advanced Options. Under the "Custom commands" section of the operating system patching command window, entering yum update --security instructs the package manager to install only security-related updates. This ensures the system remains secure without applying all available updates, which could introduce instability.

Other options are incorrect or incomplete:

A. Point the database VM to a custom patch repository and enter yum update --security command: This requires manual intervention outside NDB’s patching framework.

B. Check Advanced Options and under Pre-post commands, enter yum update security in the pre-operating system patching command window: Pre-post commands are for pre/post actions, not the main patching process, and the syntax lacks the --security flag.

C. Point the database VM to a custom patch repository before using the Patch OS now feature: This sets up a repository but doesn’t specify security-only updates within NDB’s interface.

Thus, the verified answer is D, aligning with NDB’s patching customization.

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

Nutanix NDB Administration Guide: "Patch OS Now with Custom Commands" section.