Free and Premium Nutanix NCP-DB Dumps Questions Answers

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

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.

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

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

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.

According to the Nutanix Database Automation (NCP-DB) course, the Pre-Post Commands section allows the administrator to specify custom scripts that can be executed before or after the clone operation1. The masking script can be created on any of the VMs that have access to the source database, such as the source DB VM, the Dev VM, or the SW Profile VM2. The script should contain the commands to mask the sensitive data in the Finance database, such as replacing the real values with dummy values or encrypting the data2. The administrator can then create the clone from the Time Machine and define the post-clone option with the full path and name of the masking script1. This will ensure that the script is executed after the clone is created, and the data is masked before it is available for the development team1. The other options are not correct, as they either use the wrong field (pre-clone instead of post-clone), or do not specify where to create or store the masking script. References:

• 1: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 5
• 2: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 7

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

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

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

A stretched VLAN is a virtual network that spans across multiple Nutanix clusters and allows the communication between VMs on different clusters using the same subnet. A stretched VLAN can be used to provide high availability and load balancing for NDB components, such as HAProxy VMs, that require a virtual IP address (VIP) to be accessible from any cluster. To add a stretched VLAN across two clusters in NDB, the administrator needs to meet two prerequisites: the VLAN must be static and both clusters must be registered in NDB. A static VLAN is a VLAN that is manually created and configured by the administrator, as opposed to an IPAM VLAN that is automatically created and managed by NDB. A static VLAN can be added to a stretched VLAN in NDB, while an IPAM VLAN cannot. Both clusters must be registered in NDB before adding a stretched VLAN, as NDB needs to have the information and access to the clusters and their networks. The administrator can register the clusters in NDB using the Prism Element details, agent network configuration, and storage container information. The other option, Nutanix Cluster Management, is not a prerequisite for adding a stretched VLAN in NDB. Nutanix Cluster Management is a feature that allows the administrator to manage multiple Nutanix clusters from a single NDB UI, such as creating or deleting clusters, adding or removing nodes, or performing cluster operations. Nutanix Cluster Management is not required for adding a stretched VLAN, as the VLANs are created and configured in Prism Element, not in NDB. 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 Database Service High Availability Deployment Overview, Section: HAProxy VMs and Stretched VLANs
• [Configuring a Virtual NIC to Operate in Access or Trunk Mode - Nutanix], Section: Creating a vNIC in Access or Trunk Mode

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”

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

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

• Nutanix Database Management & Automation (NDMA) course, Module 5, Lesson 5.2 - Log Backup Management
• Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Log Backup Management

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

• Nutanix Database Management & Automation Training Course, Module 1: Introduction to Nutanix Era, Lesson 1: Nutanix Era Overview, Slide 7: NDB User Interface
• Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 1: Describe NDB Concepts, Objective 1.6: Languages

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

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

 Data Access Management (DAM) policies are a feature of NDB Multi-Cluster that allows you to control the access and availability of time machine data across different Nutanix clusters. You can use DAM policies to specify which clusters can access the time machine data of a source database, and which clusters can replicate the time machine data for backup or disaster recovery purposes. DAM policies help you to optimize the storage and network resources, as well as ensure the security and compliance of your database workloads. The purpose of DAM policies is not to register multiple Nutanix clusters in NDB, as this is done by using the Add Cluster option in the NDB settings page. The purpose of DAM policies is also not to perform snapshot operations on a single Nutanix cluster, as this is done by using the Time Machine feature in the NDB dashboard. The purpose of DAM policies is also not to remove data accessibility of a time machine across all registered Nutanix clusters in NDB, as this is done by using the Delete option in the Time Machine page. References:

• Nutanix Database Management & Automation Training Course, Module 6: Managing NDB Multi-Cluster, Lesson 2: Data Access Management Policies, Slide 3: Data Access Management Policies
• Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 6: Administer an NDB Environment, Objective 6.5: Apply procedural concepts to create Data Access Management (DAM) policies

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

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

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.

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 Era enables you to clone your source databases and refresh the database clones by using snapshots or transaction logs1. For an online retail application that requires data to be synchronized between multiple SQL Server databases, having all the databases present in the same Database Virtual Machine (DBVM) and registering them in Era with Multiple Databases as a Group with one Time Machine would be the most efficient way to fulfill this requirement1. This approach allows for clearer reporting from multiple databases at the same time for consistency at the end of each business day1.

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”

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.

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

