Nutanix Certified Professional - Database Automation v6.10 NCP-DB Exam Practice Test

Answer : B

In an NDB environment, the repository VM stores metadata and configuration data but is not a critical runtime component for service availability. If the team powers off the repository VM during maintenance, and it is neither the primary nor a synchronized copy node, the NDB service will continue to operate without interruption. NDB's high availability (HA) architecture, managed by HAProxy and other components, ensures redundancy and failover capabilities, allowing the system to rely on the primary and synchronized nodes. The repository VM's downtime only affects metadata access, which can be restored post-maintenance without impacting ongoing database operations.

Option A (The HAProxy VMs will failover instead) is incorrect because HAProxy failover is triggered by primary service node failures, not repository VM power-off.

Option B (There will be no service interruption) is correct as the HA design tolerates a non-primary, non-synchronized repository VM being offline.

Option C (Manual interaction will be required to restore service) is incorrect because no service restoration is needed during this scenario.

Option D (NDB services will fail over immediately) is incorrect because failover is not triggered by a non-critical repository VM power-off.

This reflects NDB's robust HA implementation.

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: High Availability Architecture

Nutanix Support & Insights, Knowledge Base Article: 'Impact of Repository VM Maintenance in NDB'

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

Answer : B

When upgrading NDB and the upgrade includes updates to out-of-the-box (OOB) software profiles (e.g., predefined profiles for database software like PostgreSQL, SQL Server, etc.), NDB manages older versions of these profiles based on their usage. If the older OOB software profiles are not actively in use by any database VMs, NDB automatically deletes all versions of those profiles from its metadata and associated protection domains during the upgrade process. This cleanup mechanism helps maintain a lean and efficient system by removing obsolete profiles that are no longer relevant or required.

Option A is incorrect because the condition about Time Machines and snapshots in the last 24 hours is not a documented criterion for profile deletion during an NDB upgrade.

Option B is correct as it reflects NDB's behavior of removing unused OOB software profiles during upgrades to optimize resource usage and metadata.

Option C is incorrect because shutting down database VMs does not trigger automatic deletion of software profiles; the key factor is whether the profiles are in use.

Option D is incorrect because the concept of a 'base version' is not relevant here; deletion depends solely on whether the profiles are unused, not on versioning specifics.

This behavior ensures that only active and necessary profiles persist post-upgrade, streamlining administration.

Nutanix Database Service (NDB) User Guide, Chapter 6: Upgrading NDB, Section: Handling Software Profile Updates

Nutanix Support & Insights, Technical Note: 'NDB Upgrade Process and Software Profile Management'

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 6: Administer an NDB Environment

Answer : D

The Removal schedule is a feature of Nutanix Era that allows you to specify when a database clone will be automatically deleted. You can modify the Removal schedule of an existing clone by selecting the clone from the Clones page, clicking on the Update button, and changing the Removal schedule option to the desired date. This way, you can extend or shorten the lifespan of a clone as per your requirements. You do not need to remove the existing Removal schedule and add a new one, as this would be an unnecessary step. You also do not need to update the Removal schedule to the end of the month, as this would not meet the request of keeping the clone for an additional 14 days.Reference::

Nutanix Database Management & Automation Training Course, Module 4: Protecting Databases Using Time Machine, Lesson 3: Cloning Databases, Slide 10: Clone Removal Schedule

Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 5: Protect NDB-managed Databases Using Time Machine, Objective 5.3: Given business requirements, perform a database clone

Answer : B, D

Nutanix Era can be upgraded using the Offline Upgrade and One-click Upgrade methods. The Offline Upgrade method involves manually downloading the software update and applying it to the Era instance.The One-click Upgrade method allows you to upgrade Era directly from the Era management console with a single click, provided that the Era instance has internet connectivity and can reach the Nutanix software update portal1.

Answer : B

When an administrator cannot proceed with the first step of the wizard to provision a new Oracle single instance database in NDB, the most likely reason is that a software profile for Oracle is missing. NDB requires a software profile (which defines the database version, patches, and configuration) to provision a database instance. Without a profile created from a Reference: VM or uploaded manually, the wizard cannot proceed, as it relies on this profile to configure the instance correctly.

Option A (Time Machine is not configured) is incorrect because Time Machine is optional for backups and not required for initial provisioning.

Option B (Software profile is missing) is correct as it is a mandatory prerequisite for provisioning any database instance.

Option C (No remote clusters are configured) is incorrect because remote clusters are relevant for multi-cluster setups, not single instance provisioning.

Option D (A snapshot must be taken on the original DB) is incorrect because snapshots are for protection, not a prerequisite for provisioning.

The administrator must create or import a software profile to resolve this issue.

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Provisioning Databases

Nutanix Support & Insights, Knowledge Base Article: 'Troubleshooting Provisioning Failures in NDB'

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles

Answer : D

Configuring VM Host Affinity in a Nutanix AHV-powered cluster ensures that VMs are placed on specific hosts to optimize performance or HA. However, after a host failure, if database VMs cluster on a single remaining host, it indicates that the affinity rules alone are insufficient to maintain high availability (HA) during failover scenarios. To prevent this, the administrator should configure anti-affinity rules, which dynamically ensure that VMs (e.g., database server VMs) are spread across multiple hosts. Anti-affinity rules override default VM placement behavior during failover, reducing the risk of a single point of failure by keeping VMs separated even after a host outage.

Option A (Assign additional backup VMs on the same host) is incorrect because placing backups on the same host increases risk rather than mitigating it.

Option B (Increase affinity zones) is incorrect as 'affinity zones' is not a standard Nutanix term in this context, and it does not address dynamic VM separation.

Option C (Configure automatic host failover in Prism Central) is incorrect because while failover is managed by AHV, it does not inherently prevent VMs from clustering without specific rules.

Option D is correct as anti-affinity rules proactively distribute VMs, enhancing HA in failure scenarios.

This approach leverages Nutanix AHV's VM placement policies to ensure resilience.

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring VM Affinity and Anti-Affinity

Nutanix AHV Administration Guide, Section: VM High Availability and Placement Rules

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

Answer : C

The correct answer is C because the NDB Database Agent service is responsible for scheduling and monitoring the NDB-related operations, such as provisioning, patching, cloning, and restoring databases. The NDB Database Agent service is deployed on the NDB server and on each of the database server VMs provisioned by NDB. It contains the tools required to perform each task and communicates with the NDB server through the NDB API. The other options are not correct because they describe different components or functions of the NDB solution. Option A is not correct because the transaction logs are not stored by the NDB Database Agent service, but by the NDB Time Machine service, which is a distributed file system that stores the database snapshots and logs. Option B is not correct because the source databases are not hosted by the NDB Database Agent service, but by the database server VMs, which are virtual machines that contain an instance of the database engine software and the database files. Option D is not correct because the NDB Database Agent service does not contain an instance of the database engine software, but only the tools required to perform the NDB-related operations. The database engine software is installed on the database server VMs, which are provisioned by NDB using the profiles defined by the administrator.Reference::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