A stretched VLAN is a virtual network that spans across multiple Nutanix clusters and allows the communication between VMs on different clusters using the same subnet. A stretched VLAN can be used to provide high availability and load balancing for NDB components, such as HAProxy VMs, that require a virtual IP address (VIP) to be accessible from any cluster. To add a stretched VLAN across two clusters in NDB, the administrator needs to meet two prerequisites: the VLAN must be static and both clusters must be registered in NDB. A static VLAN is a VLAN that is manually created and configured by the administrator, as opposed to an IPAM VLAN that is automatically created and managed by NDB. A static VLAN can be added to a stretched VLAN in NDB, while an IPAM VLAN cannot. Both clusters must be registered in NDB before adding a stretched VLAN, as NDB needs to have the information and access to the clusters and their networks. The administrator can register the clusters in NDB using the Prism Element details, agent network configuration, and storage container information. The other option, Nutanix Cluster Management, is not a prerequisite for adding a stretched VLAN in NDB. Nutanix Cluster Management is a feature that allows the administrator to manage multiple Nutanix clusters from a single NDB UI, such as creating or deleting clusters, adding or removing nodes, or performing cluster operations. Nutanix Cluster Management is not required for adding a stretched VLAN, as the VLANs are created and configured in Prism Element, not in NDB.  References :

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 , Section 2 - Deploy and Configure an NDB Solution, Objective 2.3: Configure NDB High Availability

Nutanix Database Management & Automation (NDMA) Course , Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.3: Configuring NDB High Availability, Topic: NDB HA Architecture and Components

Nutanix Database Service High Availability Deployment Overview , Section: HAProxy VMs and Stretched VLANs

[Configuring a Virtual NIC to Operate in Access or Trunk Mode - Nutanix], Section: Creating a vNIC in Access or Trunk Mode

To allow a non-administrative NDB user to provision an Oracle database using a Software Profile created by an administrator, the administrator must promote the Software Profile to Published . In NDB, Software Profiles define the database software version and configuration (e.g., Oracle binaries). By default, a newly created profile is in a draft or private state. Promoting it to " Published " makes it available for use by other NDB users, including non-administrative ones, within the access control framework. This ensures the profile is validated and accessible without requiring individual user assignments.

Other options are incorrect:

A. Ensure that specified users have access to the Software Profile using Access Control : Access Control manages user permissions but does not make the profile available unless it is published.

B. Replicate the Software Profile to other Nutanix clusters : Replication is for HA or disaster recovery, not user access.

C. Ensure that the Software Profile has been properly versioned to the latest release of Oracle : Versioning ensures compatibility but does not grant user access.

Thus, the verified answer is D , aligning with NDB’s profile management workflow.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Managing Software Profiles.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Configure Software Profiles (applicable to v6.10).

Nutanix NDB Administration Guide: " Publishing Software Profiles " section.

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) v6.5 Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.2: Navigate the NDB UI (applicable to v6.10).

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

The administrator can remediate the issue of critical storage alerts by scaling up the storage directly from the Database Summary page for that specific DBA database.  This action allows for an increase in storage capacity to alleviate space constraints and prevent future critical alerts related to storage space 1 . The other options are not correct, as they either involve scaling the entire database group, which may not be necessary or desired, or require additional steps outside of NDB, which may not be feasible or efficient.  References :

1 : Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.4: Database Scaling, slide 5

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

Nutanix Database Service (NDB) uses software profiles for database patching to keep your databases secure and optimized 1 .  When a new database is provisioned, it will be on your current environment’s database version to maintain consistency and stop version sprawl 1 .  Therefore, after an administrator has applied an Oracle security patch to a database server VM registered in Era, the change can be made available to other existing database instances by creating a new software profile in Era from the patched VM 1 .

When cloning an SQL database with Transparent Data Encryption (TDE) enabled in NDB, the target server must handle the encryption keys to ensure the cloned database remains functional and secure. TDE uses a keystore (e.g., a bundle file containing the master key and certificate) to encrypt data. Two steps are required: (1) The administrator must back up the keystore bundle file from the source database server VM and transfer it to the target server, ensuring the clone can decrypt the data. (2) After the clone is created, the administrator must run the post-clone command script, which configures the TDE keys on the target server, completes the encryption setup, and activates the cloned database.

Option A (Backup the .cer and .pvk files from the source database server VM) is incorrect because TDE in SQL Server typically uses a keystore bundle, not separate .cer and .pvk files.

Option B (Backup the keystore bundle file from the source database server VM) is correct as it ensures the encryption keys are available on the target.

Option C (Run the pre-clone command script) is incorrect because pre-clone scripts are for preparation, not TDE-specific post-clone setup.

