Free Practice Questions for the Nutanix Certified Professional (NCP) NCP-DB Exam (2026 Updated)

In Nutanix Database Service (NDB), when an administrator deprecates a software profile version, it is marked as obsolete and restricted from certain operations. Specifically, a deprecated software profile version can no longer be used for provisioning new database instances or VMs. This ensures that only current, supported versions are utilized for new deployments, maintaining consistency and security. Existing database servers using the deprecated profile can continue to operate and may still be patched (if updates are compatible), but the profile itself is excluded from future provisioning tasks.

Option A is correct because deprecation explicitly prevents the profile version from being selected for new provisioning, aligning with NDB’s lifecycle management.

Option B (It can be used in provisioning) is incorrect as this contradicts the purpose of deprecation.

Option C (Any database server using that profile will be updated to the latest software profile) is incorrect because deprecation does not automatically update existing servers; it only affects new provisioning.

Option D (Any database server using that software profile can no longer be patched) is incorrect because patching existing servers is still possible if compatible updates exist, independent of the profile’s deprecated status.

Deprecation is a deliberate administrative action to phase out outdated profiles while preserving existing deployments.

References

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

Nutanix Support & Insights, Knowledge Base Article: "Software Profile Management in NDB"

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

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.

The exhibit shows the configuration of unencrypted Active Directory (AD) access in NDB, with the "Primary URL" set to ldap:// (indicating LDAP rather than LDAPS). Unencrypted LDAP communication uses port 389 by default. For NDB to communicate with Active Directory, this port must be allowed through the firewall to enable the NDB server to perform authentication and directory lookups using the specified service account (e.g., administrator).

Other options are incorrect in this context:

B. 636: This is the default port for LDAPS (LDAP over SSL/TLS), which is encrypted and not applicable since the configuration uses unencrypted LDAP.

C. 2009: This is not a standard port for LDAP or AD communication and is unrelated to NDB’s AD integration.

D. 9440: This is associated with Prism Element’s HTTPS management interface, not AD access.

Thus, the verified answer is A. 389, ensuring unencrypted LDAP communication between NDB and Active Directory.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.5: Configuring Active Directory Integration.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.4: Configure AD Access (applicable to v7.5).

Nutanix NDB Administration Guide: "Active Directory Integration" section, detailing LDAP port requirements.

NDB supports database and database server VM deployment on NC2 on Azure by using overlay networks created through Nutanix Flow Virtual Networking. A Flow overlay subnet provides the logical network used by the NDB-managed database server VMs while allowing the networking configuration to operate consistently within the NC2 environment. Flow underlay subnets are not the supported choice for this NDB deployment model. AHV IP Address Management is associated with AHV-managed networks and does not represent the required NC2 on Azure networking type. Azure-native networking exists beneath the NC2 infrastructure, but NDB-managed database provisioning uses the Flow overlay network exposed within NC2 rather than directly attaching database VMs to a native Azure network. Nutanix’s official NDB on NC2 documentation confirms support for Flow Virtual Networking overlay networks on NC2 environments.

To roll back an Oracle patch on a database server VM using NDB, the patch must have been applied using NDB in the first place. This is because NDB maintains a patch inventory and history for each database server VM and database that it manages. NDB uses this information to determine which patches can be rolled back and how to revert the changes made by the patch. If the patch was applied outside of NDB, NDB would not have the patch information and would not be able to roll back the patch. Therefore, the patch must have been applied using NDB for the rollback action to be successful. The other options are not required for the rollback action. The database does not need to be shut down or in read-only mode, as NDB can perform the rollback operation online. The patch does not need to be applied on Grid home only, as NDB can roll back patches applied on both Grid home and Database home. References:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 4 - Operate and Maintain an NDB Environment, Objective 4.4: Determine the correct method to apply Linux OS patches

Nutanix Database Management & Automation (NDMA) Course, Module 5: Nutanix Database Service (NDB) Patching, Lesson 5.1: Patching Overview, Topic: Patching Concepts

[Nutanix Database Service (NDB) User Guide], Chapter 7: Patching, Section: Rolling Back a Patch

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) v7.5Blueprint, Section 6: Administer an NDB Environment

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

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

When an administrator needs to scale the size of an Oracle database running on Nutanix NDB and originally configured using ASMLib (Automatic Storage Management Library), the most efficient approach is to use NDB’s built-in scaling ability to resize existing vDisks. NDB supports dynamic resizing of virtual disks (vDisks) associated with database VMs, allowing the administrator to increase storage capacity without disrupting the database or requiring complex migrations. This method leverages Nutanix’s storage integration, resizing the underlying vDisks and updating the ASMLib configuration to reflect the new size, ensuring seamless operation.

Option A (Leverage the scaling ability built into NDB to resize existing vDisks) is correct as it is the most efficient, native NDB feature for scaling storage.

Option B (Extend the size by adding new vDisks) is incorrect because adding new vDisks requires additional configuration (e.g., ASM disk group adjustments), making it less efficient than resizing.

Option C (Create a new, larger database and migrate) is incorrect because migration is time-consuming and unnecessary when resizing is supported.

Option D (Mount an iSCSI LUN and extend the database onto the new LUN) is incorrect because iSCSI LUNs are not the preferred method in NDB, and resizing vDisks is more integrated.

This approach minimizes downtime and complexity.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Scaling Storage for Databases

Nutanix Support & Insights, Knowledge Base Article: "Resizing vDisks for Oracle Databases in NDB"

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

To provision a PostgreSQL HA instance from a software profile created from a VM with services like etcd, HAProxy, Patroni, and keepalived installed, the administrator must ensure the instance aligns with NDB’s HA framework. These services (e.g., Patroni for PostgreSQL HA management, HAProxy for load balancing) may conflict with NDB’s built-in HA mechanisms. Provisioning an HA instance with these services disabled allows NDB to manage HA using its native replication and failover capabilities (e.g., streaming replication), avoiding duplication or interference from the VM’s pre-installed services.

Option A (Provision an HA instance with the services enabled) is incorrect because enabling these services may cause conflicts with NDB’s HA management.

Option B (Disable the services, create a software profile version, and provision an HA instance) is incorrect because disabling services and recreating a profile is unnecessary; the provisioning step can handle service configuration.

