In Nutanix Era, the ability to add a new VLAN or IP Pool is typically associated with the role of an Infrastructure Administrator 1 2 .  This role has the necessary permissions to manage network configurations, including the creation of VLANs and IP Pools 1 2 .  It’s important to note that the exact permissions may vary depending on the specific configuration and policies of your organization 1 2 .

When an administrator wants to manage an additional database on an existing database server VM in NDB, the first step is to identify if the database is already recognized by NDB. The " Unregistered Databases " field or section within the NDB interface lists databases that are present on a registered database server VM but have not yet been registered with NDB. This allows the administrator to discover and register the new database, enabling full management capabilities (e.g., provisioning, cloning, or patching). Once registered, the database will move to the " Registered Databases " section.

Option A (Unregistered Databases) is correct as it is the initial field to check for new, unmanaged databases on the VM.

Option B (Database Server VM) is incorrect because this refers to the VM itself, not the databases it hosts.

Option C (Registered Databases) is incorrect because this lists only databases already managed by NDB, not new ones.

Option D (Database Name in NDB) is incorrect as it is not a specific field but a general reference, lacking a defined location.

The administrator should use the Unregistered Databases section to proceed with registration.

References

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

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

When completing the NDB (Nutanix Database Service) Wizard for initial setup or configuration, certain steps are mandatory to ensure the environment is properly configured, while others are optional based on specific needs. Network Segmentation is an optional step that allows for advanced network isolation and configuration, but it is not required for basic NDB deployment. Mandatory steps include specifying the NDB Cluster Name, selecting a Storage Container, and configuring Services (e.g., database services), as these are essential for NDB to function and manage databases.

Option A (Network Segmentation) is correct as it is an optional feature for advanced networking, not a required step in the wizard.

Option B (NDB Cluster Name) is incorrect because assigning a cluster name is a mandatory step to identify the NDB instance.

Option C (Storage Container) is incorrect because selecting a storage container is required for data storage and protection.

Option D (Services) is incorrect because configuring services (e.g., database engines) is a core requirement for NDB operation.

Note: The question mentions " NDE Wizard, " which is assumed to be a typo for " NDB Wizard " based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Deploying NDB, Section: Completing the NDB Wizard

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 1: Deploy NDB

When a database is de-registered from NDB without removing the associated Time Machine, the Time Machine enters a " Frozen " state. In this state, the Time Machine retains all existing snapshots and protection data but ceases to perform new snapshot captures or log catch-up operations. This allows the administrator to preserve the historical data for potential future use (e.g., auditing or recovery) while halting active management. The Frozen state prevents further modifications until the database is re-registered or the Time Machine is explicitly deleted.

Option A (Ready) is incorrect because " Ready " implies the Time Machine is active and prepared for new operations, which is not the case post-de-registration.

Option B (Frozen) is correct as it reflects the paused protection state after de-registration without removal.

Option C (Paused) is incorrect because " Paused " is not a formal Time Machine state in NDB; " Frozen " is the specific term.

Option D (Active) is incorrect because the Time Machine cannot remain active without an associated registered database.

This state provides flexibility for data retention without ongoing resource use.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Time Machine States

Nutanix Support & Insights, Knowledge Base Article: " Understanding Time Machine States After De-registration "

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

 In the Nutanix Database Automation (NCP-DB) framework, the role that allows an administrator to work with databases and time machines, but not database parameter profiles, is the  Database Administrator (DBA) 1 2 3 . This role provides the necessary permissions to manage databases and time machines, which are essential components of the Nutanix Era solution.  However, it does not grant access to database parameter profiles, which are typically managed by other roles 4 5 .

When consolidating Microsoft SQL Server instances on database server VMs managed by NDB using a medium compute profile, concerns about DB storage capacity can arise due to increased demand. In NDB, the appropriate task to address this is to " Update the Database Server VMs, " which allows the administrator to adjust resource allocations, including storage capacity, for the VMs hosting the databases. This task can be performed within the NDB interface to expand disk space or reconfigure storage settings without altering the compute profile or requiring external tools.

Option A (Update the Database server VMs) is correct as it provides a direct method in NDB to modify VM resources, including storage.

