Configuring VM Host Affinity in a Nutanix AHV-powered cluster ensures that VMs are placed on specific hosts to optimize performance or HA. However, after a host failure, if database VMs cluster on a single remaining host, it indicates that the affinity rules alone are insufficient to maintain high availability (HA) during failover scenarios. To prevent this, the administrator should configure anti-affinity rules, which dynamically ensure that VMs (e.g., database server VMs) are spread across multiple hosts. Anti-affinity rules override default VM placement behavior during failover, reducing the risk of a single point of failure by keeping VMs separated even after a host outage.

Option A (Assign additional backup VMs on the same host) is incorrect because placing backups on the same host increases risk rather than mitigating it.

Option B (Increase affinity zones) is incorrect as " affinity zones " is not a standard Nutanix term in this context, and it does not address dynamic VM separation.

Option C (Configure automatic host failover in Prism Central) is incorrect because while failover is managed by AHV, it does not inherently prevent VMs from clustering without specific rules.

Option D is correct as anti-affinity rules proactively distribute VMs, enhancing HA in failure scenarios.

This approach leverages Nutanix AHV’s VM placement policies to ensure resilience.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring VM Affinity and Anti-Affinity

Nutanix AHV Administration Guide, Section: VM High Availability and Placement Rules

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

In NDB, database groups are used to manage multiple Microsoft SQL Server databases collectively, enabling centralized administration and protection policies. The statement " Databases within a database group can share multiple Time Machine configurations " is true. A Time Machine in NDB manages snapshots and log backups for recovery, and a database group can be associated with multiple Time Machine configurations to support different retention policies or recovery point objectives (RPOs) for the databases within the group. This flexibility allows tailored data protection strategies.

Other options are incorrect:

A. Microsoft recommends 35 databases within a single database group : There is no specific Microsoft recommendation for this limit; NDB imposes its own constraints based on performance and resource usage.

C. NDB supports one database group per database server VM or database server cluster : NDB allows multiple database groups per server or cluster, depending on configuration.

D. Databases within a database group must be all of the same size : NDB does not enforce uniform database sizes within a group.

Thus, the verified answer is B , reflecting NDB’s Time Machine flexibility.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.6: Managing Database Groups.

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

Nutanix NDB Administration Guide: " Database Groups and Time Machine Configurations " section.

In Nutanix Database Automation (NCP-DB), when an administrator logs into Era and sees a message “Update Available” on the Status of the Software Profile Version, it indicates that a newer version of the software profile is available 1 .  The administrator should manually update the software profile to the latest version 1 2 .  This process ensures that the database VM is running the most recent and compatible version of the software 1 2 .

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) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v6.10).

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

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

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

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

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

The SQL Server authentication mode to use for the databases

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

Nutanix Database Service (NDB) supports high availability (HA) instances for certain relational database management systems (RDBMS). Among the listed options, NDB natively supports Oracle and PostgreSQL for HA configurations, enabling features like replication and failover. These databases are well-integrated with NDB’s Time Machine and HA frameworks.

Option A (MongoDB) is incorrect because MongoDB is a NoSQL database, not an RDBMS, and is not supported for HA instances in NDB.

Option B (MariaDB) is incorrect because, while MariaDB is an RDBMS, it is not currently supported for HA instances in NDB v6.10.

Option C (Oracle) is correct as NDB supports Oracle in HA mode with features like Data Guard integration.

Option D (PostgreSQL) is correct as NDB supports PostgreSQL HA with streaming replication.

Note: The typo " PostgreSGL " in the question is assumed to mean " PostgreSQL " based on context.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section: Supported RDBMS for HA

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

The correct answer is D. When setting up a 3-node MSSQL Server AG with two database server VMs on a local site and a third database server VM on a remote site, the network at each site will require the following IP addresses:

1 Cluster VIP and 1 Listener IP on the local site 1 2 3 .

1 Cluster VIP and 1 Listener IP on the remote site 1 2 3 .

2 IPs in the local site and 1 on the remote site for the database server nodes 1 2 3 .

This configuration ensures that each node in the cluster has a unique IP address, and each cluster and listener also has a unique IP address.  This is necessary for the proper functioning of the cluster and to ensure that all nodes can communicate with each other and with clients 1 2 3 .

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

 Nutanix Era supports a variety of database engines, including Oracle, PostgreSQL, MySQL, and Microsoft SQL Server 1 .  However, when it comes to rolling back a patch using the Command Line Interface (CLI), this feature is specifically supported for the Oracle database engine 1 .  This allows for efficient validation of critical database updates and simplifies database rollback 1 .  Please note that while Era does provide support for other database engines, the ability to rollback a patch using CLI is currently specific to Oracle 1 .

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) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.2: Manage Alerts (applicable to v6.10).

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