Free and Premium Nutanix NCP-DB Dumps Questions Answers

When patching an Oracle Database Server VM, it's important to ensure that there is sufficient storage space allocated for the Grid home. A minimum of 10GB space is required for this purpose to accommodate the patching process without storage constraints.References: Nutanix Database Automation documentation, particularly in the sections discussing Oracle database server VM management and patching requirements.

NDB supports Linux OS patching for database server VMs. Linux OS patching is performed by using the yum or apt package managers, depending on the Linux distribution. To exclude Kernel patches for the Linux OS, the administrator can disable or exclude the appropriate repositories on the VM prior to patching. This can be done by editing the yum.conf or apt.conf files, or by using the --disablerepo or --exclude options in the yum or apt commands. This way, the administrator can control which patches are applied to the VM without affecting other VMs or requiring additional scripts or reboots.

References:

Nutanix Database Automation (NCP-DB) Course Details, Section 4.2: NDB Linux OS Patching

Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.2: Perform Linux OS Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.2: NDB Linux OS Patching

Nutanix Database Automation (NCP-DB) User Guide, Section 4.5: Patch Linux OS Software

The correct answer is A because the Windows Domain profile is the profile that includes information related to the SQL service startup account and the NDB worker service account. A Windows Domain profile is a collection of settings that define how NDB manages Windows-based database servers and databases. It contains the following information:

The domain name and credentials to join the database server VMs to the domain

The SQL service startup account and password to run the SQL Server service on the database server VMs

The NDB worker service account and password to run the NDB Database Agent service on the database server VMs

The SQL Server authentication mode to use for the databases

By using a Windows Domain profile, the administrator can simplify the database provisioning process by applying the same settings to multiple database server VMs and databases, without having to manually enter them each time. The other options are not correct because they describe different types of profiles that do not include information related to the SQL service startup account and the NDB worker service account. Option B is not correct because the Network profile is a profile that defines the network settings for the database server VMs, such as the IP address, subnet mask, gateway, DNS, and VLAN. Option C is not correct because the Database Parameter profile is a profile that defines the database parameters for the databases, such as the memory, CPU, storage, and performance settings. Option D is not correct because the Software profile is a profile that defines the software settings for the database server VMs and databases, such as the database engine version, edition, and features. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Database Services: Database modernization with Era - Now available

In the Nutanix Era management interface, an administrator should perform an upgrade under the Administration > Maintenance section1. As part of the upgrade process, the Era server is upgraded first, followed by all the Era cluster agents and database server agents in parallel1. The Dashboard displays the current version and an option to upgrade the Era server to a latest version when a new version is available for upgrade1. This ensures that the Nutanix Era environment is always up-to-date with the latest features and security updates1.

To free up space in the NDB-managed container, the administrator needs to identify storage consumption sources. Two key locations in NDB provide actionable insights:

C. Clone Database table: This displays all clone databases, including their Size (current storage usage) and Last Refresh (indicating age or staleness). Clones often consume significant space, and older or unused ones can be deleted to reclaim storage.

D. Snapshot table in Time Machine: This shows snapshots with details like Reclaimable Space (space recoverable by deletion) and Age (how long snapshots have existed). Old or unnecessary snapshots are prime candidates for reclamation.

Why not the other options?

A. NDB Dashboard (Clone Data Age): While it provides a high-level view, it lacks granular details (e.g., size per clone) needed for targeted reclamation.

B. Source Database grid: This shows registered databases’ size and status but doesn’t focus on derivative objects (clones/snapshots) that typically consume more space.

Thus, C and D are the best locations for detailed storage analysis and reclamation research.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Storage and Resource Management, Lesson 6.2: Monitoring and Reclaiming Storage.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.1: Manage Storage Consumption (applicable to v6.10).

Nutanix NDB Administration Guide: "Clone Database Table" and "Time Machine Snapshot Table" sections.

 Nutanix Era provides a unified database operating model that delivers simplicity, performance, availability, and security across private and public clouds1. It standardizes your Oracle database ecosystem by mass patching the databases with one-click simplicity2. This includes the following features:

Automated Patching: Era patching can be automated using REST API/CLI for scheduled patching many Oracle servers in a fleet patching scenario1. This allows for the standardization of your Oracle database ecosystem by mass patching the databases with one-click simplicity2.

Automatic Rollback: Era patching for Oracle databases has automatic rollback if any of the steps in the patching workflow fails1. This ensures that your databases remain secure and functional even if an issue arises during the patching process1.

When creating a Network Profile for NDB HA VMs (e.g., NDB API and Repository VMs) spread across three Nutanix clusters, the required type is PostgreSQL HA instance managed outside NDB. NDB HA relies on a PostgreSQL database for its control plane, and in a multi-cluster HA setup, this PostgreSQL instance must be configured for high availability (e.g., using streaming replication) outside NDB’s management. The Network Profile must support this external HA instance’s networking requirements (e.g., VLANs, IP ranges) to ensure connectivity across clusters.

Other options are incorrect:

A. PostgreSQL HA instance managed in NDB: NDB manages database instances, not its own HA control plane database.

B. PostgreSQL single instance managed in NDB: A single instance lacks HA, unsuitable for multi-cluster.

D. PostgreSQL single instance managed outside NDB: Lacks HA, insufficient for NDB HA VMs.

Thus, the verified answer is C, aligning with NDB HA architecture.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.2: Configuring Multi-Cluster HA.

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

Nutanix NDB Administration Guide: "Network Profile Configuration for HA VMs" section.

When registering a Nutanix cluster with the Nutanix Database Service (NDB), the Prism Element user account used for registration must have sufficient privileges to perform cluster-level operations. The recommended role for this task is Cluster Admin. The Cluster Admin role in Prism Element provides the necessary permissions to manage cluster resources, including storage, networking, and integration with external services like NDB. This role is required because registering a cluster with NDB involves tasks such as establishing connectivity, validating configurations (e.g., Data Services IP), and ensuring that NDB can interact with the cluster’s Controller VMs and storage infrastructure.

The default administrative account in Prism Element (typically "admin") often serves as the initial Cluster Admin user. However, if an administrator needs to remove or replace this default account for NDB operations, a new user with the Cluster Admin role must be created and used instead. Other roles listed have different purposes:

