Nutanix NCP-DB Online Access

To free up space in the NDB-managed container, the administrator needs to identify storage consumption sources. Two key locations in NDB provide actionable insights:

C. Clone Database table: This displays all clone databases, including their Size (current storage usage) and Last Refresh (indicating age or staleness). Clones often consume significant space, and older or unused ones can be deleted to reclaim storage.

D. Snapshot table in Time Machine: This shows snapshots with details like Reclaimable Space (space recoverable by deletion) and Age (how long snapshots have existed). Old or unnecessary snapshots are prime candidates for reclamation.

Why not the other options?

A. NDB Dashboard (Clone Data Age): While it provides a high-level view, it lacks granular details (e.g., size per clone) needed for targeted reclamation.

B. Source Database grid: This shows registered databases’ size and status but doesn’t focus on derivative objects (clones/snapshots) that typically consume more space.

Thus, C and D are the best locations for detailed storage analysis and reclamation research.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Storage and Resource Management, Lesson 6.2: Monitoring and Reclaiming Storage.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.1: Manage Storage Consumption (applicable to v6.10).

Nutanix NDB Administration Guide: "Clone Database Table" and "Time Machine Snapshot Table" sections.

 Nutanix Era provides a unified database operating model that delivers simplicity, performance, availability, and security across private and public clouds1. It standardizes your Oracle database ecosystem by mass patching the databases with one-click simplicity2. This includes the following features:

Automated Patching: Era patching can be automated using REST API/CLI for scheduled patching many Oracle servers in a fleet patching scenario1. This allows for the standardization of your Oracle database ecosystem by mass patching the databases with one-click simplicity2.

Automatic Rollback: Era patching for Oracle databases has automatic rollback if any of the steps in the patching workflow fails1. This ensures that your databases remain secure and functional even if an issue arises during the patching process1.

When creating a Network Profile for NDB HA VMs (e.g., NDB API and Repository VMs) spread across three Nutanix clusters, the required type is PostgreSQL HA instance managed outside NDB. NDB HA relies on a PostgreSQL database for its control plane, and in a multi-cluster HA setup, this PostgreSQL instance must be configured for high availability (e.g., using streaming replication) outside NDB’s management. The Network Profile must support this external HA instance’s networking requirements (e.g., VLANs, IP ranges) to ensure connectivity across clusters.

Other options are incorrect:

A. PostgreSQL HA instance managed in NDB: NDB manages database instances, not its own HA control plane database.

B. PostgreSQL single instance managed in NDB: A single instance lacks HA, unsuitable for multi-cluster.

D. PostgreSQL single instance managed outside NDB: Lacks HA, insufficient for NDB HA VMs.

Thus, the verified answer is C, aligning with NDB HA architecture.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.2: Configuring Multi-Cluster HA.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v6.10).

Nutanix NDB Administration Guide: "Network Profile Configuration for HA VMs" section.

When registering a Nutanix cluster with the Nutanix Database Service (NDB), the Prism Element user account used for registration must have sufficient privileges to perform cluster-level operations. The recommended role for this task is Cluster Admin. The Cluster Admin role in Prism Element provides the necessary permissions to manage cluster resources, including storage, networking, and integration with external services like NDB. This role is required because registering a cluster with NDB involves tasks such as establishing connectivity, validating configurations (e.g., Data Services IP), and ensuring that NDB can interact with the cluster’s Controller VMs and storage infrastructure.

The default administrative account in Prism Element (typically "admin") often serves as the initial Cluster Admin user. However, if an administrator needs to remove or replace this default account for NDB operations, a new user with the Cluster Admin role must be created and used instead. Other roles listed have different purposes:

Super Admin: This is not a standard role in Prism Element; it may refer to elevated privileges in other contexts but is not specifically defined for Nutanix cluster registration.

User Admin: This role is limited to managing users and permissions, lacking the broader cluster management capabilities needed for NDB registration.

Backup Admin: This role is specific to backup-related tasks and does not encompass the full scope of cluster management required for NDB integration.

Therefore, the Cluster Admin role is the recommended and verified choice for registering a Nutanix cluster with NDB, ensuring seamless operation and management.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster with NDB.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix cluster in NDB (applicable to v6.10 with no significant role changes documented).

Nutanix Prism Element Guide: "Role-Based Access Control (RBAC)" section, detailing Cluster Admin privileges.