A Network Profile is a collection of network settings that are used to provision database server VMs in NDB. A Network Profile can include one or more VLANs, IP ranges, and DNS servers. To make new VLANs available when provisioning an Oracle cluster database, you need to update the Network Profile to include the new VLANs. You can do this by editing the existing Network Profile or creating a new one with the new VLANs. You do not need to create or update the VLANs in Prism Element, as NDB can discover the VLANs configured in AHV1. References:

• Nutanix Database Management & Automation (NDMA) course, Module 2, Lesson 2.4 - Network Profiles
• Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Network Profiles
• Nutanix Certified Professional - Database Automation (NCP-DB), Section 2 - Deploy and Configure an NDB Solution

The Nutanix Era platform provides a feature called Time Machine, which is designed to manage the lifecycle of database copies and clones1. When a new table is added to the source database, the administrator should perform a Log Catch-up using the source database’s Time Machine. This action ensures that the Time Machine captures the latest state of the source database, including the newly added table1. After performing the Log Catch-up, the administrator should refresh the clone database. The refresh operation updates the clone with the latest state captured by the Time Machine, thereby publishing the new table to the clone1.

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

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.

References: Nutanix Support & Insights, section “NDB Data Access”

 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 is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention. When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de-registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze. 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: Time Machine Concepts
• Nutanix Support & Insights, TN-2101: Nutanix Database Service Time Machine Under the Hood, Section: Time Machine States and Transitions

The correct answer is A and D because these are the two Time Machine options that are available when creating a database clone in NDB. Point in time allows the user to specify a date and time to create a clone from a specific point in the database history. Snapshot allows the user to select a previously taken snapshot to create a clone from a consistent state of the database. Option B is incorrect because Restore point is not a Time Machine option, but a feature that allows the user to restore a source database to a previous point in time. Option C is incorrect because Backup is not a Time Machine option, but a feature that allows the user to backup a database to a remote location.

References: The following sources provide more information about the Time Machine options and cloning features in NDB:

• Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases Using Time Machine, Lesson 4.2: Cloning Databases
• Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 5 - Protect NDB-managed Databases Using Time Machine
• Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section 6.2: Cloning Databases
• [Nutanix Support & Insights], NDB Time Machine Under the Hood

 According to the Nutanix Database Automation (NCP-DB) learning documents, to refresh an existing DB Clone, a developer with RBAC privileges in Era needs to navigate to Databases > Clones. From there, they select the appropriate clone from the table, click Refresh, select the desired Point In Time or Snapshot, and then click Refresh12. This process allows the developer to update the cloned database3.

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 should perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, to accomplish the task of patching a MongoDB server cluster within an NDB environment. A rolling upgrade is a method of applying patches or updates to a cluster without downtime or interruption of service. The administrator can use the NDB patching feature to perform a rolling upgrade on a MongoDB server cluster, which consists of a primary member and one or more secondary members that form a replica set. The NDB patching feature allows the administrator to select the software profile version, the database parameters profile, and the network profile for the patching operation. The NDB patching feature also automates the steps of the rolling upgrade, such as:

• Step 1: The administrator initiates the patching operation on the NDB instance, and selects the MongoDB server cluster to be patched.
• Step 2: The NDB instance verifies the prerequisites and compatibility of the patching operation, and creates a pre-patch snapshot of the MongoDB server cluster.
• Step 3: The NDB instance applies the patch to the first secondary member of the MongoDB server cluster, and waits for the patching to complete successfully.
• Step 4: The NDB instance verifies the status and functionality of the patched secondary member, and repeats the patching process for the remaining secondary members of the MongoDB server cluster, one at a time.
• Step 5: The NDB instance performs a failover of the primary member to one of the patched secondary members, and applies the patch to the original primary member.
• Step 6: The NDB instance verifies the status and functionality of the patched primary member, and performs a failback of the primary member to the original primary member, if desired.
• Step 7: The NDB instance creates a post-patch snapshot of the MongoDB server cluster, and completes the patching operation.