Super Admin: This is not a standard role in Prism Element; it may refer to elevated privileges in other contexts but is not specifically defined for Nutanix cluster registration.

User Admin: This role is limited to managing users and permissions, lacking the broader cluster management capabilities needed for NDB registration.

Backup Admin: This role is specific to backup-related tasks and does not encompass the full scope of cluster management required for NDB integration.

Therefore, the Cluster Admin role is the recommended and verified choice for registering a Nutanix cluster with NDB, ensuring seamless operation and management.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster with NDB.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix cluster in NDB (applicable to v6.10 with no significant role changes documented).

Nutanix Prism Element Guide: "Role-Based Access Control (RBAC)" section, detailing Cluster Admin privileges.

According to the Nutanix Database Automation (NCP-DB) learning documents, when doing an Era software upgrade for a Multi-Cluster enabled installation, the Era Cluster Agent is upgraded first1. This is the first component in a Nutanix Environment Upgrade cycle2. The Era Cluster Agent is crucial for managing and monitoring the health of the Nutanix clusters1. Please refer to the official Nutanix documentation and training materials for more detailed information1.

 In the context of Nutanix Database Automation (NCP-DB), a Super Admin has the authority to apply patch profiles. However, if a patch is marked as deprecated, even if it’s published, it cannot be applied. This is because deprecation is a status that indicates the patch is outdated or has been superseded by a newer version, and thus should not be used1. This behavior ensures that only the most up-to-date and secure patches are applied to the system, maintaining the integrity and security of the database environment1.

When a quality assurance (QA) team notices a significant change between a cloned database currently in use and one used a week ago, and they have an SQL script to verify differences, the NDB administrator needs to provide a clone reflecting the database state from a week ago. The task "Clone database selecting Point in Time data" allows the administrator to select a specific point-in-time snapshot (e.g., from a week ago) using the Time Machine feature. This creates a new clone with the exact data state at that time, enabling the QA team to compare it with the current clone.

Option A (Replicate a selected snapshot) is incorrect because replication is for HA, not creating a usable clone for QA.

Option B (Create a clone database from a snapshot) is incorrect because it does not specify point-in-time selection, limiting flexibility to the latest snapshot.

Option C (Clone database selecting Point in Time data) is correct as it allows precise selection of the week-old data state.

Option D (Perform a Log Catch Up operation) is incorrect because Log Catch Up applies recent logs, not reverting to a past state.

This approach meets the QA team’s need for historical data comparison.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Cloning with Point-in-Time Data

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

In NDB, a Time Machine manages snapshots and log catch-up operations for database protection and recovery. The scenario describes a Time Machine where automatic snapshot and log catch-up activities (both automatic and manual) are halted, and manual snapshots cannot be created. This indicates the Time Machine is in a PAUSED state.

In NDB, the Time Machine states are:

FROZEN: A temporary state during specific operations (e.g., cloning), but it doesn’t halt all activities permanently.

OFFLINE: Indicates the Time Machine is unavailable or not operational, often due to connectivity or configuration issues, but this typically prevents access rather than just halting operations.

PAUSED: Explicitly stops all scheduled and manual snapshot/log activities, often manually triggered by an administrator or due to an error condition (e.g., resource constraints). Operations resume when unpaused.

READY: The normal operational state where snapshots and log catch-ups occur as scheduled.

Given the inability to create manual snapshots alongside halted automatic operations, PAUSED is the most fitting status, as it reflects an intentional or enforced suspension of activities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Time Machines.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Time Machine States (applicable to v6.10).

Nutanix NDB Administration Guide: "Time Machine Statuses and Operations" section.

When a vCenter instance managing multiple clusters, including a Nutanix cluster hosting the NDB service, crashes and a new dedicated vCenter server is deployed, the administrator must update the vCenter settings within NDB to re-establish connectivity and management. The correct action is to navigate to the NDB Administration page, where cluster and vCenter configurations can be updated. This page allows the administrator to re-register the new vCenter instance, ensuring NDB can continue to manage the clusters and database VMs effectively. This approach avoids unnecessary reconfiguration wizards or waiting for automatic syncs.

Option A (Click the Getting Started page and perform the configuration wizard) is incorrect because the Getting Started wizard is for initial setup, not post-crash vCenter updates.

Option B (Update cluster settings from the NDB administration page) is correct as it provides the specific interface to modify vCenter settings after a crash.

Option C (Open the maintenance page in NDB and configure the cluster settings) is incorrect because the maintenance page is for service operations, not vCenter reconfiguration.

Option D (Wait 60 minutes and Prism Central will automatically sync NDB) is incorrect because Prism Central does not automatically sync vCenter settings in NDB; manual updates are required.

This ensures seamless integration with the new vCenter instance.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Updating vCenter Settings

Nutanix Support & Insights, Knowledge Base Article: "Reconfiguring vCenter in NDB After Failure"

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

 In the Nutanix Database Automation (NCP-DB) process, when a database administrator is tasked with creating a new clone of a running SQL database and there are no authorized servers available, the administrator should click the Action icon to authorize one or more database server VMs1. This is because the Nutanix Database Service (NDB) requires authorized servers to perform operations such as cloning1. The authorization process allows the NDB to manage and perform operations on the database server VMs1.

To apply the latest OS security patches on a Windows server managed by NDB, the user should create and apply a Maintenance Plan within the NDB interface. NDB provides a Maintenance Plan feature that allows administrators to schedule and automate OS patching for database server VMs, ensuring patches are applied in a controlled manner without disrupting database operations. This includes validating the patch process, rolling back if needed, and maintaining compliance with security standards. The plan can be configured to target the specific Windows server and include the latest security updates from Microsoft.

Other options are incorrect or insufficient:

A. Reboot the system: A reboot alone does not apply patches; it may only activate previously installed updates.

C. Update the database: This focuses on database software, not OS security patches.

D. Use update functionality directly on the VM: Manual updates bypass NDB’s control, risking inconsistency and potential downtime without proper validation.

Thus, the verified answer is B, leveraging NDB’s centralized maintenance capabilities.

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: "Maintenance Plans for OS Patching" section.

