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

The scenario describes a PostgreSQL HA deployment managed by NDB, where an NDB-managed VLAN (PGSQLVLAN40) restricts database communication to only within VLAN 40. This indicates a network isolation issue, likely due to VLAN segmentation or routing misconfiguration, preventing communication with external networks or other VLANs. Since NDB manages the VLAN and assigns it to the database VMs, the issue lies beyond NDB’s direct control and involves the underlying network infrastructure (e.g., switches, routers, or Prism Element network settings).

Here’s why the other options are insufficient:

A. Use VLAN 1: VLAN 1 is typically a default VLAN and not recommended for production use due to security and isolation concerns. Changing to VLAN 1 does not address the root cause and could introduce further issues.

B. Change the Default Gateway on the PostgreSQL servers and update NDB: While adjusting the default gateway might enable external communication, this is a workaround rather than a fix. NDB manages the network configuration, and manual changes could be overwritten or cause inconsistency. The root issue (VLAN routing) remains unaddressed.

D. Delete the database servers, VLAN name PGSQLVLAN40, and redeploy: This is overly disruptive and unnecessary, as recreating everything under a new VLAN name does not guarantee resolution unless the network configuration is corrected.

The best approach is to engage the networking team to investigate and resolve the issue, such as configuring inter-VLAN routing, updating firewall rules, or adjusting the default gateway at the network level. Going forward, the administrator should collaborate with the networking team during VLAN planning to ensure proper connectivity. Thus, the verified answer is C.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: Troubleshooting NDB, Lesson 4.1: Identifying and Resolving Network Issues.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.2: Resolve Network-Related Issues (applicable to v7.5).

Nutanix NDB Administration Guide: "Networking Considerations for HA Deployments" section.

NDB coordinates Oracle-native recovery mechanisms when restoring a selected PDB to a specified point in time. Time Machine supplies the required snapshot and transaction-log recovery points, while Oracle Recovery Manager restores the necessary PDB datafiles and applies archived redo through the requested timestamp. Oracle redo is maintained at the container database level, so the process does not literally use a completely independent redo stream for each PDB. Nevertheless, Oracle’s recovery operation limits the recovery scope to the selected PDB and processes all required archived-log switches automatically. NDB does not reconstruct Oracle transactions using Prism Central’s Cassandra data, apply flat-text backup files, or require the administrator to append database blocks manually. Nutanix documents the ability to restore selected PDBs by snapshot or timestamp in its official Oracle PDB and CDB management guidance.

Option A: On the Era Dashboard Database Summary Table under Source Database. The dashboard provides a summary of the databases, including their sizes1.

Option B: Under the Capacity widget on the Database Server VMS > List database summary page. While this might provide information about the capacity, it does not specifically provide the size of a Source Database.

Option C: On the Databases > Sources table. This table provides detailed information about the databases, including their sizes1.

Option D: On the Profiles > Database Parameters list for the assigned DB Parameter Profile. This list provides parameters for the database but does not provide the size of a Source Database.

Option A: Nutanix Era requires network prerequisites like NTP, DNS servers, gateway, and subnet mask to be available and visible. These are essential for the proper functioning of the Era instance1.

Option B: One static IP address must be available and can be changed using CLI after VM deployment. This is necessary for the Era VM to communicate with other components in the network1.

Option C: While a storage container is necessary for Nutanix infrastructure, it is not a network prerequisite specifically for deploying an Era instance.

Option D: An SMTP server and details are typically used for sending notifications, but they are not a network prerequisite for deploying an Era instance. They are more related to the operational aspect post-deployment.

In a high availability (HA) Nutanix Database Service (NDB) environment, custom SSL certificates are used to secure communication between clients (e.g., NDB GUI, API calls) and the NDB control plane. The HA Proxy VMs serve as the entry point for all external traffic, load balancing requests across the NDB API server VMs and providing secure SSL termination. When configuring custom SSL certificates, they must be updated on all HA Proxy VMs to ensure consistent and secure communication across the HA environment. Updating only a subset of servers or other components (like API or Repository VMs) would lead to inconsistencies or SSL handshake failures.

Option A (All API server VMs) is incorrect because the API servers do not directly handle external SSL termination; this is managed by the HA Proxy layer.