Option C (Provision an HA instance with the services disabled) is correct as it ensures NDB’s HA features take precedence without interference.

Option D (Enable the services, create a software profile version, and provision an HA instance) is incorrect due to potential conflicts with NDB’s HA implementation.

Note: The typo "PostqreSQL" is assumed to mean "PostgreSQL."

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Provisioning HA Instances

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

NDB requires Prism Element credentials when a Nutanix cluster is registered. These credentials authorize NDB to communicate with the cluster and perform the infrastructure operations required for database lifecycle management. Depending on the workflow, those operations can include discovering resources, creating database server VMs, attaching or mapping storage, taking snapshots, and managing networking-related configuration. Active Directory credentials may be required for a Windows domain or database-specific authentication workflow, but they are not the fundamental credentials used to register the Nutanix cluster. Similarly, a syslog server identity and Nutanix Objects store information are not required for basic cluster registration. Nutanix’s official NDB cluster-registration documentation requires the cluster address and appropriate Prism Element administrator username and password so that NDB can access and manage the target cluster.

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.

According to the Nutanix Database Automation (NCP-DB) course, a Software Profile is a template that defines the configuration of the database engine, such as the version, edition, features, and parameters1. It also specifies the disk layout for the database installation, such as the size, type, and mount point of each disk1. However, the System Page File disk is omitted from the Software Profile, as it is automatically created by the NDB service based on the memory size of the database server VM1. The other options are included in the Software Profile, as they are essential for the database operation and performance1. References:

1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.3: Software Profiles, slide 5

In the Nutanix Database Automation (NCP-DB) framework, provisioning a new Oracle database through Era requires the configuration of both a Compute and a Storage profile1. The Compute profile is used to define the resources allocated to the database, such as CPU and memory, while the Storage profile is used to specify the storage configuration for the database. These profiles are essential in ensuring that the database is provisioned with the necessary resources and storage configurations for optimal performance23.

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) v7.5Blueprint, 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) v7.5Blueprint, Section 6: Administer an NDB Environment

The "Savings over traditional cloning" metric in the Data Usage widget on the NDB dashboard reflects the efficiency of NDB’s cloning technology compared to traditional full-copy cloning methods. NDB leverages Nutanix’s near-zero byte cloning capability, which creates lightweight clones by sharing base data and only storing changes (deltas). This metric specifically quantifies the disk space saved by using these efficient clones instead of duplicating entire datasets, as would occur in traditional cloning. It highlights NDB’s storage optimization for database provisioning and management.

Option A is correct as it directly ties to NDB’s near-zero byte cloning technology, a core feature for space efficiency.

Option B (Compression) is incorrect because compression is a separate storage optimization technique not specifically tied to cloning savings.

Option C (Shadow clones) is incorrect because shadow clones are a Nutanix feature for caching, not the cloning mechanism used by NDB Time Machines.

Option D (Deduplication) is incorrect as deduplication, while related to storage savings, is not the primary mechanism reflected in this cloning-specific metric.

This metric helps administrators quantify the benefits of NDB’s cloning approach in terms of storage utilization.

References

Nutanix Database Service (NDB) User Guide, Chapter 1: Introduction to NDB, Section: Understanding Cloning and Storage Efficiency

Nutanix Support & Insights, Technical Note: "Interpreting NDB Dashboard Metrics"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 1: NDB Concepts and Architecture

When an administrator is creating a Windows Domain profile in Era, the SQL Service Startup Account is an optional field that can be skipped and provided during the provisioning process. This account is used to start the SQL Server service when the server starts up. If this field is not provided during the creation of the Windows Domain profile, it can be provided later during the provisioning process1.

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) v7.5Blueprint, Section 6: Administer an NDB Environment

NDB requires management and storage connectivity to a registered Nutanix cluster. TCP 9440 carries Prism REST API communication between NDB components and the Nutanix cluster. TCP 3205 and 3260 support iSCSI redirection/data and standard iSCSI control traffic used when NDB attaches Volume Group disks. Therefore, both option B and option D must be allowed through the segmented network. Port 443 is used for HTTPS communication in other NDB paths, but it is not the required Prism/CVM port represented by this question. Ports 1433 and 5432 are database listener ports for Microsoft SQL Server and PostgreSQL, respectively, rather than NDB-to-CVM infrastructure ports. The source answer “D” is incomplete; the verified answer is B and D. Nutanix port reference

================

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

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.

The NDB Windows Domain Profile centralizes the Active Directory information required when provisioning Microsoft SQL Server database server VMs. It contains the domain FQDN, domain credentials, organizational-unit paths, SQL Server service startup account, and NDB worker service account information. A group Managed Service Account is an Active Directory service identity and therefore belongs in this domain-related configuration rather than a Software, Database Parameters, or Network Profile. A Software Profile supplies the operating system and SQL Server binaries. A Database Parameters Profile controls SQL Server engine initialization and runtime settings, while a Network Profile specifies the VLAN and IP configuration used by the VM. Because the requirement concerns the identity under which SQL Server services operate in an Active Directory environment, the correct selection is C, Windows Domain Profile. NDB User Guide—Windows Domain Profiles

================

NDB supports centralized drive-letter customization for SQL Server through the NDB server CLI global configuration. Nutanix documents this as the supported method for setting the database, log, backup, and TempDB drive letters used by NDB-managed provisioning and clone workflows. After the administrator changes the global values, NDB applies those assignments when it prepares eligible SQL Server database server VMs. The drive letters are not supplied interactively during each provisioning operation, stored in a Windows Domain Profile, or introduced merely by adding disks to a Software Profile. Therefore, option A is correct. The candidate file’s supplied answer B conflicts with the documented NDB configuration method and has been corrected. Nutanix SQL Server limitations

NDB patches MongoDB replica sets through a rolling workflow designed to minimize database unavailability. It first applies the selected patch to available secondary members one at a time. After the secondary members are successfully patched and validated, NDB performs the required replica-set role transitions and patches the primary member last. This order preserves service availability and avoids simultaneously taking every voting member offline. Nutanix explicitly documents rolling upgrades for MongoDB replica sets; NDB does not patch all members in parallel, and the primary is not the first member patched. Current NDB documentation also lists patching and upgrading MongoDB sharded clusters as unsupported. Therefore, the verified positive statement about the supported patching workflow is that rolling patching is available for replica sets. Nutanix MongoDB cluster-patching documentation