The command era-server > era server set ip=ip_address gateway=gateway_address netmask=ip_netmask nameserver=ns1 ntp_server=ntp1 is used to assign a static IP address to the NDB VM via the era-server CLI. This command requires core network parameters (ip, gateway, and netmask) to configure the VM’s network interface correctly. However, optional parameters like nameserver (DNS server) and ntp_server (Network Time Protocol server) can be omitted if the administrator relies on default or externally configured DNS and NTP settings (e.g., via DHCP or another management system). These optional parameters enhance functionality but are not mandatory for the basic static IP configuration.

Option A (ntp_server) is correct as it is optional and can be configured separately or omitted if NTP is managed externally.

Option B (netmask) is incorrect because the netmask is a required parameter to define the subnet for the IP address.

Option C (gateway) is incorrect because the gateway is a required parameter to specify the network route.

Option D (nameserver) is correct as it is optional and can be omitted if DNS is handled outside NDB.

Note: The typos in the question (gatevay_address, ip_J2etmas^c, narnesetver, ntpl) are assumed to be gateway_address, ip_netmask, nameserver, and ntp1 based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Configuring Network Settings via CLI

Nutanix Support & Insights, Knowledge Base Article: "Configuring Static IP for NDB VM"

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

When performing a SQL Server Restore Source Database operation in Nutanix Database Automation (NCP-DB), an administrator might choose the Restore Location as New Location if they want to restore to a new location and have Era apply Nutanix best practices1. This is because Nutanix Era automates and simplifies database management, allowing the administrator to manage databases at scale, and it applies Nutanix best practices during the restore process1. This ensures optimal performance and reliability of the restored database1.

 NDB HA is a feature that provides high availability and resilience for the NDB service and its components. NDB HA creates a cluster of API server VMs, repository VMs, and HAProxy VMs across multiple Nutanix clusters. Each component has a leader and a set of followers that are synchronized and can take over the leader role in case of a failure. NDB HA also monitors the health and status of the NDB components and performs automatic failover and recovery actions when possible. However, some failure scenarios may require manual intervention from the administrator to restore the NDB service. One such scenario is when more than one API server VM is down. The API server VMs are responsible for handling the requests from the NDB UI and CLI, as well as communicating with the repository VMs and the HAProxy VMs. If more than one API server VM is down, the NDB service may become unavailable or unstable, and the administrator will need to manually restart or redeploy the affected API server VMs. The other options do not require manual interaction for the recovery, as NDB HA can handle them automatically. If one repository VM is down, NDB HA will fail over to another repository VM that has the latest data. If more than one HAProxy VM is down, NDB HA will route the traffic to the remaining HAProxy VMs. If the NDB server process is down, NDB HA will restart the process or fail over to another API server VM. 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 Support & Insights, RA-2035: Nutanix Database Service High Availability, Section: NDB HA Failure Scenarios and Recovery Actions

 Nutanix Era can be upgraded using the Offline Upgrade and One-click Upgrade methods. The Offline Upgrade method involves manually downloading the software update and applying it to the Era instance. The One-click Upgrade method allows you to upgrade Era directly from the Era management console with a single click, provided that the Era instance has internet connectivity and can reach the Nutanix software update portal1.

A "dark site" refers to an environment with no internet connectivity, requiring manual processes for software updates. For Nutanix Database Service (NDB) in such a setup, updates cannot be downloaded automatically from the internet. The correct procedure is to:

Download the upgrade bundle: Access the Nutanix Support Portal from a system with internet access and download the NDB upgrade bundle specific to the version (e.g., v6.10 or later).

Manually upload it to the NDB server: Transfer the bundle to the NDB server (e.g., via SCP or USB) and upload it through the NDB interface under the "Software Updates" or "Maintenance" section.

Other options are incorrect in a dark site context:

B: The "Administrator > Maintenance" section allows initiating updates, but it cannot download files without internet access.

C: Changing the network to access defeats the dark site’s isolation and is impractical.

D: Uploading to Prism Element > Images is for VM images or other Prism-specific content, not NDB software updates.

Thus, the verified answer is A, aligning with Nutanix’s documented process for dark site updates.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Updating NDB in Dark Sites.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.3: Perform NDB Updates (applicable to v6.10).

Nutanix NDB Administration Guide: "Updating NDB in a Dark Site Environment" section.

In NDB, publishing a software profile update for Microsoft SQL Server makes it available for broader use within the NDB environment. When an administrator creates and publishes an updated software profile (e.g., with a new SQL Server patch or version), this action allows all authorized NDB users to leverage that profile to patch or update the database software on their managed VMs. This is a key feature of NDB’s software profile management, enabling centralized control and distribution of standardized database configurations.

Option A is correct because publishing a profile democratizes access, allowing all users to apply the update to their database VMs, aligning with NDB’s collaborative administration model.

Option B is incorrect because it suggests the profile patches itself, which is not the intent; publishing enables usage, not self-application.

Option C is incorrect because publishing does not automatically deprecate older profiles; deprecation is a separate administrative decision.

Option D is incorrect because publishing facilitates patching, not stalls it.

This process enhances efficiency and consistency in managing SQL Server updates across an organization.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Creating and Publishing Software Profiles

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

According to the Nutanix Database Automation (NCP-DB) learning documents, Era provides out-of-band patching of databases to eliminate database configuration sprawl1. The two Oracle software components that Era patches are:

A. Grid home2 B. Oracle home2

These components are crucial for the operation of Oracle databases and keeping them updated ensures data security and efficient validation of critical database updates1. Please refer to the official Nutanix documentation and training materials for more detailed information2.

The size of a database Time Machine in Nutanix Era is defined by the size of all snapshots and/or transaction logs maintained by Era1. The Time Machine leverages Nutanix’s efficient snapshot technology to capture the state of the database at different points in time1. These snapshots, along with transaction logs that record changes between snapshots, constitute the data maintained by the Time Machine1. Therefore, the size of the Time Machine is determined by the total size of these snapshots and transaction logs1.

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

When upgrading NDB and the upgrade includes updates to out-of-the-box (OOB) software profiles (e.g., predefined profiles for database software like PostgreSQL, SQL Server, etc.), NDB manages older versions of these profiles based on their usage. If the older OOB software profiles are not actively in use by any database VMs, NDB automatically deletes all versions of those profiles from its metadata and associated protection domains during the upgrade process. This cleanup mechanism helps maintain a lean and efficient system by removing obsolete profiles that are no longer relevant or required.

