Nutanix NCP-DB Online Access

To reset the NDB GUI password in Nutanix Database Service (NDB), an administrator must access the system through an SSH session and use the appropriate command-line interface (CLI) tools provided by NDB. The correct process involves entering the era-server CLI, which is the specific CLI environment for managing NDB-related configurations, including security settings like password resets. Once in the era-server CLI, the administrator executes the security password reset command to initiate the password reset process for the NDB GUI. This method ensures that the reset is performed within the NDB-managed environment securely and aligns with Nutanix’s recommended administrative procedures.

Option A is correct because it specifies the era-server CLI and the exact command security password reset, which are consistent with NDB’s administrative tools for managing GUI access credentials.

Option B (sudo passwd era) is incorrect because era is not a system user account in the context of NDB’s Linux-based control plane; this command pertains to standard Linux user management, not NDB-specific GUI password resets.

Option C (sudo passwd admin) is also incorrect as admin refers to a generic user that may not correspond to the NDB GUI account, and this approach bypasses NDB’s internal security mechanisms.

Option D is incorrect due to a typo (era CLI instead of era-server CLI), which renders it imprecise despite the intent being similar to Option A.

This process assumes the administrator has SSH access to the NDB control plane VM and the necessary privileges to execute these commands.

References

Nutanix Database Service (NDB) User Guide, Section: Administering an NDB Environment, Subsection: Managing Access Controls and Password Resets

Nutanix Support & Insights, Knowledge Base Article: "Resetting NDB GUI Password via CLI"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 6: Administer an NDB Environment

NDB High Availability uses multiple API Server VMs to provide the user interface and REST API services. The platform can automatically tolerate the failure of up to two service VMs, but if every API Server VM is offline, the API service becomes completely unavailable and manual intervention is required. Recovery requires bringing at least one API Server VM back online. Once an API Server is running, the NDB API service can restart and the remaining HA components can rejoin or recover through the normal resiliency mechanisms. Restarting HAProxy first cannot restore an API service when no API Server is available. Repository VMs should not be recreated because they contain NDB metadata, and registered Nutanix clusters do not need to be registered again. Therefore, the correct answer is A. NDB HA failure and recovery scenarios

================

NDB uses a registered Nutanix Object Store as durable storage for database log backups. When a database is registered and the administrator does not select a particular Object Store for its log drive, NDB does not fail the registration or ignore object storage. It evaluates the registered stores and assigns the first one reachable from the NDB control plane. This selection applies to the newly registered database, and subsequent log backups are written to that chosen store. The Nutanix registration procedure and knowledge-base guidance explicitly describe this first-reachable behavior when no store is specified. Therefore, option A is correct; ignoring the store, selecting it according to an unspecified priority, or failing the operation contradicts the documented workflow. Nutanix documentation

The NDB alert retention feature allows the database administrator to configure the duration for which the NDB alerts are stored and displayed in the NDB instance. The NDB alert retention feature supports alert retention globally, meaning that the same retention period applies to all the alerts generated by the NDB instance, regardless of the source cluster, policy, or operation. The database administrator can set the alert retention period from 1 day to 365 days, or choose to retain the alerts indefinitely. The NDB alert retention feature helps to manage the storage space and the visibility of the NDB alerts.

The NDB alert retention feature does not support retention at the individual policy, grouped policy, or registered cluster level. The NDB alert retention feature applies to all the alerts uniformly, and does not allow the database administrator to specify different retention periods for different policies or clusters.

Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment, Lesson 3.2: Nutanix Era Deployment, slide 11.

Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slide 6.