B.   Min 2, Max 4

Explanation:
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.

B.   The administrator wants to restore to a new location and have Era apply Nutanix best practices.

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

D.   Download the PSU from Oracle support.

Explanation:
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 outof- 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.

D.   Select Update and modify the Removal schedule.

Explanation:
The Removal schedule is a feature of Nutanix Era that allows you to specify when a database clone will be automatically deleted. You can modify the Removal schedule of an existing clone by selecting the clone from the Clones page, clicking on the Update button, and changing the Removal schedule option to the desired date. This way, you can extend or shorten the lifespan of a clone as per your requirements. You do not need to remove the existing Removal schedule and add a new one, as this would be an unnecessary step. You also do not need to update the Removal schedule to the end of the month, as this would not meet the request of keeping the clone for an additional 14 days.

A.   prism Admin
• Era Super Admin
• Era Database Admin
Era Infrastructure Admin

Explanation:
Nutanix Era offers Role-Based Access Control capabilities by organically embedding them in the product. It provides the ability to add and remove users from Era, create and assign roles to users, and associate various privileges with a role1. The default roles available within Era for Role-Based Access Control are:

• prism Admin
• Era Super Admin
• Era Database Admin

Era Infrastructure Admin1 These roles allow for the management of both physical resources like IP addresses and VLANs along with database entities like databases, time-machines, clones, and so on1.

B.   Exclude the appropriate repositories on the VM prior to patching.

Explanation:
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.

A.   NTP, DNS servers, gateway, and subnet mask must be available and visible to Ere,

B.   One static IP address must be available and changed using CLI after VM deployment.

Option A: Nutanix Era requires network prerequisites like NTP, DNS servers, gateway, and subnet mask to be available and visible. These are essential for the proper functioning of the Era instance1.
Option B: One static IP address must be available and can be changed using CLI after VM deployment. This is necessary for the Era VM to communicate with other components in the network1.
Option C: While a storage container is necessary for Nutanix infrastructure, it is not a network prerequisite specifically for deploying an Era instance.
Option D: An SMTP server and details are typically used for sending notifications, but they are not a network prerequisite for deploying an Era instance. They are more related to the operational aspect post deployment.

A.   Grid home

B.   Oracle home

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

• A. Grid home2
• B. Oracle home2

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

A.   Database Agent

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.References: Nutanix Database Automation documentation, focusing on database agents and their roles in transaction log management.

C.   15

Explanation:
The NDB GUI allows an administrator to set the schedule interval for a database log catch up, which is the process of collecting transaction logs periodically from the source databases and storing them in the time machine. The shortest possible value for this interval is 15 minutes, as per the NDB documentation1. This means that the NDB time machine will capture the database logs every 15 minutes and use them for backup, restore, clone, and refresh operations.
References: Nutanix Database Management & Automation (NDMA), page 29; Nutanix Support & Insights, section “Log Catch-up”

D.   • Daily snapshot retention: 7 days
• Snapshots per Day: 2

Explanation:
The correct answer is D because it matches the requirement of taking multiple snapshots per day and retaining them for one week. Option A is incorrect because it only takes one snapshot per day, which is not enough for the administrator’s need. Option B is incorrect because it only retains the snapshots for one week, which means the older snapshots will be deleted after seven days. Option C is incorrect because it only takes two snapshots per week, which is not frequent enough for the administrator’s need.

A.   Databases

C.   Clones

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