QUESTION: 69

What is the first step to add Time Machine (TM) data access to a Nutanix cluster?

Enable multi-cluster in NDB.
Disable multi-cluster in ND8.
Register the required Nutanix clusters in ND8.
Delete the TM data from the source database.

Answer(s): C

Explanation:

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

Reveal Solution Next Question

QUESTION: 70

An administrator is adding a stretched VLAN in NDB.
Which VLAN type(s) will satisfy this task?

Only VLANs that are not managed in NDB
Only static VLANs that are managed in NDB
Only dynamic VLANs
Both static and dynamic VLANs

Answer(s): D

Explanation:

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.

Reference:

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.

Reveal Solution Next Question

QUESTION: 71

An administrator needs to add a stretched VLAN across two clusters in NDB Which two prerequisites should be met prior to completing this action? (Choose two.)

VLAN must be IPAM.
VLAN must be static.
Both clusters must be registered in NDB.
Nutanix Cluster Management must be enabled.

Answer(s): B,C

Explanation:

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.

Reference:

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

Reveal Solution Next Question

QUESTION: 72

A user accidentally drops a table in the database at 10:42pm and the NDB administrator is tasked with restoring the table.
The snapshot schedule is set for every 30 minutes and the log catchup is set for every 15 minutes.
The last available snapshot is at 10:30pm.
What is the optimal path to restore the table back with minimum data loss?

Restore the 10:42pm snapshot.
Restore using point in time till 10:41pm.
Restore using point in time till 10:42pm.
Restore the 10:30pm snapshot.

Answer(s): C

Explanation:

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.

Reference:

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

Reveal Solution Next Question

Free NCP-DB-6.5 Exam Braindumps (page: 19)

QUESTION: 69

Explanation:

Reference:

QUESTION: 70

Explanation:

Reference:

QUESTION: 71

Explanation:

Reference:

QUESTION: 72

Explanation:

Reference:

Exam Discussions & Posts