Option B (All HA Proxy VMs) is correct as these VMs are responsible for SSL termination and load balancing in an HA setup, requiring the custom certificates to be applied uniformly.

Option C (The API and Repository VMs running on the primary cluster) is incorrect because Repository VMs do not handle client-facing traffic, and the API servers rely on HA Proxy for SSL handling.

Option D (The primary API, Repository, and HA Proxy servers) is incorrect because it implies a single "primary" server focus, whereas in an HA setup, all HA Proxy VMs (not just a primary one) must be updated.

This aligns with NDB’s HA architecture, where HA Proxy VMs are the critical components for SSL certificate management.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring High Availability and SSL Certificates

Nutanix Support & Insights, Knowledge Base Article: "Configuring Custom SSL Certificates in NDB HA Environments"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 3: Configure an NDB Environment

Before updating Oracle Database software, you need to download the Patch Set Update (PSU) from Oracle support. A PSU is a collection of critical and security patches for Oracle products. You need to have a valid Oracle account and access to the My Oracle Support portal to download the PSU. You also need to check the compatibility and prerequisites of the PSU before applying it to your Oracle Database software. NDB uses out-of-place patching for Oracle, which means you need to create a new software profile version with the patched Oracle software and use it to update your existing databases. References:

Patch Oracle Database Software, Nutanix Support & Insights

Nutanix Certified Professional - Database Automation (NCP-DB), Section 4 - Operate and Maintain an NDB Environment

Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.4 - Patching Databases

The correct answer is B and D because these are the two status values that can be set within the Alerts Dashboard in NDB. Resolved means that the alert has been fixed and no longer requires attention. Acknowledged means that the alert has been seen and is being worked on. Option A is incorrect because Auto is not a status value, but a mode that automatically resolves alerts based on predefined rules. Option C is incorrect because Data Resiliency is not a status value, but a feature that ensures the availability and integrity of the data in NDB.

The following sources provide more information about the Alerts Dashboard and its status values in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 3: Monitoring Alerts and Storage Usage Within an NDB Implementation, Lesson 3.1: Monitoring Alerts

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 3 - Monitor Alerts and Storage Usage Within an NDB Implementation

Nutanix Database Service (NDB) User Guide, Chapter 3: Monitoring Alerts and Storage Usage Within an NDB Implementation, Section 3.1: Monitoring Alerts

[Nutanix Support & Insights], Resolving All Alerts Related to a Database or Database Server VM in NDB

According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era is a database management tool that automates and simplifies database operations, including provisioning, patching, upgrading, and more1. However, for a database to be managed by Era, it must be registered with Era1. This means that if a database is on a non-Nutanix platform, it cannot be directly upgraded using an Era workflow. It must first be migrated to a Nutanix platform and registered with Era before it can be managed and upgraded using Era1.

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.

In an NDB high availability (HA) environment spanning multiple Nutanix clusters, with two clusters running VMware ESXi and one running Nutanix AHV, cross-hypervisor compatibility becomes essential to manage the heterogeneous environment effectively. Nutanix Prism Central is the centralized management platform that provides a unified interface and orchestration capabilities across multiple clusters, regardless of the underlying hypervisor (ESXi or AHV). For NDB HA to function seamlessly across these clusters, Prism Central is required to coordinate cluster operations, manage resources, and ensure consistent policy enforcement, including VM placement, failover, and database management tasks. It abstracts the differences between hypervisors, enabling NDB to operate in a mixed environment.

Option A (Stretched VLANs for all nodes) is incorrect because stretched VLANs address network connectivity, not hypervisor compatibility or NDB HA management.

Option B (NGT - Nutanix Guest Tools) is incorrect as NGT enhances guest VM functionality (e.g., drivers, backups) but does not facilitate cross-hypervisor orchestration for NDB HA.

Option C (Nutanix Prism Central) is correct because it provides the necessary multi-cluster management and compatibility layer for NDB HA across ESXi and AHV.

Option D (VirtlO) is incorrect as VirtIO refers to paravirtualized drivers for VMs, not a component for NDB HA or cross-hypervisor support.

Prism Central’s role ensures that NDB can manage database workloads across diverse hypervisor platforms efficiently.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Multi-Cluster and Multi-Hypervisor Support

Nutanix Prism Central Administration Guide, Section: Managing Mixed Hypervisor Environments

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 3: Configure an NDB Environment