The correct answer is C because a stretched VLAN is a VLAN that spans across multiple Nutanix clusters, which may cause network conflicts or latency issues when starting the database server. Option A is incorrect because a DHCP VLAN is a VLAN that uses dynamic IP address allocation, which does not affect the database server startup. Option B is incorrect because a static VLAN is a VLAN that uses fixed IP address allocation, which also does not affect the database server startup. Option D is incorrect because IPAM is not a type of VLAN, but a feature of NDB that allows managing IP addresses for database servers and databases.

The following sources provide more information about the VLAN and IPAM concepts and configuration in NDB:

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

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

Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section 2.4: Configuring NDB High Availability

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.5: Managing Networks in NDB

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.6: Managing IP Addresses in NDB

NDB requires the administrator to verify the Active Directory configuration before enabling the Save action. After entering the directory server, domain, service-account credentials, and related configuration information, the administrator must click Verify. NDB then tests whether it can connect to the Active Directory server and authenticate using the supplied service account. The Save button becomes available only after this verification succeeds. This prevents an unreachable server, invalid credential, incorrect domain, or connectivity problem from being stored as the active authentication configuration. SMTP alerting is a separate notification feature and has no dependency on Active Directory configuration. A secondary URL is not a mandatory field, and providing a domain IP address alone does not replace the connectivity-verification step. Nutanix documents this sequence explicitly in its official procedure for configuring Active Directory access.

 Nutanix Database Automation (NCP-DB) introduces the concept of MS SQL Server database groups, which allows multiple databases running in the same database instance to be grouped as one Time Machine entity1. This applies to both single DB Server VM setups, standalone databases, as well as to Availability Group databases1. However, it does not support Point In Time Recovery (PITR)-based Service Level Agreements (SLAs) for database groups containing mixed Recovery Models. This means that if the databases within the group have different recovery models, PITR-based SLAs cannot be applied to the group as a whole.

Nutanix Database Automation (NCP-DB) allows administrators to manage Service Level Agreements (SLAs) for databases. These SLAs define the data protection policies for databases. In this case, to minimize storage usage for a test database, the administrator should select the built-in NONE SLA. This SLA is configured for no snapshot or log backup, thus minimizing storage usage1.

When an administrator needs to restore databases provisioned with a shared disk configuration on Windows Storage Spaces in Nutanix Database Service (NDB), the restore operation focuses on the disks associated with the database. Windows Storage Spaces provides a virtualized storage layer, and NDB manages the restoration by reverting or recovering the specific disks that host the database files and logs. This ensures that the database is restored to its previous state using the snapshot or backup data, while preserving the shared disk configuration integrity. NDB does not replace the source volume or perform additional operations like tail log backups unless explicitly configured.

Option A (NDB restores the disk that are associated with the database) is correct as it accurately describes NDB’s restore behavior for shared disk setups.

Option B (NDB copies the DB files to be restored to the source volume) is incorrect because NDB restores the entire disk state, not just copying files to the source.

Option C (NDB replaces the source volume with the snapshot volume) is incorrect because NDB restores data to the existing volume, not replacing it entirely.

Option D (NDB performs Tail Log backup to backup any remaining logs) is incorrect because tail log backups are not automatically part of the restore process unless specified for point-in-time recovery.

This approach ensures compatibility with Windows Storage Spaces configurations.

References

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

Nutanix Support & Insights, Knowledge Base Article: "Restoring Windows Storage Spaces in NDB"

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

Before patching several Nutanix database server VMs using the "Patch OS now" feature in NDB, the administrator must configure a Repository. A repository (e.g., a custom patch repository or Nutanix-provided source) contains the OS updates or patches (e.g., for Windows or Red Hat-based systems). NDB requires this repository to be specified to fetch and apply the patches, ensuring the database VMs are updated from a validated source.

Other options are unrelated to patching:

B. Active Directory Access: Used for authentication, not patching.

C. pulse: Refers to Nutanix Pulse for support, not patch configuration.

D. An SMTP Server: Configured for alerts, not patching.

Thus, the verified answer is A, reflecting the patching prerequisite.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.3: Creating Maintenance Plans.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v7.5).

Nutanix NDB Administration Guide: "Configuring Patch Repositories" section.

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.

To ensure an NDB server can send periodic telemetry data to the central Nutanix repository, the server must be able to communicate with the Nutanix Insights platform over port 443 (HTTPS). The insights.nutanix.com site is the designated endpoint for telemetry data, which includes usage statistics, health metrics, and other operational data sent to Nutanix for support and analytics purposes. This connectivity is a standard requirement for NDB to comply with Nutanix’s telemetry and support framework, and port 443 is used for secure transmission.

Option A (download.nutanix.com) is incorrect because this site is used for downloading software updates, not telemetry data.

Option B (developers.nutanix.com) is incorrect as it is a resource for developers, not a telemetry endpoint.

Option C (portal.nutanix.com) is incorrect because this is the Nutanix customer portal for account management, not telemetry submission.

Option D (insights.nutanix.com) is correct as it is the specific site for sending telemetry data.

The administrator should ensure network policies allow outbound traffic to this site on port 443.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Telemetry and Connectivity Requirements

Nutanix Support & Insights, Knowledge Base Article: "Configuring Telemetry for NDB"

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

The Nutanix Era Time Machine provides various capabilities depending on the Service Level Agreement (SLA) selected during database registration1. For a database with a Bronze SLA, the Time Machine supports both “Log Catch up” and "Snapshots"2. “Log Catch up” allows the Time Machine to keep up with the latest changes in the database by capturing log data2. “Snapshots” are point-in-time copies of the database that can be used for recovery or cloning2.

According to the Nutanix Database Automation (NCP-DB) learning documents, the Schedule feature of the Time Machine allows developers to automate the data refresh for their clones1. This feature eliminates the time-consuming, complex process of database clone/refresh, allowing admins to create database clones/refresh to any point in time in just a few minutes1. Please refer to the official Nutanix documentation and training materials for more detailed information2.

