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

The Era copy data management service includes several components, one of which is the Time Machine. The Time Machine is responsible for collecting logs and snapshots from the database123. This functionality allows for granular clone and refresh operations, making it a crucial part of the Nutanix Era’s database as a service (DBaaS) solution1.

During an NDB upgrade, the upgrade process follows a specific order to maintain stability and HA. The Leader NDB API Server is upgraded first. This server coordinates API requests and ensures the control plane remains operational. Upgrading the leader first minimizes disruption, as subsequent components (e.g., other API servers, HAProxy) rely on its leadership role. Once the leader is upgraded, the remaining NDB HA control plane VMs (e.g., follower API servers, HAProxy) are updated in sequence.

Other options are incorrect:

A. NDB Server: Refers to the main NDB instance, not upgraded first.

C. Leader HAProxy: Upgraded after API servers to maintain load balancing.

D. NDB Agent VMs: Upgraded last, as they are client-side components.

Thus, the verified answer is B, reflecting the upgrade sequence.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "NDB Upgrade Process" section.

The Nutanix Era Time Machine provides various capabilities depending on the Service Level Agreement (SLA) selected during database registration1. For a database with a Bronze SLA, the Time Machine supports both “Log Catch up” and "Snapshots"2. “Log Catch up” allows the Time Machine to keep up with the latest changes in the database by capturing log data2. “Snapshots” are point-in-time copies of the database that can be used for recovery or cloning2.

According to the Nutanix Database Automation (NCP-DB) learning documents, an administrator can change the snapshot schedule for a given database by selecting the Time Machine, then under Action, select Update and define an appropriate schedule1. This is because the Time Machine in Nutanix Era allows you to specify the number of backups or snapshots the time machine should take, the time of day it takes those snapshots, and the day of the week it takes weekly or monthly backups1. These options help you build a complete schedule of time machine capture operations1. Even if the Time Machine is in a paused state, the administrator can still update the schedule1. Cloning the Time Machine or the database is not necessary for changing the snapshot schedule1.

To automate OS and database patching in a Nutanix NDB environment, the administrator should configure a Maintenance Window. A Maintenance Window in NDB allows the administrator to schedule automated patching tasks (e.g., OS updates and database software updates) during specified time periods, minimizing disruption to production workloads. This feature integrates with software profiles and can be set to run periodically or on-demand, ensuring patches are applied efficiently and consistently across the environment.

Option A (Access Control) is incorrect because Access Control manages user permissions, not automation of patching.

Option B (Pulse) is incorrect because Pulse is a monitoring tool, not a scheduling mechanism for patching.

Option C (Maintenance Window) is correct as it provides the scheduling and automation framework for patching activities.

Option D (SMTP Server) is incorrect because SMTP is for email notifications, not patching automation.

This configuration enhances operational efficiency and reliability.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Scheduling Maintenance Windows

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

Nutanix Database Service (NDB) supports high availability (HA) instances for certain relational database management systems (RDBMS). Among the listed options, NDB natively supports Oracle and PostgreSQL for HA configurations, enabling features like replication and failover. These databases are well-integrated with NDB’s Time Machine and HA frameworks.

Option A (MongoDB) is incorrect because MongoDB is a NoSQL database, not an RDBMS, and is not supported for HA instances in NDB.

Option B (MariaDB) is incorrect because, while MariaDB is an RDBMS, it is not currently supported for HA instances in NDB v7.5.

Option C (Oracle) is correct as NDB supports Oracle in HA mode with features like Data Guard integration.

Option D (PostgreSQL) is correct as NDB supports PostgreSQL HA with streaming replication.

Note: The typo "PostgreSGL" in the question is assumed to mean "PostgreSQL" based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Supported RDBMS for HA

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Engines

Nutanix Era is a database management system that provides API endpoints for automation and integration with external applications. These API calls are typically made over HTTPS for security, and the standard ports for HTTPS are 443 and 94401. Please note that the actual ports used can depend on the specific configuration of the Nutanix Era system. It’s always a good idea to check the system’s documentation or consult with the system administrator for the most accurate information.

In the Nutanix Era management interface, an administrator should perform an upgrade under the Administration > Maintenance section1. As part of the upgrade process, the Era server is upgraded first, followed by all the Era cluster agents and database server agents in parallel1. The Dashboard displays the current version and an option to upgrade the Era server to a latest version when a new version is available for upgrade1. This ensures that the Nutanix Era environment is always up-to-date with the latest features and security updates1.

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 SLAs are service level agreements that define the data protection and recovery objectives for NDB-managed databases. NDB SLAs consist of data retention policies that specify how long the snapshots and log backups of a database are kept in the Time Machine. Data retention policies can be customized to meet different business and compliance requirements, such as daily, weekly, monthly, or yearly retention periods. NDB SLAs also determine the frequency and schedule of the snapshots and log backups, as well as the storage location and replication options. An administrator who is tasked with auditing NDB SLAs will be reviewing the data retention policies of each database and Time Machine, as well as the snapshot and log backup history and status. The administrator will also be able to monitor the storage usage and performance of the NDB SLAs, and modify or delete the SLAs as needed. The other options are not part of the NDB SLAs, but rather separate features or concepts of NDB. Snapshot schedules are the intervals at which NDB takes snapshots of the databases, which are determined by the SLAs. Clone management is the process of creating, refreshing, or deleting database clones from the Time Machine. Recovery time objective (RTO) is the maximum acceptable time for restoring a database after a failure, which is influenced by the SLAs, but not defined by them. References:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 5 - Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies

Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: SLA Concepts

Nutanix Database Service (NDB) User Guide, Chapter 6: SLAs, Section: SLA Overview