Nutanix NCP-DB Exam Dumps

The administrator can add a stretched VLAN in NDB using either static or dynamic VLANs. A stretched VLAN is a VLAN that spans across multiple Nutanix clusters, and allows the NDB-managed databases to communicate and migrate between different clusters. A static VLAN is a VLAN that is manually configured and assigned to the database server VMs and the databases by the administrator. A dynamic VLAN is a VLAN that is automatically configured and assigned to the database server VMs and the databases by the NDB instance, using the Nutanix Calm orchestration service. Both static and dynamic VLANs can be used to create a stretched VLAN in NDB, as long as they have the same VLAN ID and network configuration across the clusters.

The administrator cannot add a stretched VLAN in NDB using only VLANs that are not managed in NDB. A VLAN that is not managed in NDB is a VLAN that is configured and assigned to the database server VMs and the databases outside of the NDB instance, using the Nutanix Prism web console or other tools. A VLAN that is not managed in NDB cannot be used to create a stretched VLAN in NDB, as it is not recognized or controlled by the NDB instance.

Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slide 8.

Nutanix Database Management & Automation Training Course, Module 6: Nutanix Era Disaster Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 6-7.

To add Time Machine data access to a Nutanix cluster, the first step is to register the cluster in NDB. This will allow NDB to discover and manage the databases and snapshots on the cluster. You can register multiple Nutanix clusters in NDB using the Add Cluster option in the NDB settings page. You can also specify the cluster role, such as source, target, or both, depending on the data access and replication needs. Enabling or disabling multi-cluster in NDB is not the first step, as this is a global setting that affects the entire NDB instance. Deleting the TM data from the source database is not the first step, as this will remove the data protection and availability of the database.Reference::

Nutanix Database Management & Automation Training Course, Module 6: Managing NDB Multi-Cluster, Lesson 1: NDB Multi-Cluster Overview, Slide 5: Registering Nutanix Clusters

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 6: Administer an NDB Environment, Objective 6.4: Apply procedural concepts to add Nutanix clusters to NDB

Nutanix Era leverages the Nutanix time-efficient snapshots to create the clones1.These database clones are highly space-efficient, consuming near-zero bytes by having only the further writes constituting to its size1. Therefore, an administrator would find the total space being used by all Era clones for a specific database under the Cloning widget on the Databases > Clones database summary page. The other options do not specifically provide information about the total space used by all Era clones for a specific database. Therefore, the correct answer is A. Under the Cloning widget on the Databases > Clones database summary page.

In Nutanix Era, aVolume Groupis 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 leverage the Oracle restore feature within Nutanix Database Service (NDB) for a Real Application Clusters (RAC) database, the administrator must ensure that the database is registered with NDB prior to initiating the restoration operation. Registration allows NDB to recognize the RAC database, manage its metadata, and perform operations like restore using Time Machine snapshots or backups. Without registration, NDB cannot access the necessary configuration details or protection data, rendering the restore feature unavailable.

Option A (Ensure the database is in a Down state) is incorrect because the database state (Up or Down) is not a prerequisite for initiating a restore; the process handles state transitions.

Option B (Ensure the database is registered with NDB) is correct as registration is the foundational requirement for NDB to manage and restore the RAC database.

Option C (Ensure the database is in an Up state) is incorrect because an Up state is not required; restore can proceed regardless of the current state.

Option D (Ensure more than one node of the RAC is reachable) is incorrect because while RAC node availability is important for HA, it is not a mandatory prerequisite for the restore operation itself.

This ensures the restore process can proceed with the necessary NDB oversight.

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring RAC Databases

Nutanix Support & Insights, Knowledge Base Article: 'Preparing Oracle RAC for Restore in NDB'

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine