During maintenance, a team wants to power off the repository VM. The VM is not the primary or synchronized copy node. What is the expected outcome?
Correct Answer: B
In an NDB environment, the repository VM stores metadata and configuration data but is not a critical runtime component for service availability. If the team powers off the repository VM during maintenance, and it is neither the primary nor a synchronized copy node, the NDB service will continue to operate without interruption. NDB's high availability (HA) architecture, managed by HAProxy and other components, ensures redundancy and failover capabilities, allowing the system to rely on the primary and synchronized nodes. The repository VM's downtime only affects metadata access, which can be restored post-maintenance without impacting ongoing database operations. * Option A (The HAProxy VMs will failover instead) is incorrect because HAProxy failover is triggered by primary service node failures, not repository VM power-off. * Option B (There will be no service interruption) is correct as the HA design tolerates a non-primary, non-synchronized repository VM being offline. * Option C (Manual interaction will be required to restore service) is incorrect because no service restoration is needed during this scenario. * Option D (NDB services will fail over immediately) is incorrect because failover is not triggered by a non-critical repository VM power-off. This reflects NDB's robust HA implementation. References * Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: High Availability Architecture * Nutanix Support & Insights, Knowledge Base Article: "Impact of Repository VM Maintenance in NDB" * Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment
Question 52
Within NDB, an administrator needs to register a PostgreSQL database server VM with a database. Where should the database data and log files be located in order to successfully complete this task?
Correct Answer: A
To register a PostgreSQL database server VM with a database on NDB, the database data and log files must be located on a separate mount point from the operating system and the binary installation. This is because NDB uses the mount point as the identifier for the database server VM and the database. If the data and log files are on the same mount point as the operating system or the binary installation, NDB will not be able to recognize them as a valid database server VM or database. Therefore, the administrator should create a separate mount point for the data and log files and specify it during the registration process. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [How to Allow Remote Access to PostgreSQL database], [5 Ways to Host PostgreSQL Databases], [Starting the Database Server].
Question 53
An administrator has been asked to patch several Nutanix database server VMs. Prior to patching, what should the administrator configure?
Correct Answer: A
Before patching several Nutanix database server VMs using the "Patch OS now" feature in NDB, the administrator must configure a Repository. A repository (e.g., a custom patch repository or Nutanix-provided source) contains the OS updates or patches (e.g., for Windows or Red Hat-based systems). NDB requires this repository to be specified to fetch and apply the patches, ensuring the database VMs are updated from a validated source. Other options are unrelated to patching: * B. Active Directory Access: Used for authentication, not patching. * C. pulse: Refers to Nutanix Pulse for support, not patch configuration. * D. An SMTP Server: Configured for alerts, not patching. Thus, the verified answer is A, reflecting the patching prerequisite. Official Nutanix Database Automation References * Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.3: Creating Maintenance Plans. * Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v6.10). * Nutanix NDB Administration Guide: "Configuring Patch Repositories" section.
Question 54
Within the NDB GUI, an administrator needs to set the shortest schedule interval possible for a database log catch up. Which value, in minutes, will satisfy this requirement?
Correct Answer: C
The NDB GUI allows an administrator to set the schedule interval for a database log catch up, which is the process of collecting transaction logs periodically from the source databases and storing them in the time machine. The shortest possible value for this interval is 15 minutes, as per the NDB documentation1. This means that the NDB time machine will capture the database logs every 15 minutes and use them for backup, restore, clone, and refresh operations. References: Nutanix Database Management & Automation (NDMA), page 29; Nutanix Support & Insights, section "Log Catch-up"
Question 55
An administrator needs to reset the NDB GUI password. What should the administrator perform from the SSH session?
Correct Answer: A
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) v6.5 Blueprint, Section 6: Administer an NDB Environment