Option A is incorrect because the condition about Time Machines and snapshots in the last 24 hours is not a documented criterion for profile deletion during an NDB upgrade.

Option B is correct as it reflects NDB’s behavior of removing unused OOB software profiles during upgrades to optimize resource usage and metadata.

Option C is incorrect because shutting down database VMs does not trigger automatic deletion of software profiles; the key factor is whether the profiles are in use.

Option D is incorrect because the concept of a "base version" is not relevant here; deletion depends solely on whether the profiles are unused, not on versioning specifics.

This behavior ensures that only active and necessary profiles persist post-upgrade, streamlining administration.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Upgrading NDB, Section: Handling Software Profile Updates

Nutanix Support & Insights, Technical Note: "NDB Upgrade Process and Software Profile Management"

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

When registering a Nutanix cluster with NDB, a manual storage mapping between the remote container and the NDB provisioning container is required if the NDB Server container and NDB Provisioning container are separate. This separation occurs when the storage containers used by the NDB server (for its own operations) and the provisioning container (for database VMs) are distinct, either due to multi-cluster setups or custom configurations. Manual mapping ensures NDB can correctly allocate storage resources and manage database provisioning across these containers.

Other conditions do not necessitate manual mapping:

B. Disaster Recovery Network Segmentation is enabled on the cluster: This affects networking, not storage mapping.

C. Nutanix Database Service High Availability is enabled on the cluster: HA configurations handle replication, not container mapping.

D. DB VMs are stored in the NDB Server or NDB Provisioning container: This is a typical setup and does not require manual mapping unless containers differ.

Thus, the verified answer is A, addressing storage container separation.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix Cluster (applicable to v6.10).

Nutanix NDB Administration Guide: "Storage Container Mapping" section.

The correct answer is B because the Time Machine feature of NDB collects logs and snapshots from databases and stores them in a distributed file system. The Time Machine enables the administrator to protect, clone, and restore databases using the SLA policies and the NDB UI or API. The Time Machine also manages the replication of database snapshots in an NDB multicluster environment. The other options are not correct because they describe different features or functions of NDB. Option A is not correct because Database Restore is an operation that uses the Time Machine to restore a source database or a clone to a previous point in time. Option C is not correct because SLA is a policy that defines the frequency and retention of database snapshots and logs. Option D is not correct because One-click Patching is a feature that allows the administrator to test, publish, and apply database patches using the NDB UI or API. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Support & Insights

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

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.

 According to the Nutanix Database Automation (NCP-DB) learning documents, when dealing with an Availability Group (AG) database, the database should be registered as an Availability database1. This is because the AG database is hosted on replicas with different named instances, and registering it as an Availability database allows for Copy Data Management operations to be performed across all instances. This is particularly important when services such as the Analytics service running on SQLAGN3\DW require real-time data1.

Ports 3205 and 3260 are important when working with Era because they must be open on the Era server and all Controller VMs (CVMs) to facilitate iSCSI connections1. Specifically, port 3205 is used for iSCSI redirection2. Please be careful of routing iSCSI traffic, as it could impact performance2.

The correct answer is D because it meets the requirements of maintaining five days of time-travel capability to any second and an additional seven days of discrete recovery at a daily interval. Continuous log retention allows the administrator to restore the database to any point in time within the specified number of days, while snapshot retention allows the administrator to restore the database to a specific point in time at a fixed interval. Therefore, by setting the daily snapshot retention to 7 days, the administrator can ensure that there is a discrete recovery point for each day of the week. By setting the continuous log retention to 5 days, the administrator can ensure that there is a time-travel capability to any second within the last five days. The other options do not meet the requirements because they either have less than five days of continuous log retention or less than seven days of snapshot retention. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Certified Professional - Database Automation (NCP-DB) datasheet

The correct answer is C because it follows the recommended procedure for applying a CU to a SQL Server Software Profile in NDB. By applying the patch to the profile VM, the administrator ensures that the CU is compatible with the existing Software Profile settings and configuration. By creating a new Software Profile version, the administrator preserves the previous version of the Software Profile for rollback purposes and allows the new version to be tested and published. Option A is incorrect because it deletes the existing Software Profile, which may cause data loss and prevent rollback. Option B is incorrect because it does not apply the patch to the profile VM, which may result in errors or inconsistencies in the Software Profile. Option D is incorrect because it creates a new Software Profile instead of a new version, which may cause confusion and duplication.

References: The following sources provide more information about the Software Profile management and patching in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 5: Patching Databases Using NDB, Lesson 5.2: Creating and Modifying Software Profiles

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 4 - Operate and Maintain an NDB Environment

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.2: Creating and Modifying Software Profiles

Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.3: Testing and Publishing Database Patches

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

 NDB supports two modes of log backup management for Microsoft SQL databases: NDB-managed and 3rd-party managed. In the NDB-managed mode, NDB takes full control of the log backups and stores them in the Cerebro log location. In the 3rd-party managed mode, NDB allows the use of external backup tools to backup the logs from the database log destination. However, NDB still needs to capture the logs for its own operations, such as point-in-time recovery, clone refresh, and log catch-up. Therefore, NDB will periodically scan the database log destination and copy the logs to the Cerebro log location. This process requires that the log catch-up begins before the logs get backed up by the 3rd-party tool, otherwise NDB will miss some logs and the operations will fail. If the 3rd-party tool grants exclusive access to the logs, then NDB will not be able to capture them at all, and the operations will not be supported. References:

Nutanix Database Management & Automation (NDMA) course, Module 5, Lesson 5.2 - Log Backup Management

Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Log Backup Management

An administrator needs to provision multiple database clones from the same source database for different purposes (e.g., QA and Test/Development) while avoiding resource starvation by differentiating VM resources for each department. The most efficient way to achieve this is by creating multiple Compute profiles in NDB. Compute profiles define CPU, memory, and other resource allocations for VMs, allowing the administrator to tailor resource limits (e.g., higher resources for QA, lower for Development) and apply them during clone provisioning. This approach is built into NDB, ensuring consistent resource management without manual adjustments.

Option A (Create multiple Compute profiles) is correct as it provides a scalable and efficient way to allocate resources per department.

Option B (Leverage NCM Self Service to deploy database clones) is incorrect because Nutanix Cluster Management (NCM) Self Service is for end-user provisioning, not resource differentiation.