For a One-Click Upgrade of an NDB environment with internet access, the patch should be downloaded directly within the NDB interface. The "Administrator > Maintenance" section of NDB provides an option to connect to the Nutanix download repository (e.g., https://download.nutanix.com) and download the latest patch or upgrade bundle automatically. This streamlined process ensures compatibility and simplifies the upgrade workflow. The One-Click Upgrade feature then applies the downloaded patch to update NDB components efficiently.

Other options are incorrect:

A. Download the patch from the Nutanix Support Portal and upload via the NDB CLI: This is suitable for dark sites but unnecessary with internet access, as NDB can download directly.

C. Open Prism Central and deploy the current version of NDB from the Apps and Marketplace section: This is for initial deployment, not upgrading an existing NDB instance.

D. Open Prism Element and use LCM to update the software: Lifecycle Manager (LCM) is for Nutanix cluster updates, not NDB-specific upgrades.

Thus, the verified answer is B, leveraging NDB’s built-in maintenance capabilities.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "One-Click Upgrade Process" section.

When an administrator enables NDB Multi-cluster functionality, certain components are deployed or reconfigured to support the distributed environment. HAProxy (High Availability Proxy) is a critical component that manages load balancing and secure communication across clusters. In a multi-cluster setup, HAProxy is deployed on a dedicated VM to ensure efficient traffic distribution and high availability for NDB services, such as API calls and GUI access, across the clusters. This dedicated deployment enhances scalability and resilience.

Option A (Agent VM) is incorrect because Agent VMs are typically deployed on managed database VMs, not as dedicated NDB service components in multi-cluster setups.

Option B (HAProxy) is correct as it is specifically deployed on a dedicated VM to handle load balancing in a multi-cluster NDB environment.

Option C (Repository DB) is incorrect because the Repository DB is part of the NDB control plane and not necessarily deployed on a separate VM for multi-cluster purposes.

Option D (APIVM) is incorrect because the API VM is part of the core NDB infrastructure but not specifically deployed as a dedicated VM for multi-cluster enablement.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Multi-Cluster Configuration

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

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

MySQL HA uses MySQL Router as the application-facing routing layer. When NDB provisions an HA instance, the Create MySQL Router option can be enabled so clients connect through router VMs instead of targeting individual database nodes. The router uses cluster topology information to direct traffic to the appropriate active member and maintain connectivity when failover changes the primary. HAProxy is the component NDB commonly uses for PostgreSQL HA and for the NDB control plane; it is not the native routing choice for a MySQL InnoDB HA deployment. An external load balancer can be used in a custom design, but it is not the requested NDB-managed option. A multi-host connection string shifts failover handling to the application rather than enabling automated routing in NDB. Nutanix exposes this setting in the MySQL HA provisioning workflow.

The minimum frequency configurable for the NDB Log Catch-up operation is 15 minutes. This setting determines how frequently the log catch-up process runs, which is crucial for maintaining data integrity and ensuring up-to-date database states.

NDB sends alert notifications using configurations auto-populated from the cluster during the initial setup, typically relying on default SMTP settings. If a dedicated SMTP server is required (e.g., for security or compliance), the administrator must change the SMTP Server configuration in NDB Service. This is configured under the NDB Admin Center, where the administrator can specify the dedicated SMTP server’s details (e.g., hostname, port, credentials, and security settings like TLS/SSL).

Other options are incorrect:

A. IDP configuration in Admin Center IAM page: Identity Provider (IDP) settings are for authentication, not email alerts.

B. Alert Email configuration in Prism Element: Prism Element manages cluster alerts, not NDB-specific email settings.

D. SNMP configuration in Prism Central: SNMP is for network monitoring, not email notifications.

Thus, the verified answer is C, reflecting NDB’s alert notification setup.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.1: Configuring Alert Notifications.

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

Nutanix NDB Administration Guide: "Configuring SMTP for Alerts" section.

According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era is a database management tool that automates and simplifies database operations, including provisioning, patching, upgrading, and more1. However, for a database to be managed by Era, it must be registered with Era1. This means that if a database is on a non-Nutanix platform, it cannot be directly upgraded using an Era workflow. It must first be migrated to a Nutanix platform and registered with Era before it can be managed and upgraded using Era1.

The scenario describes a PostgreSQL HA deployment managed by NDB, where an NDB-managed VLAN (PGSQLVLAN40) restricts database communication to only within VLAN 40. This indicates a network isolation issue, likely due to VLAN segmentation or routing misconfiguration, preventing communication with external networks or other VLANs. Since NDB manages the VLAN and assigns it to the database VMs, the issue lies beyond NDB’s direct control and involves the underlying network infrastructure (e.g., switches, routers, or Prism Element network settings).

Here’s why the other options are insufficient:

A. Use VLAN 1: VLAN 1 is typically a default VLAN and not recommended for production use due to security and isolation concerns. Changing to VLAN 1 does not address the root cause and could introduce further issues.

B. Change the Default Gateway on the PostgreSQL servers and update NDB: While adjusting the default gateway might enable external communication, this is a workaround rather than a fix. NDB manages the network configuration, and manual changes could be overwritten or cause inconsistency. The root issue (VLAN routing) remains unaddressed.

D. Delete the database servers, VLAN name PGSQLVLAN40, and redeploy: This is overly disruptive and unnecessary, as recreating everything under a new VLAN name does not guarantee resolution unless the network configuration is corrected.

The best approach is to engage the networking team to investigate and resolve the issue, such as configuring inter-VLAN routing, updating firewall rules, or adjusting the default gateway at the network level. Going forward, the administrator should collaborate with the networking team during VLAN planning to ensure proper connectivity. Thus, the verified answer is C.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 4: Troubleshooting NDB, Lesson 4.1: Identifying and Resolving Network Issues.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 4: Troubleshoot NDB Solutions, Objective 4.2: Resolve Network-Related Issues (applicable to v7.5).

Nutanix NDB Administration Guide: "Networking Considerations for HA Deployments" section.

The Global Service Level Agreement (SLA) feature of Era allows an administrator to create Time Machine policies in a Multi-Cluster configuration1. This feature provides a unified way to manage and enforce backup and replication policies across multiple clusters, ensuring consistent data protection and recovery across the entire environment1.

The correct answer is B because setting VM-Host affinity ensures that the DB Server VMs are not migrated to another host during the LCM upgrade process. This way, the DB Server VMs can continue to serve the database requests without interruption. Option A is incorrect because updating the Nutanix cluster does not prevent the DB Server VMs from being moved to another host. Option C is incorrect because removing the Nutanix cluster from NDB will make the DB Server VMs unmanaged by NDB and lose the benefits of NDB features. Option D is incorrect because unsetting VM-Host affinity will allow the DB Server VMs to be migrated to another host during the LCM upgrade process, which may cause downtime or performance degradation.

The following sources provide more information about the LCM upgrades and VM-Host affinity in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 6: Administering an NDB Environment, Lesson 6.3: Performing NDB Software Upgrades

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

Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.3: Performing NDB Software Upgrades

Nutanix Support & Insights, Your guide to the Upgrades, LCM Design

Nutanix Life Cycle Manager Guide, Chapter 3: Upgrading Software and Firmware, Section 3.2: Preparing for an Upgrade, VM-Host Affinity

According to the Nutanix Database Automation (NCP-DB) course, the ports 3205 and 3260 are required for iSCSI connections between the NDB server and the Controller VMs1. Port 3205 is used for the NDB iSCSI initiator service, which initiates the iSCSI sessions and sends SCSI commands to the Controller VMs1. Port 3260 is used for the iSCSI target service, which listens for incoming iSCSI requests and provides access to the storage devices on the Controller VMs1. The other options are not related to iSCSI connections. Port 22 is used for SSH, port 9440 is used for Prism Central, port 80 is used for HTTP, port 443 is used for HTTPS, port 5985 is used for WinRM HTTP, and port 5986 is used for WinRM HTTPS2. References:

1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.2: Database Engine Installation, slide 13

2: Nutanix NCP-DB Certification Exam Sample Questions, Question 18, Answer

For an NDB offline upgrade, you need to download the upgrade bundle from the Nutanix Support Portal and copy it to the NDB server. Then, you need to use the NDB CLI command upload upgrade_bundle with the path parameter to specify the location of the upgrade bundle file. This command will upload the upgrade bundle to the NDB server and verify its integrity. After uploading the upgrade bundle, you can use the upgrade command to perform the upgrade. References: Nutanix Support & Insights, Cisco Nexus Data Broker Deployment Guide, Release 3.10.x

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

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

Time Machine is a feature of Nutanix Era that allows you to create and manage snapshots of your databases. You can use Time Machine to create clones from any snapshot, either manually or automatically. You can also configure Time Machine to create clones from snapshots based on a schedule, such as daily, weekly, or monthly. This way, you can ensure that your clones are always up to date with the latest data from your production databases. In this scenario, the most efficient way to meet the developer’s requirement is to configure Time Machine to create a clone from a daily snapshot at 7:00am. This will save the developer’s time and effort, as well as reduce the storage consumption by using the existing snapshots. References:

Nutanix Database Management & Automation Training Course

Nutanix Certified Professional - Database Automation datasheet

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam

 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.

A Development team requesting updated data for a cloned MongoDB instance used as source data for a script needs the latest snapshot or point-in-time data. In NDB, the "Clone Refresh" task updates an existing clone with the most recent data from the source database, ensuring the development team has access to current information without recreating the clone. This is the most efficient approach for maintaining an updated clone.

Option A (Clone the DB from the latest point in time data) is incorrect because it creates a new clone, duplicating effort instead of refreshing the existing one.

Option B (Execute a clone update) is incorrect as "clone update" is not a standard NDB task; refresh is the correct term.

Option C (Provision a MongoDB instance) is incorrect because it provisions a new instance, not an update to the clone.

Option D is correct as Clone Refresh syncs the clone with the latest source data.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Clones and Refresh

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

Failed NDB provisioning workflows normally perform a rollback that removes resources created during the unsuccessful operation, including the database server VM. For troubleshooting, the administrator can enable the global skip_rollback_global setting so that NDB does not execute this cleanup path. The failed VM is then preserved for inspection of its operating-system state, logs, network configuration, and database installation artifacts. Nutanix Support states that automatic deletion occurs only when delete_vm_on_failure is true and skip_rollback_global is false; other combinations preserve the VM and require manual cleanup afterward. Because the question specifically asks which global rollback option must be enabled, skip_rollback_global is the correct selection. It should be returned to its normal value after troubleshooting to avoid abandoned resources. Nutanix KB 14629

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) v7.5Blueprint, Section 4: Manage Database Software Profiles

