An administrator is tasked with auditing NDB SLAs. What data will the administrator be reviewing?
Answer(s): 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.
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 policiesNutanix 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
A development team has requested that an administrator provide them a copy of the production Finance database. The business requires that any financial data is masked before going into development.How should the administrator create a clone with masked data for the development environment?
Answer(s): B
According to the Nutanix Database Automation (NCP-DB) course, the Pre-Post Commands section allows the administrator to specify custom scripts that can be executed before or after the clone operation1. The masking script can be created on any of the VMs that have access to the source database, such as the source DB VM, the Dev VM, or the SW Profile VM2. The script should contain the commands to mask the sensitive data in the Finance database, such as replacing the real values with dummy values or encrypting the data2. The administrator can then create the clone from the Time Machine and define the post-clone option with the full path and name of the masking script1. This will ensure that the script is executed after the clone is created, and the data is masked before it is available for the development team1. The other options are not correct, as they either use the wrong field (pre-clone instead of post-clone), or do not specify where to create or store the masking script.
1: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 52: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 7
Which statement best describes what happens when a 3rd-party backup tool is chosen to manage log backups for Microsoft SQL in NDB?
NDB supports two modes of log backup management for Microsoft SQL databases: NDB-managed and 3rd-party managed. In the NDB-managed mode, NDB takes full control of the log backups and stores them in the Cerebro log location. In the 3rd-party managed mode, NDB allows the use of external backup tools to backup the logs from the database log destination. However, NDB still needs to capture the logs for its own operations, such as point-in-time recovery, clone refresh, and log catch-up. Therefore, NDB will periodically scan the database log destination and copy the logs to the Cerebro log location. This process requires that the log catch-up begins before the logs get backed up by the 3rd-party tool, otherwise NDB will miss some logs and the operations will fail. If the 3rd-party tool grants exclusive access to the logs, then NDB will not be able to capture them at all, and the operations will not be supported.
Nutanix Database Management & Automation (NDMA) course, Module 5, Lesson 5.2 - Log Backup ManagementNutanix Support & Insights, Nutanix NDB User Guide v2.5, Log Backup Management
An administrator needs to restore a source database from a snapshot. The database shares the source volume with multiple other databases.How does NDB handle this database restore operation?
Answer(s): A
The correct answer is A because NDB handles the database restore operation by copying the specific database files from the snapshot volume to the source volume, without affecting the other databases that share the same source volume. NDB uses a copy-on-write mechanism to create snapshots and clones, which means that only the changes made to the database files are stored in the snapshot or clone volume, while the original files are kept in the source volume. Therefore, when restoring a source database from a snapshot, NDB only needs to copy the specific database files that have been modified since the snapshot was taken, and overwrite them on the source volume. The other options are not correct because they either cause data loss or unnecessary data transfer. Option B is not correct because replacing the source volume with specific db disks would erase the other databases that share the same source volume, which is not desirable. Option C is not correct because replacing the source volume with the snapshot volume would also erase the other databases that share the same source volume, as well as any changes made to the source database after the snapshot was taken, which is not desirable. Option D is not correct because copying all database files to the source volume would be inefficient and unnecessary, as only the modified files need to be copied, and the other files are already present on the source volume.
Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, [Nutanix Support & Insights]
When trying to restore a database via Time Machine (TM), the option to restore data to a Point in Time is not available.What should the administrator do to enable Point in Time Recovery?
Point in Time Recovery (PITR) is a feature of NDB that allows restoring a database to any point in time within the retention period of the SLA. To enable PITR, the SLA must support Continuous Log retention, which means that NDB captures and stores the database logs continuously. This allows NDB to replay the logs from the last snapshot to the desired point in time during the restore process. The other options do not enable PITR, but rather affect the frequency and timing of the snapshots and log catch up operations.
Nutanix Support & Insights, section "NDB Time Machine Point in Time Recovery"
Post your Comments and Discuss Nutanix NCP-DB exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the NCP-DB content, but please register or login to continue.