NCP-DB Exam Dumps - Nutanix Certified Professional (NCP) Questions and Answers

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.

 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

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.

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.

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.

 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.

To install NDB on a Nutanix AHV cluster, you need to download the QCOW2 image file of NDB from the Nutanix Support Portal and upload it to Prism Element. This image file contains the NDB software and the CentOS operating system. After uploading the image, you need to create a VM from the image and configure the network settings. Then, you need to register the NDB VM with Prism Central and enable the NDB service in the settings menu. References: Nutanix Support & Insights, Professional Services: NDB Database Cloning

The NDB alert retention feature allows the database administrator to configure the duration for which the NDB alerts are stored and displayed in the NDB instance. The NDB alert retention feature supports alert retention globally, meaning that the same retention period applies to all the alerts generated by the NDB instance, regardless of the source cluster, policy, or operation. The database administrator can set the alert retention period from 1 day to 365 days, or choose to retain the alerts indefinitely. The NDB alert retention feature helps to manage the storage space and the visibility of the NDB alerts.

The NDB alert retention feature does not support retention at the individual policy, grouped policy, or registered cluster level. The NDB alert retention feature applies to all the alerts uniformly, and does not allow the database administrator to specify different retention periods for different policies or clusters.

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.

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 site123.
• 1 Cluster VIP and 1 Listener IP on the remote site123.
• 2 IPs in the local site and 1 on the remote site for the database server nodes123.

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

To change the static IP address on the NDB VM, an administrator would need to enter the NDB command line using the cerebro_cli command. The cerebro_cli command is used to access the Cerebro service, which is responsible for managing the NDB instance and its components. The cerebro_cli command can be run from the NDB VM or from any other VM that has network connectivity to the NDB VM. The cerebro_cli command has various subcommands and options to perform different tasks, such as changing the IP address, hostname, password, or certificate of the NDB VM. To change the static IP address, the administrator would need to use the cerebro_cli network update subcommand with the appropriate parameters, such as the new IP address, netmask, gateway, and DNS servers. The cerebro_cli network update subcommand also requires the administrator to provide the current password of the NDB VM for authentication. After changing the IP address, the administrator would need to restart the NDB VM for the changes to take effect. References:

• Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.2: Configure an NDB Instance
• Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.2: Configuring NDB, Topic: Changing the IP Address of the NDB VM
• Nutanix Database Service (NDB) Command Line Interface Guide, Chapter 2: Cerebro CLI, Section: cerebro_cli network update