The recovery plans policy defines the Time Machine data availability across multiple registered clusters in NDB. The recovery plans policy allows the database administrator to specify the source and target clusters, the frequency and retention of the cross-cluster snapshots, and the network and compute profiles for the recovery operations. The recovery plans policy helps to ensure the disaster recovery and business continuity of the NDB-managed databases in case of a cluster failure or outage.

The data access management policy defines the access permissions and roles for the NDB users and groups. The data access management policy allows the database administrator to grant or revoke access to the NDB instance, the database server VMs, the databases, and the database operations. The data access management policy helps to ensure the security and compliance of the NDB-managed databases and users.

The data protection policy defines the backup and restore settings for the NDB-managed databases. The data protection policy allows the database administrator to specify the frequency, retention, and compression of the database snapshots, and the backup location and encryption for the database backups. The data protection policy helps to ensure the backup and recovery of the NDB-managed databases within the same cluster.

The service level agreements policy defines the performance and availability metrics for the NDB-managed databases. The service level agreements policy allows the database administrator to monitor and enforce the database uptime, latency, throughput, and IOPS. The service level agreements policy helps to ensure the quality of service and performance of the NDB-managed databases.

References :

Nutanix Database Management & Automation Training Course , Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slide 9.

Nutanix Database Management & Automation Training Course , Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 8, 12, 16, 20.

Nutanix Database Management & Automation Training Course , Module 6: Nutanix Era Disaster Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 5-7.

Nutanix Era leverages the Nutanix time-efficient snapshots to create the clones 1 .  These database clones are highly space-efficient, consuming near-zero bytes by having only the further writes constituting to its size 1 . Therefore, an administrator would find the total space being used by all Era clones for a specific database under the Cloning widget on the Databases > Clones database summary page. The other options do not specifically provide information about the total space used by all Era clones for a specific database. Therefore, the correct answer is A. Under the Cloning widget on the Databases > Clones database summary page.

When an administrator is asked to add a database to a PostgreSQL instance already managed by NDB, the most appropriate task is to add a new database to the existing source database. In NDB, a PostgreSQL instance refers to a managed database server or cluster, and adding a new database involves creating it within the existing instance using NDB’s database management capabilities. This can be done through the NDB GUI or CLI by selecting the source database and adding the new database, leveraging the current configuration and resources without requiring new VM provisioning.

Option A (Add a new database to a source DB) is correct as it directly addresses adding a database to an existing managed instance.

Option B (Register a new DB VM to add the DB) is incorrect because a new VM registration is unnecessary when the instance is already managed.

Option C (Provision a new DB server VM and add the new DB) is incorrect because provisioning a new VM is overkill for adding a database to an existing instance.

Option D (Update a database clone to add a new DB) is incorrect because clones are read-only copies, not suitable for adding new databases.

This approach ensures efficiency and leverages the existing NDB-managed infrastructure.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Managing Databases in an Instance

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

The image provided shows the " Register Database Server VM " interface in NDB, which includes fields for registering a database server, including options for Windows and SQL Server credentials. When an administrator wants to register a database using a SQL Server User (instead of Windows credentials), the appropriate place to specify this user is in the " Connect to SQL Server Login " section. The interface includes a " User Name " field under this section, which becomes relevant after selecting the option to use a SQL Server User (typically indicated by a radio button or dropdown, though not fully visible in the image). This allows NDB to authenticate and manage the SQL Server instance using database-specific credentials rather than relying solely on Windows Administrator credentials.

Option A (In the Windows Administrator Name field) is incorrect because this field is intended for Windows OS-level credentials, not SQL Server-specific login credentials.

Option B (In the Login field after selecting SQL Server User) is correct as it aligns with the " Connect to SQL Server Login " section in the interface, where the SQL Server User can be specified after the appropriate option is selected.

Option C (Only via the command line registration option) is incorrect because the GUI provides a direct method to specify SQL Server credentials, as shown in the image.

Option D (By modifying the code in the API Equivalent section) is incorrect because the API Equivalent section is for reference and does not allow real-time modification; it’s meant to guide API-based automation, not manual registration.

The image confirms the presence of a " User Name " field under " Connect to SQL Server Login, " supporting the use of a SQL Server User for registration.

References

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

Nutanix Support & Insights, Knowledge Base Article: " Registering SQL Server VMs with NDB Credentials "

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

To automate OS and database patching in a Nutanix NDB environment, the administrator should configure a Maintenance Window. A Maintenance Window in NDB allows the administrator to schedule automated patching tasks (e.g., OS updates and database software updates) during specified time periods, minimizing disruption to production workloads. This feature integrates with software profiles and can be set to run periodically or on-demand, ensuring patches are applied efficiently and consistently across the environment.

Option A (Access Control) is incorrect because Access Control manages user permissions, not automation of patching.

Option B (Pulse) is incorrect because Pulse is a monitoring tool, not a scheduling mechanism for patching.

Option C (Maintenance Window) is correct as it provides the scheduling and automation framework for patching activities.

Option D (SMTP Server) is incorrect because SMTP is for email notifications, not patching automation.

