Nutanix NCP-DB-6.5 Practice Test - Questions Answers, Page 14

According to the Nutanix Database Automation (NCP-DB) Learning documents12, to clone a source production database to an existing development server, the following actions must be taken:

A)The development server must be registered by Era in order to receive the clone1. This is because Nutanix Era is a database management tool that manages the lifecycle of databases and their copies. Registering the development server with Era allows it to manage the database on that server.

D)The development server must have the IP and credentials provided during cloning2. This is necessary for Era to access the development server and perform the cloning operation. The IP address and credentials are used to establish a connection to the development server. Without these details, Era would not be able to access the server and perform the cloning operation.

In the context of Nutanix Database Automation (NCP-DB), when there are insufficient resources on a development cluster, the administrator can adjust theComputeandDatabase Parametersprofiles to make the copy fit within the available resources1. The Compute profile includes settings related to CPU and memory resources, which can be adjusted to fit within the available resources.The Database Parameters profile includes settings that control the behavior and resource usage of the database, which can also be adjusted to optimize resource usage1.

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.

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]

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.

To register an Oracle Database Server VM to Era in Nutanix Database Automation (NCP-DB), certain dependencies must be met.One of these is that SUDO NOPASS access is required1. This allows the Era service to perform necessary operations on the Oracle Database Server VM.As for assigning a static IP address to the Era VM on ESXi, you can use the vSphere Client to configure static IP settings2. However, this is not directly related to the registration of an Oracle Database Server VM to Era. Please note that these answers are based on the information available as of my last update in 2021 and may need to be verified with the most recent Nutanix Database Automation (NCP-DB) documentation or resources.

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.

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.

To create a software profile version for a newly-released Oracle ISc patch, an administrator should follow these steps:

Download the required patch from MyOracle Support1. This is because Oracle patches are typically available from MyOracle Support, not Microsoft Support.

Apply the patch to the Oracle Home/Grid Home on a cloned VM of the gold image using OPatchAuto1. OPatchAuto is a utility provided by Oracle that automates the process of applying patches to a database.

Ensure success of patch application1. It's important to verify that the patch has been applied successfully to avoid any issues down the line.

Create a new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era GUI1. This step is necessary to ensure that the new patch is included in the software profile.

Mark the original patch profile as hidden1. This step is optional but can be useful for keeping the software profile clean and organized.

Please note that these answers are based on the information available as of my last update in 2021 and may need to be verified with the most recent Nutanix Database Automation (NCP-DB) documentation or resources.