Nutanix NCP-DB Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Exam Practice Test

According to the NDB documentation, the NDB patching process for MongoDB Server Cluster follows these steps1:

• NDB identifies the primary member of the MongoDB Server Cluster and patches it first.
• NDB triggers a failover to elect a new primary member from the remaining secondary members.
• NDB patches the former primary member, which becomes a secondary member after the failover.
• NDB patches the remaining secondary members one by one.
• NDB verifies the patching status and the cluster health.

This process ensures that the MongoDB Server Cluster always has a primary member available to handle write operations, while minimizing the downtime and the impact on the cluster performance.

References: Nutanix Support & Insights, section “Patching a MongoDB Server Cluster”

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.

References: 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

The correct answer is B because it allows the administrator to create a custom role with the specific privileges that the Jr DBA user needs, and then assign that role to the user. This way, the administrator can control the access level of the Jr DBA user without affecting the existing roles or users in NDB. Option A is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then adding more privileges, which is unnecessary and redundant. Option C is incorrect because it involves creating a user for the Jr DBA, but not assigning a role to the user, which means the user will not have any privileges in NDB. Option D is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then removing some of the privileges, which is inefficient and risky.

References: The following sources provide more information about the user roles and privileges in NDB:

• Nutanix Database Management & Automation (NDMA) course, Module 8: Administering an NDB Environment, Lesson 8.6: Managing Access Controls in NDB
• 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.6: Managing Access Controls in NDB

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

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

• Nutanix Database Management & Automation (NDMA) course, Module 5: Patching Databases Using NDB, Lesson 5.2: Creating and Modifying Software Profiles
• Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 4 - Operate and Maintain an NDB Environment
• Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.2: Creating and Modifying Software Profiles
• Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.3: Testing and Publishing Database Patches

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

An NDB compute profile defines the CPU and memory resources for the database server VMs that are provisioned using NDB. It does not include any information about the network, domain, or software of the database server VMs. Those are specified in separate profiles, such as network profile, domain profile, and software profile.

References: Nutanix Support & Insights, section “NDB Compute”

Nutanix Era (NDB) utilizes DEFAULT_008 SLAs with varying frequencies for snapshots and log backups to achieve different recovery point objectives (RPOs). Here's how they compare:

• DEFAULT_008 GOLD SLA: Typically has frequent log backups (e.g., every 15 minutes) and snapshots every few hours. This is designed for critical databases with very low RPOs.
• DEFAULT_008 SILVER SLA: Offers a balance between protection and resource usage. Log backups might occur every hour with snapshots less frequently. This SLA is often suitable for databases requiring a good RPO without being overly resource-intensive.
• DEFAULT_008 BRONZE SLA: Has less frequent log backups (e.g., every few hours) and less frequent snapshots. This is used for databases with less stringent RPO requirements.
• DEFAULT_008 BRASS SLA: This has infrequent log backups and is usually considered the least protective SLA with the longest potential RPO

Reasoning:

Since the requirement is to have at least a 7-day log recovery period, any SLA with more frequent log backups than daily is excessive. The DEFAULT_008 SILVER SLA, with its hourly log backups, easily satisfies this requirement, offering the ability to restore to a point in time within the last hour of the past seven days.

References:

• Nutanix Era User Guide/SLA Management: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-NDB-User-Guide-v2_5:top-sla-management-c.html ]

According to the Nutanix Database Automation (NCP-DB) learning documents, an administrator can change the snapshot schedule for a given database by selecting the Time Machine, then under Action, select Update and define an appropriate schedule1. This is because the Time Machine in Nutanix Era allows you to specify the number of backups or snapshots the time machine should take, the time of day it takes those snapshots, and the day of the week it takes weekly or monthly backups1. These options help you build a complete schedule of time machine capture operations1. Even if the Time Machine is in a paused state, the administrator can still update the schedule1. Cloning the Time Machine or the database is not necessary for changing the snapshot schedule1.

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

References:

• Nutanix Database Automation (NCP-DB) Course Details, Section 4.2: NDB Linux OS Patching
• Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.2: Perform Linux OS Patching
• Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.2: NDB Linux OS Patching
• Nutanix Database Automation (NCP-DB) User Guide, Section 4.5: Patch Linux OS Software

Nutanix Era is a database management system that provides API endpoints for automation and integration with external applications. These API calls are typically made over HTTPS for security, and the standard ports for HTTPS are 443 and 94401. Please note that the actual ports used can depend on the specific configuration of the Nutanix Era system. It’s always a good idea to check the system’s documentation or consult with the system administrator for the most accurate information.

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

 The 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.

References: The following sources provide more information about the SLA retention policies and how to create and modify them in NDB:

• Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases Using Time Machine, Lesson 4.1: Creating and Modifying SLA Retention Policies
• Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 5 - Protect NDB-managed Databases Using Time Machine
• Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section 6.1: Creating and Modifying SLA Retention Policies

The Nutanix Era API documentation is available on the Nutanix.dev API Reference page12. This documentation outlines the operations that are possible with the Era APIs2. In addition to the API reference, the NutanixDev code samples repo provides working code that implements the practices shown in the documentation1. The Era API Explorer is another resource that provides a comprehensive view of the available APIs, allowing users to interactively explore and test the APIs. However, there is no mention of a specific “Era GitHub API Repository” or the “Nutanix Support Portal” being used as a reference resource for Nutanix Era APIs in the provided resources. Therefore, the correct answers are B. Nutanix.dev API Reference and C. Era API Explorer.

The correct answer is D because it allows the administrator to make the profile available to all users without requiring any additional permissions or roles. A profile is a collection of settings that define how NDB manages a database server or a database. By default, a profile is only available to the user who created it and the Database Admin role. To make a profile available to all users, the administrator can update the profile and set the available state to All. This will enable all users to view and use the profile for their database operations. The other options are not correct because they either require additional steps or do not achieve the desired outcome. Option A is not correct because creating an Access Control role with the Create Profile right and assigning it to all users will only allow them to create their own profiles, not use the existing one. Option B is not correct because creating an Access Control group with the desired users and granting it the Database Admin role will only make the profile available to those users, not all users. Option C is not correct because updating the profile and setting the status to Published will not change the availability of the profile, only the state of the profile. A published profile is a profile that has been tested and verified by the administrator and is ready for use. A draft profile is a profile that is still under development or testing and is not ready for use. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Certified Professional - Database Automation (NCP-DB) datasheet

 The optimal path to restore the table back with minimum data loss is to use the point in time restore feature of NDB, which allows the administrator to restore the database to a specific point in time based on the available snapshots and logs1. By restoring using point in time till 10:42pm, the administrator can recover the table just before it was dropped by the user, and minimize the data loss to the least possible amount1. The other options are not optimal, as they either involve restoring an older snapshot, which may result in more data loss, or restoring a non-existent snapshot, which is not possible. References:

• 1: Nutanix Database Automation (NCP-DB) course, Module 6: Database Recovery, Lesson 6.2: Point in Time Restore, slide 5

• 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.

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

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

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

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

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

To create an NDB Software Profile Version for PostgreSQL, it is required to have an installer package for the database software. This package forms the basis of the software profile, enabling the deployment and management of PostgreSQL instances.References: Nutanix Database Automation documentation, particularly in the area of software profile creation and management for PostgreSQL.

• Option A: On the Era Dashboard Database Summary Table under Source Database. The dashboard provides a summary of the databases, including their sizes1.
• Option B: Under the Capacity widget on the Database Server VMS > List database summary page. While this might provide information about the capacity, it does not specifically provide the size of a Source Database.
• Option C: On the Databases > Sources table. This table provides detailed information about the databases, including their sizes1.
• Option D: On the Profiles > Database Parameters list for the assigned DB Parameter Profile. This list provides parameters for the database but does not provide the size of a Source Database.

 Nutanix Database Service (NDB) supports automated minor version upgrades for PostgreSQL1. Before applying the patch, the administrator should create a new software profile2. This is because the software profile contains the database engine binaries and other software required to run the database engine2. Therefore, to apply a minor version upgrade, a new software profile with the updated binaries needs to be created2. Once the new software profile is created, it can be used to patch the PostgreSQL database2.

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 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

Nutanix Era is a database management solution that automates and simplifies database administration tasks such as provisioning, patching, cloning, and backup. In the event of a database crash, the most effective way to minimize data loss and reduce restore time is to perform a restore of the source database by selecting the most recent point in time and including the Tail log Backup12.

The Tail log Backup includes all the transactions that have occurred since the last transaction log backup, which helps to minimize data loss. By selecting the most recent point in time for the restore, the administrator ensures that the database is restored to the state it was in just before the crash, thereby reducing the amount of data that needs to be reprocessed or reentered12. This approach aligns with the Nutanix Era’s capabilities and best practices for database recovery12.

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.

To register a PostgreSQL database server VM with a database on NDB, the database data and log files must be located on a separate mount point from the operating system and the binary installation. This is because NDB uses the mount point as the identifier for the database server VM and the database. If the data and log files are on the same mount point as the operating system or the binary installation, NDB will not be able to recognize them as a valid database server VM or database. Therefore, the administrator should create a separate mount point for the data and log files and specify it during the registration process. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [How to Allow Remote Access to PostgreSQL database], [5 Ways to Host PostgreSQL Databases], [Starting the Database Server].