Option C (Use a VM Template for each department) is incorrect because VM templates are less flexible and not natively integrated with NDB clone provisioning.

Option D (Generate a playbook to resize database VMs when released) is incorrect because playbooks are for automation, not initial resource allocation, and resizing post-provisioning is less efficient.

This method optimizes resource use across departments.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Configuring Compute Profiles

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

For supported Linux-based database VMs managed by NDB, keeping software profiles updated for provisioning new database VMs requires a structured process. The administrator must first apply the necessary patches (e.g., OS updates and database engine patches) to an existing database VM for each supported database engine (e.g., PostgreSQL, Oracle). Then, a new software profile version must be created using the updated VM as the source. This new version captures the patched configuration and can be used to provision new VMs, ensuring they are deployed with the latest updates.

Option A (Create a Maintenance window under the policy menu, then under Database VM, add the database VMs to that maintenance window and check both Database and Operating system updates) is incorrect because a Maintenance Window schedules updates for existing VMs, not for updating software profiles for new provisions.

Option B (Apply patches to a database VM for each supported database engine, then create a new software profile version for each supported database VM for each one using the updated database VM as the source) is correct as it follows the standard NDB process for profile updates.

Option C (Associate the newly provisioned database VMs with a maintenance window so they are kept updated) is incorrect because this applies to ongoing maintenance, not initial profile updates for provisioning.

Option D (In the Administrator menu drop down, go the Maintenance tab and choose Download Upgrade) is incorrect because downloading upgrades is part of the patch process, not the profile creation step.

This method ensures new VMs are provisioned with the latest software configurations.

References

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

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

When an administrator encounters an error provisioning a new Oracle database VM in NDB, the best action to provide Nutanix support with the most complete picture is to select the failed job in the Operations menu and choose Generate Bundle from the lower right. The "Generate Bundle" option creates a comprehensive diagnostic package, including logs, configuration details, and error traces specific to the failed operation. This bundle is ideal for troubleshooting and can be uploaded to Nutanix Support for analysis.

Other options are less comprehensive:

A. From the Administration section of NDB, go to the Diagnostics section and choose Generate Bundle: This generates a general diagnostic bundle, not specific to the failed job.

B. Copy the error message from the Operations menu: This provides limited context compared to a full bundle.

D. Take a screenshot of the error in the Operations menu: A screenshot lacks detailed logs and system data needed for support.

Thus, the verified answer is C, ensuring detailed support data.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.4: Troubleshooting and Support.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.4: Generate Support Bundles (applicable to v6.10).

Nutanix NDB Administration Guide: "Generating Support Bundles for Failed Operations" section.

Nutanix Database Service (NDB) uses software profiles for database patching to keep your databases secure and optimized1. When a new database is provisioned, it will be on your current environment’s database version to maintain consistency and stop version sprawl1. 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 VM1.

When setting up a Time Machine for a newly-provisioned database in NDB, the GUI allows the administrator to configure the frequency of snapshots for data protection. The maximum number of snapshots per day that can be configured in the NDB GUI is 6. This limit ensures a balance between data granularity (for point-in-time recovery) and storage overhead, preventing excessive resource consumption. The administrator can schedule these snapshots at regular intervals (e.g., every 4 hours) within the Time Machine configuration wizard.

Other options are incorrect based on NDB’s design:

A. 4: This is below the maximum supported limit.

C. 8: Exceeds the GUI-configurable maximum.

D. 12: Far exceeds the limit, suggesting manual or unsupported customization.

Thus, the verified answer is B, aligning with NDB’s snapshot scheduling constraints.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.1: Configuring Time Machine.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.1: Configure Time Machine Settings (applicable to v6.10).

Nutanix NDB Administration Guide: "Time Machine Snapshot Scheduling" section.

 In Nutanix Database Automation (NCP-DB), the Database Parameters profile is used to manage database-specific settings, including the maximum number of database connections. This profile would be the appropriate choice when an administrator needs to change these settings during the cloning workflow1.

 The correct answer is B and D because they are the two restore options that can be used to restore an Oracle database to the prior day’s state using Nutanix Era. A snapshot is a point-in-time copy of a database that is stored in the Era Time Machine, which is a distributed file system that collects logs and snapshots from databases. A point in time is a specific moment in time within the retention period of the SLA policy that is applied to the database. By using either of these options, the administrator can select the snapshot or the point in time that corresponds to the prior day’s state and restore the database from it. The other options are not correct because they are not restore options that are available in Nutanix Era. Option A is not correct because Most Recent Time Available is not a restore option, but a clone option that creates a clone of the database from the most recent snapshot or log backup. Option C is not correct because Tail Logs Backup is not a restore option, but a backup option that captures the transaction logs of the database that have not been backed up by the SLA policy. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, [Nutanix Database Services: Database modernization with Era - Now available]

In the context of Nutanix Database Automation (NCP-DB), when provisioning a new Oracle SIHA DB & VM, if only ASMFD is available in the ASM Driver drop-down, it indicates that ASMLIB is not included in the current software profile. To provision the requested SIHA DB and DB VM with ASMLIB, it’s essential to update the software profile to include the ASMLIB driver. This action will enable ASMLIB as an option in the ASM Driver drop-down during the provisioning workflow.

References:

Nutanix Database Automation (NCP-DB) Course Details, Section 2.3: Provisioning Oracle Databases

Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.3: Provision Oracle Databases

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.3: Provisioning Oracle Databases

[Nutanix Database Automation (NCP-DB) User Guide], Section 2.3: Provision Oracle Databases

To release PostgreSQL HA instances using a dedicated subnet in Nutanix Database Service (NDB), the administrator must create a network profile that defines the subnet and its associated VLAN. Before creating this network profile, it is mandatory to add a VLAN to the NDB Networks configuration. This VLAN ensures that the dedicated subnet is recognized and manageable within NDB, allowing the HA instances to be provisioned with isolated network connectivity. The VLAN must be configured in the NDB Networks page to be available for selection during network profile creation.

Option A (The subnet in Prism Element must be IPAM configured) is incorrect because IP Address Management (IPAM) configuration in Prism Element is optional and not a mandatory prerequisite for creating a network profile in NDB.

Option B (The DB VMs must be registered first) is incorrect because VM registration is a subsequent step, not a prerequisite for network profile creation.