Option D (Run the post-clone command script) is correct as it finalizes the TDE configuration on the target server.

These steps ensure a successful TDE-enabled clone.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Cloning TDE-Enabled Databases

Nutanix Support & Insights, Knowledge Base Article: " Cloning SQL Server with TDE in NDB "

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

NDB supports SMTP server configuration for sending email notifications and alerts. SMTP server configuration requires specifying the SMTP server address, port, username, password, and encryption method. The encryption method determines how the email messages are secured during transmission. NDB supports two encryption methods for SMTP server configuration: TLS and SSL.

TLS (Transport Layer Security) is a protocol that encrypts and authenticates data between the email client and the SMTP server. TLS can operate in two modes: explicit and implicit. In explicit mode, the email client and the SMTP server negotiate the encryption method and parameters after establishing a plain text connection. This mode typically uses port 587. In implicit mode, the email client and the SMTP server assume that the connection is encrypted from the start, without any negotiation. This mode typically uses port 465.

SSL (Secure Sockets Layer) is a predecessor of TLS that also encrypts and authenticates data between the email client and the SMTP server. SSL operates in implicit mode only, and uses port 465 by default. SSL is less secure than TLS, but it is still widely used and supported by many email providers.

S/MIME (Secure/Multipurpose Internet Mail Extensions) is a standard that encrypts and signs email messages at the application layer, rather than the transport layer. S/MIME requires the use of digital certificates and public key cryptography to ensure the confidentiality and integrity of email messages. S/MIME is not a valid encryption method for SMTP server configuration, as it does not affect the connection between the email client and the SMTP server.

IPsec (Internet Protocol Security) is a suite of protocols that secures IP packets at the network layer, rather than the application or transport layer. IPsec can encrypt and authenticate data between any two IP endpoints, such as routers, firewalls, or hosts. IPsec is not a valid encryption method for SMTP server configuration, as it does not apply to the specific protocol or port used by SMTP.

References :

Nutanix Database Automation (NCP-DB) Course Details , Section 1.4: NDB Alerts and Notifications

Nutanix Database Automation (NCP-DB) Certification Details , Objective 1.4: Configure NDB Alerts and Notifications

Nutanix Database Automation (NCP-DB) YouTube Playlist , Video 1.4: NDB Alerts and Notifications

[Nutanix Database Automation (NCP-DB) User Guide], Section 1.4: Configure SMTP Server Settings

Nutanix Era (NDB) utilizes DEFAULT_008 SLAs with varying frequencies for snapshots and log backups to achieve different recovery point objectives (RPOs). Here ' s how they compare:

DEFAULT_008 GOLD SLA:  Typically has frequent log backups (e.g., every 15 minutes) and snapshots every few hours. This is designed for critical databases with very low RPOs.

DEFAULT_008 SILVER SLA:  Offers a balance between protection and resource usage. Log backups might occur every hour with snapshots less frequently. This SLA is often suitable for databases requiring a good RPO without being overly resource-intensive.

DEFAULT_008 BRONZE SLA:  Has less frequent log backups (e.g., every few hours) and less frequent snapshots. This is used for databases with less stringent RPO requirements.

DEFAULT_008 BRASS SLA:  This has infrequent log backups and is usually considered the least protective SLA with the longest potential RPO

Reasoning:

Since the requirement is to have at least a 7-day log recovery period, any SLA with more frequent log backups than daily is excessive. The DEFAULT_008 SILVER SLA, with its hourly log backups, easily satisfies this requirement, offering the ability to restore to a point in time within the last hour of the past seven days.

References:

Nutanix Era User Guide/SLA Management:   https://portal.nutanix.com/page/documents/details?targetId=Nutanix-NDB-User-Guide-v2_5:top-sla-management-c.html  ]

Before registering a database server VM to NDB, an administrator must verify that all required software (e.g., database engine, OS dependencies) and configuration settings (e.g., WinRM for Windows, SSH for Linux) are in place. NDB provides a prerequisites script, which can be run on the target VM to check these dependencies automatically. This script ensures compatibility and readiness, reducing registration failures.

Option A (LCM - Lifecycle Manager) is incorrect because LCM is used for cluster upgrades, not VM prerequisite checks.

Option B (Upgrade Software) is incorrect as it applies to updating existing software, not initial dependency verification.

Option C (Prerequisites script) is correct as it is the designated tool for pre-registration validation.

Option D (NCC - Nutanix Cluster Check) is incorrect because NCC checks cluster health, not VM-specific software dependencies.

References

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Preparing Database Server VMs

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 2: Deploy and Configure an NDB Solution