Nutanix Database Automation (NCP-DB) simplifies database provisioning using predefined profiles customized to your environment. Software profiles, which are templates of the OS and database engine, allow you to maintain consistent software versions1. You then use additional profiles to customize that deployment1.

NDB supports SMTP server configuration for sending email notifications and alerts. SMTP server configuration requires specifying the SMTP server address, port, username, password, and encryption method. The encryption method determines how the email messages are secured during transmission. NDB supports two encryption methods for SMTP server configuration: TLS and SSL.

TLS (Transport Layer Security) is a protocol that encrypts and authenticates data between the email client and the SMTP server. TLS can operate in two modes: explicit and implicit. In explicit mode, the email client and the SMTP server negotiate the encryption method and parameters after establishing a plain text connection. This mode typically uses port 587. In implicit mode, the email client and the SMTP server assume that the connection is encrypted from the start, without any negotiation. This mode typically uses port 465.

SSL (Secure Sockets Layer) is a predecessor of TLS that also encrypts and authenticates data between the email client and the SMTP server. SSL operates in implicit mode only, and uses port 465 by default. SSL is less secure than TLS, but it is still widely used and supported by many email providers.

S/MIME (Secure/Multipurpose Internet Mail Extensions) is a standard that encrypts and signs email messages at the application layer, rather than the transport layer. S/MIME requires the use of digital certificates and public key cryptography to ensure the confidentiality and integrity of email messages. S/MIME is not a valid encryption method for SMTP server configuration, as it does not affect the connection between the email client and the SMTP server.

IPsec (Internet Protocol Security) is a suite of protocols that secures IP packets at the network layer, rather than the application or transport layer. IPsec can encrypt and authenticate data between any two IP endpoints, such as routers, firewalls, or hosts. IPsec is not a valid encryption method for SMTP server configuration, as it does not apply to the specific protocol or port used by SMTP.

References:

• Nutanix Database Automation (NCP-DB) Course Details, Section 1.4: NDB Alerts and Notifications
• Nutanix Database Automation (NCP-DB) Certification Details, Objective 1.4: Configure NDB Alerts and Notifications
• Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 1.4: NDB Alerts and Notifications
• [Nutanix Database Automation (NCP-DB) User Guide], Section 1.4: Configure SMTP Server Settings

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

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.

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.

NDB can leverage snapshots and transaction logs to refresh a database clone to the latest state of the source database. Snapshots are point-in-time copies of the database that are stored on the Nutanix cluster. Transaction logs are records of the changes made to the database after the snapshot was taken. NDB can use either snapshots or transaction logs, or a combination of both, to refresh a database clone. Cerebro logs and templates are not used for refreshing database clones. Cerebro logs are used for log catch-up operations, which are different from refresh operations. Templates are used for provisioning new databases, not for refreshing existing ones. References:

• Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.3 - Refreshing Clones
• Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Clone Database Management

 The correct answer is A because NDB handles the database restore operation by copying the specific database files from the snapshot volume to the source volume, without affecting the other databases that share the same source volume. NDB uses a copy-on-write mechanism to create snapshots and clones, which means that only the changes made to the database files are stored in the snapshot or clone volume, while the original files are kept in the source volume. Therefore, when restoring a source database from a snapshot, NDB only needs to copy the specific database files that have been modified since the snapshot was taken, and overwrite them on the source volume. The other options are not correct because they either cause data loss or unnecessary data transfer. Option B is not correct because replacing the source volume with specific db disks would erase the other databases that share the same source volume, which is not desirable. Option C is not correct because replacing the source volume with the snapshot volume would also erase the other databases that share the same source volume, as well as any changes made to the source database after the snapshot was taken, which is not desirable. Option D is not correct because copying all database files to the source volume would be inefficient and unnecessary, as only the modified files need to be copied, and the other files are already present on the source volume. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, [Nutanix Support & Insights]

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

References:

• Nutanix Database Automation (NCP-DB) Course Details, Section 2.3: Provisioning Oracle Databases
• Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.3: Provision Oracle Databases
• Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.3: Provisioning Oracle Databases
• [Nutanix Database Automation (NCP-DB) User Guide], Section 2.3: Provision Oracle Databases

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.References: Nutanix Database Automation documentation, focusing on log management and catch-up operation settings.

The Alerts dashboard in Nutanix displays alert messages with three severity levels: Critical, Warning, and Info1. These severity levels help users understand the importance and urgency of each alert, allowing them to prioritize their responses accordingly1.

 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

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

• Nutanix Certified Professional - Database Automation (NCP-DB), Section 5 - Protect NDB-managed Databases Using Time Machine
• Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 9, Objective 5.6
• Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.2 - Data Access Management

The default continuous recovery for the Gold SLA in Era Time Machine is 30 days1. This means that the system keeps a continuous recovery point for the last 30 days, allowing you to restore your database to any point within this period1.

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.

References:

• 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