Free Nutanix NCP-DB Practice Exam with Questions & Answers | Set: 5

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) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.4: Generate Support Bundles (applicable to v6.10).

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

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.

References:

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

When restoring a PostgreSQL HA instance in NDB, if the standby node fails to restore but the primary node is successfully restored and ready to serve application traffic, NDB considers the database operational from the perspective of the primary node. In this scenario, NDB leaves the database in an "ONLINE" state, reflecting that the primary node is functional and capable of handling requests, even though the HA configuration is not fully intact due to the standby failure. The administrator would need to address the standby node separately (e.g., by re-provisioning or troubleshooting), but the database’s state is determined by the primary node’s readiness.

Option A (PAKFIAL.READY) appears to be a typo and is not a valid NDB state.

Option B (OFFLINE) is incorrect because the primary node is operational, so the database is not offline.

Option C (ONLINE) is correct as it reflects the primary node’s ability to serve traffic.

Option D (RECOVERY PENDING) is incorrect because the primary node has completed recovery and is active, not pending.

This behavior aligns with NDB’s focus on maintaining service availability where possible.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring HA Instances

Nutanix Support & Insights, Knowledge Base Article: "Handling Partial Restore Failures in PostgreSQL HA"

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

 Nutanix Database Service (NDB) supports automated minor version upgrades for PostgreSQL1. Before applying the patch, the administrator should create a new software profile2. This is because the software profile contains the database engine binaries and other software required to run the database engine2. Therefore, to apply a minor version upgrade, a new software profile with the updated binaries needs to be created2. Once the new software profile is created, it can be used to patch the PostgreSQL database2.

According to the Nutanix Database Automation (NCP-DB) learning documents, to create a network profile in Era, the network must be added to Era1. This is because Era needs to have control over the network in order to manage the databases effectively1. Once the network is added to Era, it can be used for various operations such as provisioning new databases, managing existing databases, and more1.

NDB supports patching for PostgreSQL database instances. Patching for PostgreSQL is validated on VMs provisioned by NDB (greenfield deployments). To patch PostgreSQL database server VMs, you must create a software profile version by uploading the PostgreSQL update file in NDB. You can then use the PostgreSQL update to patch other database server VMs or provision a new database server VM with the updated software profile. The first step in the NDB patching workflow is to create a software profile version with the desired PostgreSQL version.

References:

Nutanix Database Automation (NCP-DB) Course Details, Section 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.1: Perform Database Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) User Guide, Section 4.4: Patch PostgreSQL Database Software

In Nutanix Database Automation (NCP-DB), the Time Machine feature is used for protecting databases and creating database clones. To create a database clone using the Era Interface, an administrator should select Time Machines, select a source database, and then choose Create Clone12. This process allows the administrator to create a copy of the source database at a specific point in time1.

After a new NDB deployment, the administrator can test the provisioning capabilities using a database instance that is fully supported and readily configurable out of the box. PostgreSQL is the most suitable option because it is one of the core database engines supported by NDB from the initial deployment, with built-in provisioning templates and HA capabilities. NDB provides a streamlined process to provision PostgreSQL instances, making it an ideal choice for testing provisioning workflows, including VM creation, storage allocation, and network configuration.

Other options may require additional setup or licensing:

B. Oracle DB: Requires specific licensing and additional configuration, not typically available for initial testing.

C. MSSQL Server: Supported but may need Microsoft licensing and setup, less immediate than PostgreSQL.

D. MongoDB: Supported but less commonly used for initial testing due to its NoSQL nature and additional configuration needs.

Thus, the verified answer is A, reflecting PostgreSQL’s accessibility for testing.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Provisioning Databases.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Provision Database Instances (applicable to v6.10).

Nutanix NDB Administration Guide: "Supported Databases for Provisioning" section, noting PostgreSQL availability.

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

To configure a database with a Time Machine protection mode that includes the Log Catchup operation in NDB, the most essential component is a Service Level Agreement (SLA) that supports continuous log retention. The Log Catchup operation enables point-in-time recovery (PITR) by replaying transaction logs from a specified point, ensuring minimal data loss and meeting Recovery Point Objective (RPO) requirements. This functionality depends on the Time Machine being configured with an SLA that includes the "Continuous Log Retention" option, which ensures transaction logs are captured and retained continuously alongside snapshots.

Option A is incorrect because a daily snapshot alone is insufficient without log retention to enable Log Catchup.

Option B is incorrect because an SLA retention schedule for daily snapshots does not inherently include continuous log capture, which is required for Log Catchup.

Option C is correct as it specifies the Continuous Log Retention option, the critical feature for enabling Log Catchup in a Time Machine SLA.

Option D is incorrect because while frequency settings are important, they are secondary to selecting an SLA with continuous log retention as the foundational requirement.

This configuration ensures robust data protection and recovery capabilities tailored to the database’s needs.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Setting Up SLAs with Log Catchup

Nutanix Support & Insights, Knowledge Base Article: "Configuring Time Machine with Log Catchup in NDB"

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