Option C (A VLAN must be added to NDB networks) is correct as it is a required step to define the network infrastructure before creating the profile.

Option D (Configure Network Segmentation) is incorrect because network segmentation is an advanced feature and not mandatory for basic network profile setup.

This ensures the dedicated subnet is properly integrated into NDB for HA provisioning.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring Network Profiles

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

The NDB user interface supports multiple languages, including English, Chinese, and Japanese. You can change the language preference in the NDB settings page. The NDB user interface does not support Korean, French, or German languages at this time. References:

Nutanix Database Management & Automation Training Course, Module 1: Introduction to Nutanix Era, Lesson 1: Nutanix Era Overview, Slide 7: NDB User Interface

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 1: Describe NDB Concepts, Objective 1.6: Languages

Time Machine data access is a feature of Nutanix Database Service (NDB) that allows you to access a point-in-time snapshot of a database without restoring it. To use this feature, you need to create a Data Access Management (DAM) policy that defines the access mode, the source database, the destination cluster, and the storage container mapping. The storage container mapping is needed when the source database and the NDB Server containers are different, because NDB needs to know where to store the metadata and the clone of the source database. If the source database and the NDB Server containers are the same, then NDB will use the same container for both the metadata and the clone. References:

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

Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 9, Objective 5.6

Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.2 - Data Access Management

When downloading a list of alerts from NDB, the available file format is csv (Comma-Separated Values). NDB provides this format to export alert data (e.g., alert ID, timestamp, severity, description) in a structured, machine-readable way that can be easily imported into spreadsheet applications like Microsoft Excel or analyzed programmatically. This aligns with NDB’s focus on operational efficiency and data portability.

Other options are not supported:

A. xlsx: Excel’s native format is not offered by NDB for alert exports.

C. xml: Not a supported format for alert downloads in NDB.

D. pdf: Used for reports, not alert list exports.

Thus, the verified answer is B, reflecting NDB’s export capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.2: Managing Alerts.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.2: Manage Alerts (applicable to v6.10).

Nutanix NDB Administration Guide: "Exporting Alerts" section, specifying CSV format.

During an NDB upgrade, the upgrade process follows a specific order to maintain stability and HA. The Leader NDB API Server is upgraded first. This server coordinates API requests and ensures the control plane remains operational. Upgrading the leader first minimizes disruption, as subsequent components (e.g., other API servers, HAProxy) rely on its leadership role. Once the leader is upgraded, the remaining NDB HA control plane VMs (e.g., follower API servers, HAProxy) are updated in sequence.

Other options are incorrect:

A. NDB Server: Refers to the main NDB instance, not upgraded first.

C. Leader HAProxy: Upgraded after API servers to maintain load balancing.

D. NDB Agent VMs: Upgraded last, as they are client-side components.

Thus, the verified answer is B, reflecting the upgrade sequence.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Updating NDB.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.3: Perform NDB Updates (applicable to v6.10).

Nutanix NDB Administration Guide: "NDB Upgrade Process" section.

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) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.5: Manage NDB Security (applicable to v6.10).

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

To leverage the Oracle restore feature within Nutanix Database Service (NDB) for a Real Application Clusters (RAC) database, the administrator must ensure that the database is registered with NDB prior to initiating the restoration operation. Registration allows NDB to recognize the RAC database, manage its metadata, and perform operations like restore using Time Machine snapshots or backups. Without registration, NDB cannot access the necessary configuration details or protection data, rendering the restore feature unavailable.

Option A (Ensure the database is in a Down state) is incorrect because the database state (Up or Down) is not a prerequisite for initiating a restore; the process handles state transitions.

Option B (Ensure the database is registered with NDB) is correct as registration is the foundational requirement for NDB to manage and restore the RAC database.

Option C (Ensure the database is in an Up state) is incorrect because an Up state is not required; restore can proceed regardless of the current state.

Option D (Ensure more than one node of the RAC is reachable) is incorrect because while RAC node availability is important for HA, it is not a mandatory prerequisite for the restore operation itself.

This ensures the restore process can proceed with the necessary NDB oversight.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring RAC Databases

Nutanix Support & Insights, Knowledge Base Article: "Preparing Oracle RAC for Restore in NDB"

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

 An Infrastructure Administrator is a role in NDB that has the permission to manage network and storage resources, such as VLANs, IP Pools, and Storage Containers. This role is suitable for the engineer who needs to add new VLANs or IP Pools in NDB. The other roles have either more or less privileges than required for this task. A Database Administrator can manage databases and database server VMs, but not network and storage resources. A Super Administrator can manage all aspects of NDB, but this is more than the least-privilege access needed. A Database Infrastructure Administrator can manage both databases and network and storage resources, but this is also more than the least-privilege access needed.

References: Nutanix Support & Insights, section “NDB Roles and Permissions”

When registering a new Nutanix Cluster with Era, the Era Agent is installed on the target Nutanix cluster via the Register Nutanix Cluster workflow1. This agent is crucial for the functioning of the Nutanix Database Service (NDB) as it helps in managing and optimizing database workloads2. It also enables the application of procedural concepts to add Nutanix clusters to NDB2.

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

In Nutanix Database Service (NDB), patching Oracle database engines requires the "Update" button to be available on the database server VM’s management interface. If this button is missing, it typically indicates a configuration issue preventing NDB from performing the patching operation. The most common and critical reason is that the operating system (OS) credentials for the database server VM have not been set or registered with NDB. These credentials are necessary for NDB to authenticate and execute patching tasks on the VM, such as accessing the Oracle software and applying updates via a software profile.

Option A is correct because missing OS credentials prevent NDB from establishing the required connection to the VM, disabling the Update button.

Option B (Database parameters are missing) is incorrect because while database parameters are important for configuration, they do not directly control the visibility of the Update button for patching.

Option C (Oracle DB engines cannot be patched) is incorrect as NDB explicitly supports patching Oracle databases when properly configured.

Option D (Software profile is not published) is incorrect because an unpublished software profile might limit availability to users, but the Update button’s presence relies on VM connectivity, not profile publication status.

