Passed Exam Today NCP-DB

For enabling Multi-Cluster management on an Era installation, the hypervisor version must be supported and port 9440 must be open between the Era VM and clusters. This ensures that the Era VM can communicate with the clusters for management tasks1.

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

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) v6.5 Blueprint, Section 3: Configure an NDB Environment

To enable iSCSI connections between the Nutanix Database Service (NDB) server, Controller VMs (CVMs), and Prism Element, a Data Services IP must be configured in Prism Element. The Data Services IP acts as a cluster-wide address that facilitates iSCSI target discovery and connectivity. It is used by Nutanix Volumes (a block storage service) to present storage to external clients or services, such as the NDB server, via the iSCSI protocol. This IP ensures that iSCSI traffic is routed correctly and remains available even if a CVM fails, as ownership of the Data Services IP can move to another CVM in the cluster.

Configuring the Data Services IP is a prerequisite for integrating NDB with a Nutanix cluster, as NDB relies on iSCSI to manage database storage operations like provisioning and cloning. Without this configuration, the NDB server cannot establish the necessary connections to the CVMs for database-related tasks. Options like Virtual IP, Secondary DNS IP, and Backplane IP are not relevant in this context:

Virtual IP: This is typically associated with high-availability setups for applications, not iSCSI connectivity.

Secondary DNS IP: This pertains to network resolution, not storage connectivity.

Backplane IP: This is an internal network IP for cluster communication, not for external iSCSI access.

Thus, the correct and verified answer is the Data Services IP.

Official Nutanix Database Automation References

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

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution (applicable to v6.10 as foundational concepts remain consistent).

Nutanix Support & Insights Portal: "Configuring iSCSI Data Services IP for Nutanix Volumes" (general Volumes configuration applicable to NDB).