This configuration enhances operational efficiency and reliability.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Scheduling Maintenance Windows

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles

To deploy Microsoft SQL Servers in an Active Directory (AD) environment and select a specific service account to start up the database, the administrator must configure a Windows domain profile in NDB. A Windows domain profile defines the AD integration settings, including the service account credentials (e.g., username and password) that NDB uses to authenticate and manage the SQL Server instances. This configuration ensures the database starts and runs under the specified AD service account, aligning with enterprise security policies.

Option A (Compute profile) is incorrect because a compute profile defines VM resources (CPU, memory), not AD or service account settings.

Option B (Sysprep Windows image) is incorrect because Sysprep is for generalizing Windows images, not configuring AD service accounts.

Option C (Windows domain profile) is correct as it is the specific NDB feature for AD integration and service account management.

Option D (Database parameters) is incorrect because database parameters tune database settings, not AD authentication.

This configuration ensures secure and compliant SQL Server deployment.

References

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Configuring Windows Domain Profiles

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

To view information about all roles and the number of users assigned to each in NDB, the user must belong to the Super Administrator role. This role provides full administrative privileges, including access to the " Users and Roles " section of the NDB GUI, where role assignments and user counts are visible. Lower-tier roles (e.g., Database Infrastructure Administrator, Database Administrator, Infrastructure Administrator) have limited scopes and cannot access this comprehensive role/user overview.

Other options are insufficient:

A. Database Infrastructure Administrator : Manages infrastructure but not role/user details.

B. Database Administrator : Focuses on database operations, not user management.

C. Infrastructure Administrator : Handles cluster resources, not role/user analytics.

Thus, the verified answer is D , requiring the highest privilege level.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.4: Managing Users and Roles.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.3: Manage User Permissions (applicable to v6.10).

Nutanix NDB Administration Guide: " Role-Based Access Control (RBAC) " section, detailing Super Administrator privileges.

When an administrator experiences issues with NDB and Nutanix Support requests a diagnostics bundle, it can be generated from two valid locations. The NDB GUI provides an option under the administration or support section to create and download the bundle, offering a user-friendly interface. Alternatively, the NDB CLI allows generation via specific commands (e.g., era diagnostics collect), providing a scriptable approach. Both methods are supported for troubleshooting and support purposes.

Option A (Prism Central GUI) is incorrect because diagnostics for NDB are managed within NDB interfaces, not Prism Central.

Option B (Prism Element GUI) is incorrect as Prism Element focuses on cluster management, not NDB-specific diagnostics.

Option C (NDB GUI) is correct as it supports bundle generation via the UI.

Option D (NDB CLI) is correct as it supports bundle generation via command-line tools.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Generating Diagnostics Bundle

Nutanix Support & Insights, Knowledge Base Article: " Collecting NDB Diagnostics for Support "

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

Before registering a SQL Server VM with Nutanix Database Service (NDB), the administrator must ensure that the VM is configured to allow NDB to communicate with and manage it. For SQL Server VMs running on Windows, NDB relies on Windows Remote Management (WinRM) to facilitate remote administration, discovery, and management tasks. WinRM is a Microsoft protocol that enables secure communication between the NDB control plane and the Windows-based database server VM. It must be enabled and properly configured (e.g., with HTTP or HTTPS listeners and appropriate firewall rules) to allow NDB to register the VM and perform operations like provisioning, patching, or cloning.

Option A (Secure Shell - SSH) is incorrect because SSH is a protocol primarily used for Linux-based systems, not Windows-based SQL Server VMs. NDB uses WinRM for Windows environments.

Option B (Remote Management - WinRM) is correct as it aligns with NDB’s requirements for managing Windows VMs hosting SQL Server instances.

Option C (Remote Desktop - RDP) is incorrect because RDP is a protocol for interactive desktop access, not for the automated management and communication required by NDB.

Option D (Windows PowerShell) is incorrect as a standalone answer. While PowerShell can leverage WinRM for remote execution, NDB specifically requires WinRM to be enabled as the underlying service, not just PowerShell itself.

To verify WinRM is enabled, the administrator can run winrm quickconfig on the SQL Server VM or check the service status and firewall settings. NDB documentation emphasizes this prerequisite to ensure successful registration and management of SQL Server VMs.

References

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

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

Nutanix Support & Insights, Technical Note: " Preparing Windows VMs for NDB Registration "

NDB can leverage snapshots and transaction logs to refresh a database clone to the latest state of the source database. Snapshots are point-in-time copies of the database that are stored on the Nutanix cluster. Transaction logs are records of the changes made to the database after the snapshot was taken. NDB can use either snapshots or transaction logs, or a combination of both, to refresh a database clone. Cerebro logs and templates are not used for refreshing database clones. Cerebro logs are used for log catch-up operations, which are different from refresh operations. Templates are used for provisioning new databases, not for refreshing existing ones.  References :

Nutanix Database Management & Automation (NDMA) course , Module 4, Lesson 4.3 - Refreshing Clones

Nutanix Support & Insights , Nutanix NDB User Guide v2.5, Clone Database Management