The Storage Usage widget on the NDB dashboard provides the required entity-level storage information. It displays the percentage of storage consumed by registered Nutanix clusters and NDB entities, including source databases, database clones, and Time Machines. Administrators can use this information to distinguish production database capacity from space consumed by protected copies and downstream clones. NDB periodically collects and stores historical usage information, which also supports storage-trend analysis and capacity forecasting. Prism Element and Prism Central provide infrastructure-level capacity information, but they do not present the same NDB-aware classification of source databases, clones, and Time Machines. NCM reporting is therefore unnecessary for this specific requirement. The official NDB Dashboard reference identifies Storage Usage as the dashboard widget that reports consumption for clusters, data sources, clones, and Time Machines.

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) v7.5Blueprint, Section 5: Protect Databases Using Time Machine

NDB Time Machine protects Microsoft SQL Server databases through application-consistent snapshots and a continuous sequence of transaction-log backups captured by Log Catch-up operations. When the latest protected time is selected, NDB uses the appropriate snapshot as the baseline and applies the required transaction logs through the most recent available recovery point. This produces a transactionally consistent clone rather than a crash-consistent VM copy. NDB does not need to leave the source database in read-only mode, and Volume Shadow Copy Service alone cannot provide the transaction-log replay required for granular point-in-time cloning. “Latest Time” means the latest point covered by the valid Time Machine snapshot and log chain, not an unprotected wall-clock instant after the last log capture. Nutanix’s Database Log Backup Management documentation explains that Log Catch-up captures database transaction logs for point-in-time cloning.

NDB High Availability (HA) is a feature that ensures the availability and reliability of the NDB management plane components, such as the API Server, the Repository VMs, and the NDB Agents. To enable NDB HA, you need to deploy at least three HA Proxy VMs on the same L2 network as the NDB Server VM. The HA Proxy VMs act as load balancers and health monitors for the NDB management plane components, and they also provide a single endpoint for accessing the NDB APIs and UI. References:

Nutanix Certified Professional - Database Automation (NCP-DB), Section 2 - Deploy and Configure an NDB Solution

Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 7, Objective 2.3