Option B (Expand vDisk in Prism Element) is incorrect because NDB manages database VMs holistically, and storage expansion should be handled through NDB’s Update task rather than Prism Element directly.

Option C (Update the compute profile) is incorrect because compute profiles define CPU and memory, not storage capacity.

Option D (Scale the source database) is incorrect as scaling typically refers to database-level adjustments (e.g., adding nodes), not VM storage expansion.

This approach ensures seamless integration with NDB’s management framework.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Updating Database Server VMs

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

A Time Machine frozen status indicates that the database that was associated with the Time Machine has been de-registered from NDB, but the Time Machine itself has not been deleted. This means that the Time Machine still contains the snapshots and logs of the de-registered database, but it cannot perform any further operations on it. To resume the normal functioning of the Time Machine, the administrator can either re-register the database with NDB, or delete the Time Machine and free up the storage space.

References :  Nutanix Support & Insights , section “Resolving All Alerts for a Time Machine”

The correct answer is A and D because these are the two Time Machine options that are available when creating a database clone in NDB. Point in time allows the user to specify a date and time to create a clone from a specific point in the database history. Snapshot allows the user to select a previously taken snapshot to create a clone from a consistent state of the database. Option B is incorrect because Restore point is not a Time Machine option, but a feature that allows the user to restore a source database to a previous point in time. Option C is incorrect because Backup is not a Time Machine option, but a feature that allows the user to backup a database to a remote location.

References : The following sources provide more information about the Time Machine options and cloning features in NDB:

Nutanix Database Management & Automation (NDMA) course , Module 4: Protecting Databases Using Time Machine, Lesson 4.2: Cloning Databases

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 , Knowledge Objectives, Section 5 - Protect NDB-managed Databases Using Time Machine

Nutanix Database Service (NDB) User Guide , Chapter 6: Protecting Databases Using Time Machine, Section 6.2: Cloning Databases

[Nutanix Support & Insights], NDB Time Machine Under the Hood

The exhibit shows the NDB user management interface with a newly created user named " ndb_test " assigned the " Database Infrastructure Admin " role and sourced as a " Local User. " In NDB, the " Database Infrastructure Admin " role grants specific permissions, allowing the user to manage database-related tasks such as creating, managing, and deleting clones, as well as performing configuration tasks within the NDB environment (e.g., updating settings or managing database servers). However, this role does not extend to higher-level administrative functions like Access Control or Network Profiles, which are reserved for roles with broader administrative privileges (e.g., System Administrator).

Option A (Access Control) is incorrect because managing user access and roles requires a higher privilege level, such as System Administrator, not Database Infrastructure Admin.

Option B (Network Profiles) is incorrect because configuring network profiles is an administrative task outside the Database Infrastructure Admin scope.

Option C (Clones) is correct as the Database Infrastructure Admin role includes permissions to create and manage clones using Time Machine.

Option D (NDB Configuration) is correct as this role allows configuration of database-related settings within NDB, such as registering VMs or adjusting database parameters.

Thus, the " ndb_test " user can perform clone management and NDB configuration tasks.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: User Roles and Permissions

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

In a multi-cluster NDB instance with HA enabled, the NDB architecture includes multiple API server VMs to ensure availability. If more than one API server VM is down after a failure, the administrator should ensure at least one API server VM is online . NDB’s HA design tolerates multiple API server failures as long as one remains operational, and the remaining VMs will recover automatically through the HA failover mechanism. This leverages Nutanix’s distributed architecture and self-healing capabilities to restore full functionality without manual intervention beyond ensuring one VM is running.

Other options are incorrect:

A. Restart all database server VMs as NDB HA only tolerates single API server failure : NDB HA can handle multiple API server failures, and restarting database VMs is unnecessary.

B. Manually distribute connections across remaining clusters : This is not required, as HA manages connections automatically.

C. Call Nutanix support to reset all API server connections : Support is not needed for this scenario; recovery is automated.

Thus, the verified answer is D , reflecting NDB’s HA resilience.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.3: Recovering from Failures.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.4: Recover NDB HA (applicable to v6.10).

Nutanix NDB Administration Guide: " High Availability Recovery Procedures " section.