Nutanix Certified Professional (NCP) NCP-DB Syllabus Exam Questions Answers

NDB uses Oracle out-of-place patching for Oracle database software. Instead of modifying the actively used Oracle home directly, NDB prepares or uses a separate Oracle home containing the required patched software and then moves the database to that home through an orchestrated workflow. This method keeps the original Oracle home available and reduces the risks associated with changing production binaries in place. It also supports more predictable patching and recovery procedures because the old and new software homes remain logically separated. Binary synchronization and in-memory synchronization are not Oracle patching methods used by NDB. In-place patching would directly modify the existing Oracle home and therefore does not describe the documented NDB workflow. Nutanix explicitly states that NDB uses out-of-place patching in its official Oracle database patching documentation.

The "Savings over traditional cloning" metric in the Data Usage widget on the NDB dashboard reflects the efficiency of NDB’s cloning technology compared to traditional full-copy cloning methods. NDB leverages Nutanix’s near-zero byte cloning capability, which creates lightweight clones by sharing base data and only storing changes (deltas). This metric specifically quantifies the disk space saved by using these efficient clones instead of duplicating entire datasets, as would occur in traditional cloning. It highlights NDB’s storage optimization for database provisioning and management.

Option A is correct as it directly ties to NDB’s near-zero byte cloning technology, a core feature for space efficiency.

Option B (Compression) is incorrect because compression is a separate storage optimization technique not specifically tied to cloning savings.

Option C (Shadow clones) is incorrect because shadow clones are a Nutanix feature for caching, not the cloning mechanism used by NDB Time Machines.

Option D (Deduplication) is incorrect as deduplication, while related to storage savings, is not the primary mechanism reflected in this cloning-specific metric.

This metric helps administrators quantify the benefits of NDB’s cloning approach in terms of storage utilization.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Introduction to NDB, Section: Understanding Cloning and Storage Efficiency

Nutanix Support & Insights, Technical Note: "Interpreting NDB Dashboard Metrics"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 1: NDB Concepts and Architecture

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) v7.5Blueprint, Section 5: Protect Databases Using Time Machine

NDB deployments on NC2 use overlay networking created with Nutanix Flow Virtual Networking. Consequently, an appropriate Flow overlay subnet must be created for NDB and the database server VMs that it will manage. A floating IP address must also be created or assigned to the NDB VM so that the NDB interface and services are reachable through the cloud networking environment. A Flow underlay subnet is not the supported network type for this deployment. Although an NC2 environment ultimately operates within AWS networking infrastructure, creating a native AWS VPC is not the NDB-specific deployment step requested by the question. Nutanix’s NC2 networking documentation identifies Flow-created overlay networks, while the Flow integration guidance describes assigning a floating IP address to the NDB VM.