Nutanix Database Management & Automation (NDMA) course, Module 2, Lesson 2.3 - NDB High Availability

The first NDB management-plane VM on an AHV-based Nutanix cluster is deployed from the NDB QCOW2 disk image. The administrator downloads the QCOW2 image from the Nutanix Support portal, configures it through the Prism Element Image Service, and then creates the NDB VM from that image. QCOW2 is the appropriate virtual-disk format for AHV because AHV uses the KVM virtualization stack. VMDK is principally associated with VMware virtual disks, VHDX is used by Microsoft Hyper-V, and VDI is associated primarily with Oracle VirtualBox. Those formats are not used for the initial NDB VM deployment on a dedicated AHV cluster. Consequently, option C is correct. The VM must subsequently receive the required compute, network, and static-IP configuration before NDB initial setup is completed. NDB User Guide—Installing NDB on AHV

================

NDB High Availability uses multiple API Server VMs to provide the user interface and REST API services. The platform can automatically tolerate the failure of up to two service VMs, but if every API Server VM is offline, the API service becomes completely unavailable and manual intervention is required. Recovery requires bringing at least one API Server VM back online. Once an API Server is running, the NDB API service can restart and the remaining HA components can rejoin or recover through the normal resiliency mechanisms. Restarting HAProxy first cannot restore an API service when no API Server is available. Repository VMs should not be recreated because they contain NDB metadata, and registered Nutanix clusters do not need to be registered again. Therefore, the correct answer is A. NDB HA failure and recovery scenarios

================

Selecting Group Database with One Time Machine associates multiple SQL Server databases with one protection construct rather than separate Time Machines. Nutanix explicitly recommends grouping databases when they share protection requirements because the arrangement provides optimized RPO and improved performance. It also lets the group be protected, cloned, and recovered consistently under one SLA and one snapshot and log-catch-up schedule. Reduced storage consumption may occur as a secondary operational effect, but it is not the documented key architectural benefit. Faster provisioning is likewise not the principal reason for creating a database group, and independent recovery contradicts the group model because the databases share the same Time Machine. Therefore, optimized RPO and performance is the only option that matches Nutanix’s documented guidance for database groups.

There are two ways to upgrade an NDB Server: one-click upgrade and offline upgrade. One-click upgrade is the recommended method, as it automatically downloads and installs the latest NDB software version from the Nutanix portal. Offline upgrade is an alternative method, which requires you to manually download the NDB software bundle and upload it to the NDB Server VM. Both methods require you to have a valid Nutanix account and an internet connection. References:

Nutanix Certified Professional - Database Automation (NCP-DB), Section 6 - Administer an NDB Environment

Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 10, Objective 6.2

Nutanix Database Management & Automation (NDMA) course, Module 6, Lesson 6.1 - NDB Software Upgrade

According to the Nutanix Database Automation (NCP-DB) learning documents, to create a network profile in Era, the network must be added to Era1. This is because Era needs to have control over the network in order to manage the databases effectively1. Once the network is added to Era, it can be used for various operations such as provisioning new databases, managing existing databases, and more1.

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) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Time Machine States (applicable to v7.5).

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

In Nutanix Database Service (NDB), alert policies are configured to notify administrators of significant events affecting database operations. The default severity level for NDB alert policies is set to Error. This level indicates issues that require attention, such as failed operations (e.g., provisioning failures, as shown in the exhibit), connectivity issues, or other critical operational problems. Other severity levels like Info, Critical, and Warning may be used for different scenarios, but the base configuration for NDB alert policies starts at Error to ensure administrators are alerted to actionable issues without being overwhelmed by less severe notifications.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.1: Configuring Alert Policies.

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

Nutanix NDB Administration Guide: "Alert Policies and Severity Levels" section.

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) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.3: Perform NDB Updates (applicable to v7.5).

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

The Database Agent is used to temporarily store the transaction logs of the source database before they are copied to the log. This is a critical component for ensuring data consistency and recovery in database operations.

NDB deployments on NC2 use overlay networking created with Nutanix Flow Virtual Networking. Consequently, an appropriate Flow overlay subnet must be created for NDB and the database server VMs that it will manage. A floating IP address must also be created or assigned to the NDB VM so that the NDB interface and services are reachable through the cloud networking environment. A Flow underlay subnet is not the supported network type for this deployment. Although an NC2 environment ultimately operates within AWS networking infrastructure, creating a native AWS VPC is not the NDB-specific deployment step requested by the question. Nutanix’s NC2 networking documentation identifies Flow-created overlay networks, while the Flow integration guidance describes assigning a floating IP address to the NDB VM.

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

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

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

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

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

References

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

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

NDB creates database clones by using Nutanix space-efficient snapshots instead of copying every source database block into a new 2 TB allocation. The initial clone primarily consists of metadata and references to the source snapshot’s existing blocks. Consequently, it consumes near-zero additional storage when it is first created. The clone becomes an independent database environment, and new physical capacity is consumed only when blocks are changed or newly written. Because the question specifies that the clone remains read-only, there should be no meaningful database write growth after creation. Its storage consumption is therefore not equal to the source size and is not determined by fixed compression ratios such as 50 or 20 percent. Nutanix’s official Clone Management documentation states that NDB clones are highly space-efficient and initially consume near-zero additional bytes.

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

Other options are insufficient:

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

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

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

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

Official Nutanix Database Automation References

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

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

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

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) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix cluster in NDB (applicable to v7.5 with no significant role changes documented).

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

To create a Microsoft SQL Server software profile for each of the three Nutanix clusters in an NDB environment, a key requirement is that each cluster must host at least one VM with the Microsoft SQL Server database engine installed. NDB uses these VMs to discover, validate, and generate software profiles tailored to the specific SQL Server versions and configurations present on each cluster. This ensures that the profiles are compatible with the cluster’s environment and can be used for provisioning or patching.

Option A (Compute profile must be created first on every cluster) is incorrect because compute profiles are optional and not a prerequisite for creating software profiles.

Option B (Enable Multi-cluster capabilities for NDB) is incorrect as multi-cluster support is already implied by the deployment across three clusters, but it’s not a specific requirement for profile creation.

Option C (Enable High Availability for the current NDB Service) is incorrect because HA is a separate configuration and not required to create software profiles.