To resolve this, the administrator must register valid OS credentials for the VM in NDB, enabling the patching functionality.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Patching Database Engines

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Missing Update Button in NDB"

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

 The correct answer is C because the NDB Database Agent service is responsible for scheduling and monitoring the NDB-related operations, such as provisioning, patching, cloning, and restoring databases. The NDB Database Agent service is deployed on the NDB server and on each of the database server VMs provisioned by NDB. It contains the tools required to perform each task and communicates with the NDB server through the NDB API. The other options are not correct because they describe different components or functions of the NDB solution. Option A is not correct because the transaction logs are not stored by the NDB Database Agent service, but by the NDB Time Machine service, which is a distributed file system that stores the database snapshots and logs. Option B is not correct because the source databases are not hosted by the NDB Database Agent service, but by the database server VMs, which are virtual machines that contain an instance of the database engine software and the database files. Option D is not correct because the NDB Database Agent service does not contain an instance of the database engine software, but only the tools required to perform the NDB-related operations. The database engine software is installed on the database server VMs, which are provisioned by NDB using the profiles defined by the administrator. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Support & Insights

For deploying Nutanix Database Service (NDB), the required file type to download from the Nutanix Portal is an OVA (Open Virtual Appliance) file. The OVA format is a standardized package that includes a pre-configured virtual machine image, including the NDB software, which can be imported into supported hypervisors (e.g., VMware ESXi or Nutanix AHV). This simplifies the deployment process by providing a ready-to-use VM template with all necessary components.

Option A (ZIP) is incorrect as ZIP files are generic archives, not deployment-specific formats for NDB.

Option B (QCOW2) is incorrect because QCOW2 is a disk image format primarily used with KVM/QEMU, not the standard for NDB deployment.

Option C (OVA) is correct as it is the official file type provided by Nutanix for NDB deployment.

Option D (TAR) is incorrect as TAR files are used for archiving, not as a deployment package for NDB.

Administrators should download the OVA from the Nutanix Portal and follow the deployment guide.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Deploying NDB, Section: Downloading and Deploying the OVA

Nutanix Support & Insights, Knowledge Base Article: "NDB Deployment Prerequisites"

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

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.

 In Nutanix Era, a Volume Group is the recommended storage provisioning method for a large I/O-intensive database that doesn’t support a multi-disk layout1. A Volume Group in Nutanix Era is a collection of disks that can be managed as a single entity, providing a way to aggregate the storage capacity of multiple disks into a larger storage unit1. This allows for better performance optimization as it enables the database to leverage the combined I/O capabilities of all the disks in the group1. It’s important to note that while other options like Load Balancing, Storage Spaces, and vDisk based provisioning can also be used in certain scenarios, a Volume Group is specifically designed for situations where a single, high-performance storage unit is required1.

The Era One-Click Provisioning service in Nutanix Database Automation (NCP-DB) simplifies and automates database administration. It brings one-click simplicity to database provisioning and life-cycle management. This service enables database administrators to provision, clone, and refresh the database clones to any point in time1. Specifically, it enables the creation of space-efficient clones and zero-byte database clones1. This is part of Era’s copy data management service, which includes components like Time Machine, one-click cloning and refresh, and one-click backup21.

An administrator can configure a custom SSL certificate for Era through the Era User Interface (UI)1. This can be done by logging into the Nutanix Console and selecting SSL Certificates from the drop-down list inside the gear icon23. In the SSL Certificate dialog box, the administrator can click Replace Certificate, then select the Import Key and Certificate radio button23. This process ensures secure communication within the Nutanix Era environment4.

HA drivers are software components that enable high availability features for database VMs, such as failover, fencing, and heartbeat. HA drivers can be upgraded using the Life Cycle Management (LCM) feature of Nutanix Prism. LCM can detect the available updates for HA drivers and apply them to the database VMs in a non-disruptive manner. LCM can also perform health checks and pre-upgrade validations to ensure the successful completion of the upgrade process. One-click software upgrade is a feature of Nutanix Era that allows you to upgrade the Era software itself, not the HA drivers. Database VM OS patching is a feature of Nutanix Era that allows you to patch the operating system of the database VMs, not the HA drivers. Database software patching is a feature of Nutanix Era that allows you to patch the database software of the database VMs, not the HA drivers. References:

Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 3: Configuring NDB High Availability, Slide 9: HA Driver Upgrade

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.4: Upgrade databases

In the context of Nutanix Database Automation (NCP-DB), when there are insufficient resources on a development cluster, the administrator can adjust the Compute and Database Parameters profiles to make the copy fit within the available resources1. The Compute profile includes settings related to CPU and memory resources, which can be adjusted to fit within the available resources. The Database Parameters profile includes settings that control the behavior and resource usage of the database, which can also be adjusted to optimize resource usage1.

The Era copy data management service includes several components, one of which is the Time Machine. The Time Machine is responsible for collecting logs and snapshots from the database123. This functionality allows for granular clone and refresh operations, making it a crucial part of the Nutanix Era’s database as a service (DBaaS) solution1.

For enabling Multi-Cluster management on an Era installation, the hypervisor version must be supported and port 9440 must be open between the Era VM and clusters. This ensures that the Era VM can communicate with the clusters for management tasks1.

The provided exhibit shows the NDB Time Machine restore interface for October 31, 2024, with a Point-in-Time (PIT) restore option selected at 21:50. However, the restore option is unavailable, as indicated by the question. The exhibit includes a warning: "Logs to Backup: The database may contain additional logs. Backup any remaining logs before restore or they will be lost." This suggests that PIT restore requires continuous log retention, and if logs since the last snapshot (at 01:10:00) are not backed up, the restore to 21:50 cannot proceed. Running the "Logs to Backup" operation ensures all transaction logs are captured, enabling PIT restore by allowing NDB to replay logs to the desired point.

Option A (Point in time must be within the most recent range) is incorrect because the selected 21:50 is within the log retention period shown (up to the current time), but logs need to be backed up.

Option B (Selected Restore time is not available) is incorrect because 21:50 is a valid time within the log range, but log backup is the issue.

Option C (Change to snapshot option) is incorrect because switching to a snapshot limits the restore to the snapshot time (01:10:00), not 21:50.

Option D (Logs to Backup must be run first) is correct as the warning indicates that backing up remaining logs is necessary for PIT restore.

After running the backup, the administrator can proceed with the PIT restore.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Point-in-Time Restore Requirements

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting PIT Restore Issues in NDB"

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

