An administrator is tasked with auditing NDB SLAs. What data will the administrator be reviewing?
Correct Answer: C
NDB SLAs are service level agreements that define the data protection and recovery objectives for NDB-managed databases. NDB SLAs consist of data retention policies that specify how long the snapshots and log backups of a database are kept in the Time Machine. Data retention policies can be customized to meet different business and compliance requirements, such as daily, weekly, monthly, or yearly retention periods.NDB SLAs also determine the frequency and schedule of the snapshots and log backups, as well as the storage location and replication options. An administrator who is tasked with auditing NDB SLAs will be reviewing the data retention policies of each database and Time Machine, as well as the snapshot and log backup history and status. The administrator will also be able to monitor the storage usage and performance of the NDB SLAs, and modify or delete the SLAs as needed. The other options are not part of the NDB SLAs, but rather separate features or concepts of NDB. Snapshot schedules are the intervals at which NDB takes snapshots of the databases, which are determined by the SLAs. Clone management is the process of creating, refreshing, or deleting database clones from the Time Machine. Recovery time objective (RTO) is the maximum acceptable time for restoring a database after a failure, which is influenced by the SLAs, but not defined by them. References: * Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 5 - Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies * Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: SLA Concepts * Nutanix Database Service (NDB) User Guide, Chapter 6: SLAs, Section: SLA Overview
Question 7
Refer to the exhibit. An administrator attempts to provision their first clustered database environment with NDB. The operation fails with the Operation Error shown in the exhibit. Which database engine was being deployed during this operation?
Correct Answer: B
The error message in the exhibit indicates that the operation failed during the "Create and Register Database Server VMs" step because "Provisioning of all the observers simultaneously took more than two hours." This type of error is associated with MySQL, as it involves observers which are a part of MySQL Group Replication, used for ensuring high availability1. The other options are not related to the error message, as they do not use observers or Group Replication for clustering. References: * 1: Nutanix Database Automation (NCP-DB) course, Module 5: Database High Availability, Lesson 5.2: MySQL Group Replication, slide 7
Question 8
An administrator needs to restore databases provisioned with a shared disk configuration on Windows Storage Spaces What happens when NDB runs the restore operation?
Correct Answer: A
When an administrator needs to restore databases provisioned with a shared disk configuration on Windows Storage Spaces in Nutanix Database Service (NDB), the restore operation focuses on the disks associated with the database. Windows Storage Spaces provides a virtualized storage layer, and NDB manages the restoration by reverting or recovering the specific disks that host the database files and logs. This ensures that the database is restored to its previous state using the snapshot or backup data, while preserving the shared disk configuration integrity. NDB does not replace the source volume or perform additional operations like tail log backups unless explicitly configured. * Option A (NDB restores the disk that are associated with the database) is correct as it accurately describes NDB's restore behavior for shared disk setups. * Option B (NDB copies the DB files to be restored to the source volume) is incorrect because NDB restores the entire disk state, not just copying files to the source. * Option C (NDB replaces the source volume with the snapshot volume) is incorrect because NDB restores data to the existing volume, not replacing it entirely. * Option D (NDB performs Tail Log backup to backup any remaining logs) is incorrect because tail log backups are not automatically part of the restore process unless specified for point-in-time recovery. This approach ensures compatibility with Windows Storage Spaces configurations. References * Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring Databases with Shared Disks * Nutanix Support & Insights, Knowledge Base Article: "Restoring Windows Storage Spaces in NDB" * Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
Question 9
Which two options can NDB leverage to refresh a database clone? (Choose two.)
Correct Answer: B,C
NDB can leverage snapshots and transaction logs to refresh a database clone to the latest state of the source database. Snapshots are point-in-time copies of the database that are stored on the Nutanix cluster. Transaction logs are records of the changes made to the database after the snapshot was taken. NDB can use either snapshots or transaction logs, or a combination of both, to refresh a database clone. Cerebro logs and templates are not used for refreshing database clones. Cerebro logs are used for log catch-up operations, which are different from refresh operations. Templates are used for provisioning new databases, not for refreshing existing ones. References: * Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.3 - Refreshing Clones * Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Clone Database Management
Question 10
Which statement is true regarding the NDB alert retention feature?
Correct Answer: A
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.