Option D (Each cluster must host a VM with the DB engine) is correct as it aligns with NDB’s requirement to have a reference VM for profile generation.

This setup ensures accurate and cluster-specific software profile creation.

References

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

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

NDB allows creating and refreshing clones to a point in time using two primary methods:

B. Snapshots: NDB uses storage snapshots (e.g., via Nutanix Volumes or AHV) to capture the database state at a specific point. These snapshots can be used to create or refresh clones, providing a consistent recovery point.

D. Transaction logs: Transaction logs (e.g., PostgreSQL WAL, SQL Server logs) enable point-in-time recovery (PITR) by applying logs to a snapshot, allowing clones to be refreshed to a precise moment.

Other options are not supported for this purpose:

A. Full backups: Full backups are used for complete restores but are not optimized for frequent clone refreshes.

C. VM snapshots: VM-level snapshots (e.g., AHV snapshots) are not managed by NDB for database cloning, as they lack database consistency.

Thus, the verified answers are B and D, reflecting NDB’s clone refresh capabilities.

Official Nutanix Database Automation References

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

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Clones (applicable to v7.5).

Nutanix NDB Administration Guide: "Clone Creation and Refresh" section.

NDB supports patching for PostgreSQL database instances. Patching for PostgreSQL is validated on VMs provisioned by NDB (greenfield deployments). To patch PostgreSQL database server VMs, you must create a software profile version by uploading the PostgreSQL update file in NDB. You can then use the PostgreSQL update to patch other database server VMs or provision a new database server VM with the updated software profile. The first step in the NDB patching workflow is to create a software profile version with the desired PostgreSQL version.

Nutanix Database Automation (NCP-DB) Course Details, Section 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.1: Perform Database Patching

Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.1: NDB Patching Overview

Nutanix Database Automation (NCP-DB) User Guide, Section 4.4: Patch PostgreSQL Database Software

Before updating Oracle Database software, you need to download the Patch Set Update (PSU) from Oracle support. A PSU is a collection of critical and security patches for Oracle products. You need to have a valid Oracle account and access to the My Oracle Support portal to download the PSU. You also need to check the compatibility and prerequisites of the PSU before applying it to your Oracle Database software. NDB uses out-of-place patching for Oracle, which means you need to create a new software profile version with the patched Oracle software and use it to update your existing databases. References:

Patch Oracle Database Software, Nutanix Support & Insights

Nutanix Certified Professional - Database Automation (NCP-DB), Section 4 - Operate and Maintain an NDB Environment

Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.4 - Patching Databases

To replicate database snapshots to remote Nutanix clusters, the administrator needs to add Data Access to each Nutanix cluster and assign a Data Availability Management (DAM) policy. Data Access is a feature of NDB that enables cross-cluster data mobility and protection. A DAM policy defines the replication frequency, retention period, and priority of the database snapshots across the clusters. By adding Data Access to each Nutanix cluster and assigning a DAM policy, the administrator can manage the Time Machine data availability across all registered Nutanix clusters in NDB.

 Nutanix Support & Insights, section “NDB Data Access”

 NDB SLAs are service level agreements that define the data protection and recovery objectives for NDB-managed databases. NDB SLAs consist of data retention policies that specify how long the snapshots and log backups of a database are kept in the Time Machine. Data retention policies can be customized to meet different business and compliance requirements, such as daily, weekly, monthly, or yearly retention periods. NDB SLAs also determine the frequency and schedule of the snapshots and log backups, as well as the storage location and replication options. An administrator who is tasked with auditing NDB SLAs will be reviewing the data retention policies of each database and Time Machine, as well as the snapshot and log backup history and status. The administrator will also be able to monitor the storage usage and performance of the NDB SLAs, and modify or delete the SLAs as needed. The other options are not part of the NDB SLAs, but rather separate features or concepts of NDB. Snapshot schedules are the intervals at which NDB takes snapshots of the databases, which are determined by the SLAs. Clone management is the process of creating, refreshing, or deleting database clones from the Time Machine. Recovery time objective (RTO) is the maximum acceptable time for restoring a database after a failure, which is influenced by the SLAs, but not defined by them. References:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 5 - Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies

Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: SLA Concepts

Nutanix Database Service (NDB) User Guide, Chapter 6: SLAs, Section: SLA Overview

 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

To capture database transaction logs in NDB, the Log Catch-up operation within the Time Machine is used. Log Catch-up retrieves and applies transaction logs (e.g., PostgreSQL WAL, SQL Server logs) to a snapshot, ensuring the database can be restored to a specific point in time. This operation bridges gaps between snapshots by incorporating log data, maintaining a continuous recovery chain.

Other options are incorrect:

A. Write-Ahead Logging: A database feature (e.g., in PostgreSQL), not an NDB Time Machine operation.

B. Log Flush: Refers to writing logs to disk, not capturing them for recovery.

D. Snapshots: Capture the database state but do not handle transaction logs specifically.

Thus, the verified answer is C, aligning with NDB’s log management.

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) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Time Machine Operations (applicable to v7.5).

Nutanix NDB Administration Guide: "Log Catch-up Operation" section.

In an NDB high-availability deployment, multiple API server and repository VMs protect the availability of the management plane. If the primary API server becomes unavailable, NDB automatically fails over API responsibilities to an available standby server. HAProxy directs management requests to the functioning service, allowing administrators and automation clients to continue accessing NDB. The managed databases operate independently of the NDB API service for normal client connections, so an API-server failure does not automatically stop database workloads. Backup or patching workflows are not categorically canceled or suspended merely because one API service fails; their processing continues through the surviving HA components, subject to the state of the individual operation. Nutanix’s official highly available NDB architecture confirms that NDB automatically fails over to a standby VM when the primary API server or repository VM becomes unavailable.

When running the Linux prerequisites script for NDB, the -t argument is a required parameter that specifies the timeout interval. This argument defines the maximum time (in seconds) the script will wait for certain operations (e.g., connectivity checks, package installations) to complete before timing out. This is critical during the preinstallation phase to ensure the environment is properly configured and responsive, avoiding indefinite hangs. Other options are not associated with -t:

A. Operating System type: This is not a typical argument for the prerequisites script.

C. NDB server IP: This would be specified separately (e.g., via -s or a similar flag).

D. Database engine: This is irrelevant to the prerequisites script, which focuses on system setup.