In a high availability (HA) Nutanix Database Service (NDB) environment, custom SSL certificates are used to secure communication between clients (e.g., NDB GUI, API calls) and the NDB control plane. The HA Proxy VMs serve as the entry point for all external traffic, load balancing requests across the NDB API server VMs and providing secure SSL termination. When configuring custom SSL certificates, they must be updated on all HA Proxy VMs to ensure consistent and secure communication across the HA environment. Updating only a subset of servers or other components (like API or Repository VMs) would lead to inconsistencies or SSL handshake failures.

Option A (All API server VMs) is incorrect because the API servers do not directly handle external SSL termination; this is managed by the HA Proxy layer.

Option B (All HA Proxy VMs) is correct as these VMs are responsible for SSL termination and load balancing in an HA setup, requiring the custom certificates to be applied uniformly.

Option C (The API and Repository VMs running on the primary cluster) is incorrect because Repository VMs do not handle client-facing traffic, and the API servers rely on HA Proxy for SSL handling.

Option D (The primary API, Repository, and HA Proxy servers) is incorrect because it implies a single "primary" server focus, whereas in an HA setup, all HA Proxy VMs (not just a primary one) must be updated.

This aligns with NDB’s HA architecture, where HA Proxy VMs are the critical components for SSL certificate management.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring High Availability and SSL Certificates

Nutanix Support & Insights, Knowledge Base Article: "Configuring Custom SSL Certificates in NDB HA Environments"

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

To enable iSCSI connections between the Nutanix Database Service (NDB) server, Controller VMs (CVMs), and Prism Element, a Data Services IP must be configured in Prism Element. The Data Services IP acts as a cluster-wide address that facilitates iSCSI target discovery and connectivity. It is used by Nutanix Volumes (a block storage service) to present storage to external clients or services, such as the NDB server, via the iSCSI protocol. This IP ensures that iSCSI traffic is routed correctly and remains available even if a CVM fails, as ownership of the Data Services IP can move to another CVM in the cluster.

Configuring the Data Services IP is a prerequisite for integrating NDB with a Nutanix cluster, as NDB relies on iSCSI to manage database storage operations like provisioning and cloning. Without this configuration, the NDB server cannot establish the necessary connections to the CVMs for database-related tasks. Options like Virtual IP, Secondary DNS IP, and Backplane IP are not relevant in this context:

Virtual IP: This is typically associated with high-availability setups for applications, not iSCSI connectivity.

Secondary DNS IP: This pertains to network resolution, not storage connectivity.

Backplane IP: This is an internal network IP for cluster communication, not for external iSCSI access.

Thus, the correct and verified answer is the Data Services IP.

Official Nutanix Database Automation References

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

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution (applicable to v6.10 as foundational concepts remain consistent).

Nutanix Support & Insights Portal: "Configuring iSCSI Data Services IP for Nutanix Volumes" (general Volumes configuration applicable to NDB).

The log frequency in the Era IJI for log catchup operation can be configured to as low as 5 minutes. This allows the system to capture changes to the database at a high frequency, enabling more precise point-in-time recovery options. However, it’s important to note that a higher frequency of log catchup operations can lead to increased system load. Therefore, the optimal frequency may vary depending on the specific requirements and capabilities of your system12. Please refer to the Nutanix Database Automation (NCP-DB) Learning documents for more detailed information.

Before registering a SQL Server Single Node Database Server VM with NDB, it is necessary that the login account provided for this task must be a member of the sysadmin role. This ensures the necessary permissions are in place for managing and administering the SQL Server instance.References: Nutanix Database Automation documentation, under SQL Server database registration and permission requirements.

To create a software profile version for a newly-released Oracle ISc patch, an administrator should follow these steps:

Download the required patch from MyOracle Support1. This is because Oracle patches are typically available from MyOracle Support, not Microsoft Support.

Apply the patch to the Oracle Home/Grid Home on a cloned VM of the gold image using OPatchAuto1. OPatchAuto is a utility provided by Oracle that automates the process of applying patches to a database.

Ensure success of patch application1. It’s important to verify that the patch has been applied successfully to avoid any issues down the line.

Create a new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era GUI1. This step is necessary to ensure that the new patch is included in the software profile.

Mark the original patch profile as hidden1. This step is optional but can be useful for keeping the software profile clean and organized.

Please note that these answers are based on the information available as of my last update in 2021 and may need to be verified with the most recent Nutanix Database Automation (NCP-DB) documentation or resources.

When using the "Patch OS now" feature in NDB to apply updates to a Red Hat-based operating system, the administrator can limit updates to security patches only by leveraging the Advanced Options. Under the "Custom commands" section of the operating system patching command window, entering yum update --security instructs the package manager to install only security-related updates. This ensures the system remains secure without applying all available updates, which could introduce instability.

Other options are incorrect or incomplete:

A. Point the database VM to a custom patch repository and enter yum update --security command: This requires manual intervention outside NDB’s patching framework.

B. Check Advanced Options and under Pre-post commands, enter yum update security in the pre-operating system patching command window: Pre-post commands are for pre/post actions, not the main patching process, and the syntax lacks the --security flag.

C. Point the database VM to a custom patch repository before using the Patch OS now feature: This sets up a repository but doesn’t specify security-only updates within NDB’s interface.

Thus, the verified answer is D, aligning with NDB’s patching customization.

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: "Patch OS Now with Custom Commands" section.

When an administrator creates a new SQL Server software profile version to apply the latest cumulative update, they should update the software profile version and set the status to Published1. This makes the new profile version available to all users. NDB will show available updates for any database server using the software profile as soon as the new profile version is published1.

 According to the Nutanix Database Automation (NCP-DB) learning documents, when provisioning a new database, there are two options available for the target12:

Provision database to an existing registered: This option allows you to provision a database to an existing registered database server. This is useful when you want to add a database to a server that is already being managed by Nutanix Era1.

Provision databases to a new container: This option allows you to provision a database to a new container. This is useful when you want to create a new isolated environment for your database1.

According to the Nutanix Database Automation (NCP-DB) learning documents, metadata tags can be applied to various entities in Nutanix Era for better database inventory management1. Among the options provided, Databases and Clones are two entities that support metadata tags1. These tags can be used to categorize, search, and manage these entities more effectively1. Please note that the information might be available in the Nutanix Database Automation (NCP-DB) course materials or in the Nutanix Era documentation.