Sure Pass Exam NCP-DB PDF

A SQL Server Database Group in NDB is a logical protection construct for databases that have common recovery-point and retention requirements. The databases are managed by one collective Time Machine and SLA, allowing NDB to coordinate snapshots and log backups and reduce Time Machine sprawl. However, grouping does not merge all database files into one common virtual-disk set. Each database retains its own set of storage disks while participating in the group-level protection workflow. The group also does not force databases onto different Always On Availability Group nodes, and it does not prevent an administrator from restoring or cloning an individual database. Those facts eliminate A, B, and C. Option D correctly describes separate per-database storage combined with centralized Time Machine management. Nutanix NDB Database Groups

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. References:

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

According to the Nutanix Database Automation (NCP-DB) course, the ports 3205 and 3260 are required for iSCSI connections between the NDB server and the Controller VMs1. Port 3205 is used for the NDB iSCSI initiator service, which initiates the iSCSI sessions and sends SCSI commands to the Controller VMs1. Port 3260 is used for the iSCSI target service, which listens for incoming iSCSI requests and provides access to the storage devices on the Controller VMs1. The other options are not related to iSCSI connections. Port 22 is used for SSH, port 9440 is used for Prism Central, port 80 is used for HTTP, port 443 is used for HTTPS, port 5985 is used for WinRM HTTP, and port 5986 is used for WinRM HTTPS2. References:

1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.2: Database Engine Installation, slide 13

2: Nutanix NCP-DB Certification Exam Sample Questions, Question 18, Answer

NDB Time Machine is the data-protection and recovery capability designed for this requirement. It combines application-consistent Nutanix storage snapshots with captured database transaction logs. The snapshot supplies a consistent recovery baseline, and the retained logs can be replayed to the requested time, enabling point-in-time recovery after an accidental modification while avoiding database reinstallation. This storage-efficient workflow is designed to reduce recovery time and minimize operational disruption. A Software Profile supplies standardized operating-system and database binaries for provisioning or patching; it does not preserve transactional recovery history. A Database Parameters Profile controls engine settings. Database cloning creates another usable copy and may use Time Machine data, but it is not the primary in-place recovery capability requested. Therefore, the correct answer is B, Time Machine. Nutanix Time Machine data protection

================