Thus, the verified answer is B, aligning with the script’s purpose of managing execution timeouts.

Official Nutanix Database Automation References

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

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v7.5).

Nutanix NDB Installation Guide: "Running the Linux Prerequisites Script" section, detailing -t usage.

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.

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

In Nutanix Database Service (NDB), a Network Profile is used to define networking configurations for database VMs, including VLAN assignments and IP address ranges. The correct procedure to create a Network Profile that assigns a VLAN and provides IP addresses to a database VM is as follows:

Create Network Profile: Start by initiating the creation of a new Network Profile within NDB. This is done from the NDB interface under the "Network" or "Profiles" section.

Select the VLAN: During the Network Profile creation process, you specify the VLAN that the database VM will use. This involves selecting an existing VLAN configured in the Nutanix cluster (e.g., via Prism Element) or defining a new VLAN ID if applicable.

Define IP Range: Finally, you define the IP address range (e.g., a subnet or specific IPs) that will be assigned to the database VM(s) within the selected VLAN. This ensures the VM receives a valid IP address for communication.

The sequence in option B aligns with the NDB workflow, where the Network Profile is created first, followed by associating it with a VLAN and then defining the IP allocation. Other options are incorrect:

A: "Add the VLAN" is vague and does not specify where the VLAN is added, disrupting the logical flow.

C: Adding a VLAN before creating the profile is not the standard NDB process, as VLANs are associated during profile creation.

D: Defining an IP range before creating the profile is out of sequence, as the profile must exist to hold the configuration.

Thus, the verified answer is B. Create Network Profile, Select the VLAN, Define IP Range.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.2: Configuring Network Profiles.

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

Nutanix NDB Administration Guide: "Network Profiles" section, detailing VLAN and IP configuration steps.

To reset the NDB GUI password in Nutanix Database Service (NDB), an administrator must access the system through an SSH session and use the appropriate command-line interface (CLI) tools provided by NDB. The correct process involves entering the era-server CLI, which is the specific CLI environment for managing NDB-related configurations, including security settings like password resets. Once in the era-server CLI, the administrator executes the security password reset command to initiate the password reset process for the NDB GUI. This method ensures that the reset is performed within the NDB-managed environment securely and aligns with Nutanix’s recommended administrative procedures.

Option A is correct because it specifies the era-server CLI and the exact command security password reset, which are consistent with NDB’s administrative tools for managing GUI access credentials.

Option B (sudo passwd era) is incorrect because era is not a system user account in the context of NDB’s Linux-based control plane; this command pertains to standard Linux user management, not NDB-specific GUI password resets.

Option C (sudo passwd admin) is also incorrect as admin refers to a generic user that may not correspond to the NDB GUI account, and this approach bypasses NDB’s internal security mechanisms.

Option D is incorrect due to a typo (era CLI instead of era-server CLI), which renders it imprecise despite the intent being similar to Option A.

This process assumes the administrator has SSH access to the NDB control plane VM and the necessary privileges to execute these commands.

References

Nutanix Database Service (NDB) User Guide, Section: Administering an NDB Environment, Subsection: Managing Access Controls and Password Resets

Nutanix Support & Insights, Knowledge Base Article: "Resetting NDB GUI Password via CLI"

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

A SQL Server Always On availability-group listener needs a stable, unused static IP address that clients can use independently of the current replica role. For NDB to let the administrator select a specific listener address, the target Nutanix network must have IP address management configured so NDB can validate and allocate addresses from the managed pool. Nutanix’s SQL Server prerequisites require static addresses for the Windows cluster and availability-group listener, while the provisioning workflow exposes IP selection only on networks whose addresses are managed by NDB or Prism-based IPAM. A Windows Domain Profile supplies domain-related information, not listener address inventory. A Network Profile identifies networking settings, but enabling a setting without an address-management source is insufficient. Therefore, option B is correct. Nutanix SQL Server prerequisites

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

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) v7.5Blueprint, Section 1: Deploy NDB

Maintenance Windows simplify coordinated patching by allowing administrators to define when operating-system or database software updates should run and associate multiple database server VMs with that schedule. At execution time, NDB connects to the associated servers, performs its prechecks, identifies applicable patching tasks, and updates the database software to the recommended published software profile version. Software profile versions contain the target software or patch level, but they do not independently coordinate patch execution across multiple servers. Database Groups primarily provide collective protection, snapshot, log-management, clone, and recovery behavior for related SQL Server databases; they are not the scheduling mechanism for fleet patching. Database Cloning is unrelated to software maintenance. The official Nutanix Maintenance Window documentation states that database patching performed through a maintenance window updates databases to the recommended software profile version.

When provisioning a PostgreSQL HA Instance using NDB, the minimum and maximum number of DB server VMs that can be deployed in a cluster are 2 and 4, respectively. A PostgreSQL HA Instance is a database instance that provides high availability and fault tolerance for PostgreSQL databases using the Patroni framework. Patroni is a Python-based tool that manages PostgreSQL configuration and performs automatic failover and switchover operations. Patroni relies on a distributed consensus store, such as etcd, Consul, or ZooKeeper, to store and synchronize the cluster state and leader information. NDB supports etcd as the consensus store for PostgreSQL HA Instances. NDB allows the administrator to provision PostgreSQL HA Instances with different sizes and configurations, such as small, medium, large, or custom. The size of the PostgreSQL HA Instance determines the number of DB server VMs, the number of etcd nodes, the CPU, memory, and disk resources, and the replication factor of the database. The minimum number of DB server VMs for a PostgreSQL HA Instance is 2, which corresponds to a small size instance. This configuration provides one leader and one follower DB server VM, and one etcd node. The maximum number of DB server VMs for a PostgreSQL HA Instance is 4, which corresponds to a large size instance. This configuration provides one leader and three follower DB server VMs, and three etcd nodes. The other options are not valid for a PostgreSQL HA Instance, as they either do not provide enough redundancy or exceed the supported limit of DB server VMs. References:

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

Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.2: Configuring NDB, Topic: Provisioning PostgreSQL HA Instances

Nutanix Database Service (NDB) User Guide, Chapter 4: Provisioning Databases, Section: Provisioning PostgreSQL HA Instances

[PostgreSQL High Availability: Under the Hood – Nutanix.dev], Section: PostgreSQL HA Architecture and Components