Nutanix Updated NCP-DB Exam Questions and Answers by edwin

When an administrator changes the NDB language settings from English to Spanish, but the language reverts to English when accessing NDB from a different workstation, it indicates that the language settings are tied to the web browser on the original workstation rather than being globally applied. NDB’s language settings are typically stored locally in the browser’s cache or preferences (e.g., via cookies or browser locale settings), meaning they do not persist across different devices or browsers unless explicitly synchronized (e.g., via user profile settings, which NDB does not universally enforce).

Other options are incorrect:

B. The language settings match workstation regional settings: This would depend on the OS locale, not the observed behavior of reverting to English.

C. The language settings revert to English after logoff: NDB does not reset language settings upon logoff; the issue is device-specific.

D. The language settings are bound to NDB users: If this were true, the language would persist across workstations for the same user, which is not the case here.

Thus, the verified answer is A, reflecting browser-local language management.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.3: User Interface Customization.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.2: Navigate the NDB UI (applicable to v7.5).

Nutanix NDB User Guide: "Customizing Language Settings" section, noting browser dependency.

 According to the Nutanix Database Automation (NCP-DB) learning documents, to refresh an existing DB Clone, a developer with RBAC privileges in Era needs to navigate to Databases > Clones. From there, they select the appropriate clone from the table, click Refresh, select the desired Point In Time or Snapshot, and then click Refresh12. This process allows the developer to update the cloned database3.

NDB Time Machine protects Microsoft SQL Server databases through application-consistent snapshots and a continuous sequence of transaction-log backups captured by Log Catch-up operations. When the latest protected time is selected, NDB uses the appropriate snapshot as the baseline and applies the required transaction logs through the most recent available recovery point. This produces a transactionally consistent clone rather than a crash-consistent VM copy. NDB does not need to leave the source database in read-only mode, and Volume Shadow Copy Service alone cannot provide the transaction-log replay required for granular point-in-time cloning. “Latest Time” means the latest point covered by the valid Time Machine snapshot and log chain, not an unprotected wall-clock instant after the last log capture. Nutanix’s Database Log Backup Management documentation explains that Log Catch-up captures database transaction logs for point-in-time cloning.

To add multiple databases to an existing PostgreSQL instance managed by NDB, the administrator should use the NDB graphical user interface (GUI). The GUI provides a user-friendly way to modify the parameter profile associated with the PostgreSQL instance, allowing the addition of new databases by adjusting settings such as database names, sizes, or configurations. This process typically involves navigating to the "Databases" or "Instances" section, selecting the PostgreSQL instance, and editing the parameter profile to include additional databases.

Other options are less appropriate:

A. Modify parameter profile using ncli: The ncli (Nutanix Command Line Interface) is used for cluster-level management in Prism, not for NDB database configuration.

C. Modify parameter profile using post script: Post-scripts are used for custom actions post-provisioning, not for modifying parameter profiles to add databases.

D. Modify parameter profile using NDB CLI: While NDB has a CLI, the GUI is the recommended and supported method for such configuration changes, offering a guided workflow and validation.

Thus, the verified answer is B, leveraging the NDB GUI for ease and compliance with best practices.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.4: Modifying Database Configurations.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.3: Modify Parameter Profiles (applicable to v7.5).

Nutanix NDB Administration Guide: "Managing PostgreSQL Instances" section, detailing GUI-based modifications.