Performing a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, is the recommended and best practice method of patching a MongoDB server cluster within an NDB environment, as it ensures the high availability, consistency, and performance of the MongoDB server cluster and the databases.

Performing a rolling upgrade, applying the patch to the primary member first, followed by the secondary members, is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to the primary member first would disrupt the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to restore the MongoDB server cluster to a functional state.

Applying the patch to all nodes at once is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to all nodes at once would require shutting down the entire MongoDB server cluster, and would expose the MongoDB server cluster and the databases to potential errors, failures, and corruption during the patching process.

Disabling the replica set while patching is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Disabling the replica set while patching would break the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to re-enable the replica set and restore the MongoDB server cluster to a functional state.

References:

• Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 11-12, 15-16.
• Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.3: Nutanix Era Patching, slides 5-9.
• Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.4: Nutanix Era Patching Lab, slides 5-10.
• Nutanix Database Management & Automation Training Course, Module 7: Nutanix Era Troubleshooting, Lesson 7.1: Nutanix Era Troubleshooting, slide 6.

 The database parameters profile is used to define the initialization variables for different types of database engines and workloads, such as OLTP and DW. The database parameters profile allows the database administrator to customize the configuration settings for each database engine, such as Oracle, SQL Server, PostgreSQL, and MySQL. The database parameters profile can also be applied to different database operations, such as provisioning, cloning, and patching. The database parameters profile helps to optimize the performance and functionality of the databases according to the specific requirements and best practices of each database engine and workload.

The software profile version is used to define the software version and edition for each database engine, such as Oracle 19c Enterprise Edition or SQL Server 2019 Standard Edition. The software profile version is required for provisioning new databases and patching existing databases. The software profile version helps to ensure the compatibility and compliance of the databases with the supported software versions and editions.

The network profile is used to define the network configuration and security settings for the database server VMs and the databases, such as the IP address, subnet mask, gateway, DNS, firewall rules, and SSL certificates. The network profile is required for registering new database server VMs and provisioning new databases. The network profile helps to ensure the connectivity and protection of the database server VMs and the databases within the network environment.

The compute profile is used to define the compute resources and storage policies for the database server VMs and the databases, such as the CPU, memory, disk size, disk type, compression, deduplication, and replication factor. The compute profile is required for provisioning new databases and cloning existing databases. The compute profile helps to ensure the availability and efficiency of the database server VMs and the databases within the Nutanix cluster.

References:

• Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slides 6-9.
• Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 5-8, 11-12, 15-16.

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

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

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

NDB sends notifications when alerts are generated via email. The email notifications can be configured to send to one or more recipients, and can be customized to include the alert severity, category, description, and resolution steps. The email notifications help to inform the database administrator and other stakeholders about the status and issues of the NDB-managed databases and operations.

NDB does not send notifications via SNMP, APIs, or Pulse. SNMP is a protocol for collecting and organizing information about managed devices on a network. APIs are interfaces for communicating and exchanging data between different applications or systems. Pulse is a feature of the Nutanix cluster that collects and sends diagnostic and usage data to Nutanix for analysis and support.

References:

• Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment, Lesson 3.2: Nutanix Era Deployment, slide 11.
• Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slide 6.
• Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.2: Nutanix Era Alerts and Notifications, slides 5-7.

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.

 To increase storage for a MongoDB database provisioned using NDB, the administrator needs to use the extend_storage parameter in the input file for the NDB CLI. This parameter specifies the amount of additional storage to be added to the database server VM in GB. For example, if the current storage size is 100 GB and the administrator wants to increase it to 150 GB, the input file should contain the following line:

extend_storage: 50

The other parameters are not relevant for this operation. The update parameter is used to update the database software version, the database parameter is used to specify the database name, and the data_percent parameter is used to specify the percentage of data to be copied during a clone operation. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [Nutanix Database Automation User Guide].