NCP-DB Leak Questions

To change the NDB GUI password via the CLI, the administrator should use the command era-server > security password reset. This command interacts with the NDB server (referred to as era-server in the CLI context) to reset the password for the GUI admin user. The process typically prompts for the new password and confirmation, ensuring secure password management. This is the supported method for CLI-based password changes in NDB.

Other options are incorrect:

A. sudo passwd era: The passwd command is for Linux user accounts, not NDB-specific GUI credentials.

B. sudo user name admin password: This is not a valid command syntax for NDB CLI.

C. era-server > username admin password: This lacks the correct subcommand (security password reset) and syntax.

Thus, the verified answer is D, aligning with NDB’s CLI security management.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.6: Managing NDB via CLI.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.5: Manage NDB Security (applicable to v7.5).

Nutanix NDB Administration Guide: "Changing GUI Password via CLI" section, detailing era-server commands.

When running the Linux prerequisites script for NDB, the -t argument is a required parameter that specifies the timeout interval. This argument defines the maximum time (in seconds) the script will wait for certain operations (e.g., connectivity checks, package installations) to complete before timing out. This is critical during the preinstallation phase to ensure the environment is properly configured and responsive, avoiding indefinite hangs. Other options are not associated with -t:

A. Operating System type: This is not a typical argument for the prerequisites script.

C. NDB server IP: This would be specified separately (e.g., via -s or a similar flag).

D. Database engine: This is irrelevant to the prerequisites script, which focuses on system setup.

Thus, the verified answer is B, aligning with the script’s purpose of managing execution timeouts.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.1: Running Prerequisites Scripts.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v7.5).

Nutanix NDB Installation Guide: "Running the Linux Prerequisites Script" section, detailing -t usage.

A SQL Server Database Group in NDB is a logical protection construct for databases that have common recovery-point and retention requirements. The databases are managed by one collective Time Machine and SLA, allowing NDB to coordinate snapshots and log backups and reduce Time Machine sprawl. However, grouping does not merge all database files into one common virtual-disk set. Each database retains its own set of storage disks while participating in the group-level protection workflow. The group also does not force databases onto different Always On Availability Group nodes, and it does not prevent an administrator from restoring or cloning an individual database. Those facts eliminate A, B, and C. Option D correctly describes separate per-database storage combined with centralized Time Machine management. Nutanix NDB Database Groups

A new web application with up to 200 concurrent connections to a PostgreSQL database requires a robust and scalable configuration. Provisioning a PostgreSQL HA (High Availability) instance in NDB is the most effective action to achieve this goal. An HA instance leverages replication (e.g., streaming replication) to distribute load and ensure availability, accommodating high concurrency by allowing multiple nodes to handle traffic. This approach simplifies configuration compared to manual scripting or parameter adjustments.

Option A (Use Post Create Command when provisioning the DB) is incorrect because post-create commands are for custom scripts, not optimal for handling concurrent connections.

Option B (Create a new Database Parameters profile) is incorrect because while it can tune settings, it’s less efficient than HA for scaling concurrency.

Option C (Edit the API equivalent shell script) is incorrect as it’s a manual and error-prone method compared to HA provisioning.

Option D is correct because a PostgreSQL HA instance natively supports high concurrency and availability.

Note: The typo "PostqreSQL" is assumed to mean "PostgreSQL."

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Provisioning HA Instances

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