Free Practice Questions for Nutanix NCP-DB Exam

HA drivers are software components that enable high availability features for database VMs, such as failover, fencing, and heartbeat. HA drivers can be upgraded using the Life Cycle Management (LCM) feature of Nutanix Prism. LCM can detect the available updates for HA drivers and apply them to the database VMs in a non-disruptive manner. LCM can also perform health checks and pre-upgrade validations to ensure the successful completion of the upgrade process. One-click software upgrade is a feature of Nutanix Era that allows you to upgrade the Era software itself, not the HA drivers. Database VM OS patching is a feature of Nutanix Era that allows you to patch the operating system of the database VMs, not the HA drivers. Database software patching is a feature of Nutanix Era that allows you to patch the database software of the database VMs, not the HA drivers. References:

Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 3: Configuring NDB High Availability, Slide 9: HA Driver Upgrade

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.4: Upgrade databases

When provisioning a PostgreSQL cluster instance with an external load balancer in NDB, the administrator creates a software profile from a reference VM. The reference VM typically includes software like Patroni (for HA management), HAProxy (for internal load balancing), keepalived (for high availability IP management), and etcd (for distributed configuration). Since an external load balancer is used, the internal HAProxy can be omitted from the reference VM. NDB will rely on the external load balancer to distribute traffic, eliminating the need for HAProxy in the software profile, while the other components remain essential for cluster management.

Option A (Patroni) is incorrect because Patroni is required for PostgreSQL HA management.

Option B (HAProxy) is correct as it can be omitted when an external load balancer is configured.

Option C (keepalived) is incorrect because keepalived is needed for HA IP failover.

Option D (etcd) is incorrect because etcd is necessary for distributed configuration in the cluster.

This adjustment streamlines the profile for external load balancer use.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Creating Software Profiles for HA Instances

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

NDB creates database clones by using Nutanix space-efficient snapshots instead of copying every source database block into a new 2 TB allocation. The initial clone primarily consists of metadata and references to the source snapshot’s existing blocks. Consequently, it consumes near-zero additional storage when it is first created. The clone becomes an independent database environment, and new physical capacity is consumed only when blocks are changed or newly written. Because the question specifies that the clone remains read-only, there should be no meaningful database write growth after creation. Its storage consumption is therefore not equal to the source size and is not determined by fixed compression ratios such as 50 or 20 percent. Nutanix’s official Clone Management documentation states that NDB clones are highly space-efficient and initially consume near-zero additional bytes.

The minimum frequency configurable for the NDB Log Catch-up operation is 15 minutes. This setting determines how frequently the log catch-up process runs, which is crucial for maintaining data integrity and ensuring up-to-date database states.

NDB diagnostic collection gathers relevant logs from the NDB control plane and the database server VMs participating in the failed operation. For a Linux database server, the NDB agent collects applicable operating-system information, database-engine logs, work-driver output, and operation-specific diagnostic data. These files are packaged into a downloadable compressed bundle associated with the failed operation, allowing administrators or Nutanix Support to examine the complete execution context. NDB does not copy the active database data directory, create a runtime memory dump, or use a hypervisor snapshot of the log directory. Time Machine protects database data through snapshots and transaction logs; it is not the mechanism used to assemble support bundles. The official Nutanix instructions for viewing operation logs and downloading diagnostic bundles describe the collected and compressed diagnostic information.

In NDB, a Time Machine manages snapshots and log catch-up operations for database protection and recovery. The scenario describes a Time Machine where automatic snapshot and log catch-up activities (both automatic and manual) are halted, and manual snapshots cannot be created. This indicates the Time Machine is in a PAUSED state.

In NDB, the Time Machine states are:

FROZEN: A temporary state during specific operations (e.g., cloning), but it doesn’t halt all activities permanently.

OFFLINE: Indicates the Time Machine is unavailable or not operational, often due to connectivity or configuration issues, but this typically prevents access rather than just halting operations.

PAUSED: Explicitly stops all scheduled and manual snapshot/log activities, often manually triggered by an administrator or due to an error condition (e.g., resource constraints). Operations resume when unpaused.

READY: The normal operational state where snapshots and log catch-ups occur as scheduled.

Given the inability to create manual snapshots alongside halted automatic operations, PAUSED is the most fitting status, as it reflects an intentional or enforced suspension of activities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Time Machines.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Time Machine States (applicable to v7.5).

Nutanix NDB Administration Guide: "Time Machine Statuses and Operations" section.

The correct answer is A and D because these are the two Time Machine options that are available when creating a database clone in NDB. Point in time allows the user to specify a date and time to create a clone from a specific point in the database history. Snapshot allows the user to select a previously taken snapshot to create a clone from a consistent state of the database. Option B is incorrect because Restore point is not a Time Machine option, but a feature that allows the user to restore a source database to a previous point in time. Option C is incorrect because Backup is not a Time Machine option, but a feature that allows the user to backup a database to a remote location.

The following sources provide more information about the Time Machine options and cloning features in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases Using Time Machine, Lesson 4.2: Cloning Databases

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 5 - Protect NDB-managed Databases Using Time Machine

Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section 6.2: Cloning Databases

[Nutanix Support & Insights], NDB Time Machine Under the Hood

 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.

The Storage Usage widget on the NDB dashboard provides the required entity-level storage information. It displays the percentage of storage consumed by registered Nutanix clusters and NDB entities, including source databases, database clones, and Time Machines. Administrators can use this information to distinguish production database capacity from space consumed by protected copies and downstream clones. NDB periodically collects and stores historical usage information, which also supports storage-trend analysis and capacity forecasting. Prism Element and Prism Central provide infrastructure-level capacity information, but they do not present the same NDB-aware classification of source databases, clones, and Time Machines. NCM reporting is therefore unnecessary for this specific requirement. The official NDB Dashboard reference identifies Storage Usage as the dashboard widget that reports consumption for clusters, data sources, clones, and Time Machines.

The Alerts dashboard in Nutanix displays alert messages with three severity levels: Critical, Warning, and Info1. These severity levels help users understand the importance and urgency of each alert, allowing them to prioritize their responses accordingly1.