Pass the Nutanix Certified Professional (NCP) NCP-DB Questions and answers with Dumpstech

 In the Nutanix Database Automation (NCP-DB) framework, the role that allows an administrator to work with databases and time machines, but not database parameter profiles, is the Database Administrator (DBA)123. This role provides the necessary permissions to manage databases and time machines, which are essential components of the Nutanix Era solution. However, it does not grant access to database parameter profiles, which are typically managed by other roles45.

NDB diagnostic collection gathers relevant logs from the NDB control plane and the database server VMs participating in the failed operation. For a Linux database server, the NDB agent collects applicable operating-system information, database-engine logs, work-driver output, and operation-specific diagnostic data. These files are packaged into a downloadable compressed bundle associated with the failed operation, allowing administrators or Nutanix Support to examine the complete execution context. NDB does not copy the active database data directory, create a runtime memory dump, or use a hypervisor snapshot of the log directory. Time Machine protects database data through snapshots and transaction logs; it is not the mechanism used to assemble support bundles. The official Nutanix instructions for viewing operation logs and downloading diagnostic bundles describe the collected and compressed diagnostic information.

To add a new Nutanix AHV cluster to the current single default container for database provisioning and enable NDB multi-cluster functionality, the administrator must ensure a unified management framework. Nutanix Prism Central serves as the centralized management platform for multi-cluster environments, allowing NDB to manage multiple clusters (in this case, the existing cluster and the new AHV cluster) under a single instance. Before enabling multi-cluster support in NDB, both clusters must be registered with the same Prism Central instance, and NDB must be confirmed as registered to that instance. This ensures consistent policy enforcement, resource visibility, and database provisioning across clusters using the default container.

Option A (Deploy Nutanix Self Service VM and use blueprints) is incorrect because Nutanix Self Service is an optional tool for end-user provisioning and not a prerequisite for multi-cluster enablement.

Option B (Configure datastore mapping within Prism Element Protection Domains) is incorrect because datastore mapping is a lower-level configuration and not directly required for multi-cluster setup in NDB.

Option C (Enable High Availability for NDB service on the Administration page) is incorrect because HA is a separate configuration for NDB resilience, not a prerequisite for multi-cluster support.

Option D is correct as it aligns with NDB’s requirement for Prism Central integration to manage multiple clusters effectively.

This configuration ensures seamless multi-cluster operation.

References

Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Multi-Cluster Configuration

Nutanix Prism Central Administration Guide, Section: Managing Multiple Clusters

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

When an administrator needs to scale the size of an Oracle database running on Nutanix NDB and originally configured using ASMLib (Automatic Storage Management Library), the most efficient approach is to use NDB’s built-in scaling ability to resize existing vDisks. NDB supports dynamic resizing of virtual disks (vDisks) associated with database VMs, allowing the administrator to increase storage capacity without disrupting the database or requiring complex migrations. This method leverages Nutanix’s storage integration, resizing the underlying vDisks and updating the ASMLib configuration to reflect the new size, ensuring seamless operation.

Option A (Leverage the scaling ability built into NDB to resize existing vDisks) is correct as it is the most efficient, native NDB feature for scaling storage.

Option B (Extend the size by adding new vDisks) is incorrect because adding new vDisks requires additional configuration (e.g., ASM disk group adjustments), making it less efficient than resizing.

Option C (Create a new, larger database and migrate) is incorrect because migration is time-consuming and unnecessary when resizing is supported.

Option D (Mount an iSCSI LUN and extend the database onto the new LUN) is incorrect because iSCSI LUNs are not the preferred method in NDB, and resizing vDisks is more integrated.

This approach minimizes downtime and complexity.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Scaling Storage for Databases

Nutanix Support & Insights, Knowledge Base Article: "Resizing vDisks for Oracle Databases in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Servers

NDB High Availability uses multiple API Server VMs to provide the user interface and REST API services. The platform can automatically tolerate the failure of up to two service VMs, but if every API Server VM is offline, the API service becomes completely unavailable and manual intervention is required. Recovery requires bringing at least one API Server VM back online. Once an API Server is running, the NDB API service can restart and the remaining HA components can rejoin or recover through the normal resiliency mechanisms. Restarting HAProxy first cannot restore an API service when no API Server is available. Repository VMs should not be recreated because they contain NDB metadata, and registered Nutanix clusters do not need to be registered again. Therefore, the correct answer is A. NDB HA failure and recovery scenarios

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

Nutanix Era (NDB) utilizes DEFAULT_008 SLAs with varying frequencies for snapshots and log backups to achieve different recovery point objectives (RPOs). Here's how they compare:

DEFAULT_008 GOLD SLA: Typically has frequent log backups (e.g., every 15 minutes) and snapshots every few hours. This is designed for critical databases with very low RPOs.

DEFAULT_008 SILVER SLA: Offers a balance between protection and resource usage. Log backups might occur every hour with snapshots less frequently. This SLA is often suitable for databases requiring a good RPO without being overly resource-intensive.

DEFAULT_008 BRONZE SLA: Has less frequent log backups (e.g., every few hours) and less frequent snapshots. This is used for databases with less stringent RPO requirements.

DEFAULT_008 BRASS SLA: This has infrequent log backups and is usually considered the least protective SLA with the longest potential RPO

Reasoning:

Since the requirement is to have at least a 7-day log recovery period, any SLA with more frequent log backups than daily is excessive. The DEFAULT_008 SILVER SLA, with its hourly log backups, easily satisfies this requirement, offering the ability to restore to a point in time within the last hour of the past seven days.

If a database administrator is unable to provision a new MongoDB database using an existing software profile, the most likely cause is that the administrator lacks the proper permissions in Prism Element. NDB relies on Prism Element for cluster-level operations (e.g., storage and compute resource allocation). The database administrator needs appropriate Prism Element roles (e.g., Cluster Admin) to interact with the underlying infrastructure, even if the software profile is available in NDB. Without these permissions, the provisioning action will fail.

Other options are less likely:

A. A database clone operation is in progress: This might delay actions but wouldn’t prevent provisioning unless it locks resources indefinitely.

B. The software profile was created by another user: NDB allows profile reuse across users if published, so this is not a barrier.

D. The software profile is undergoing a patching operation: Patching affects the profile’s state but doesn’t block provisioning unless explicitly locked.

Thus, the verified answer is C, highlighting the need for Prism Element permissions.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Provisioning Databases.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Troubleshoot Provisioning Issues (applicable to v7.5).

Nutanix NDB Administration Guide: "Prerequisites for Database Provisioning" section, noting Prism Element roles.

For a One-Click Upgrade of an NDB environment with internet access, the patch should be downloaded directly within the NDB interface. The "Administrator > Maintenance" section of NDB provides an option to connect to the Nutanix download repository (e.g., https://download.nutanix.com) and download the latest patch or upgrade bundle automatically. This streamlined process ensures compatibility and simplifies the upgrade workflow. The One-Click Upgrade feature then applies the downloaded patch to update NDB components efficiently.

Other options are incorrect:

A. Download the patch from the Nutanix Support Portal and upload via the NDB CLI: This is suitable for dark sites but unnecessary with internet access, as NDB can download directly.

C. Open Prism Central and deploy the current version of NDB from the Apps and Marketplace section: This is for initial deployment, not upgrading an existing NDB instance.

D. Open Prism Element and use LCM to update the software: Lifecycle Manager (LCM) is for Nutanix cluster updates, not NDB-specific upgrades.

Thus, the verified answer is B, leveraging NDB’s built-in maintenance capabilities.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Updating NDB with Internet Access.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.3: Perform NDB Updates (applicable to v7.5).

Nutanix NDB Administration Guide: "One-Click Upgrade Process" section.

According to the Nutanix Database Automation (NCP-DB) learning documents, to configure Era to send alert notifications to email recipients, you need to go to the Administration section, select Era Service, then go to the configure notification widget. From there, you can update the SMTP server configuration1. This allows Era to use the SMTP server to send alert notifications to the specified email recipients1.

The administrator should begin with the NDB dashboard because its Storage Usage information provides a consolidated view of capacity consumed by registered clusters and NDB-managed entities. The dashboard distinguishes consumption associated with source databases, clones, and Time Machines, making it the fastest location for identifying the largest storage consumers before investigating an individual entity. Database Server Details focuses on a selected server and does not provide the same environment-wide comparison. Time Machine Properties applies only to a particular protection entity, while Software Profile Management concerns database software images and versions rather than database storage consumption. NDB also records historical storage information, enabling administrators to assess trends and determine whether capacity pressure is increasing. Nutanix’s official NDB Dashboard documentation confirms that the Storage Usage view reports consumption for data sources, clones, Time Machines, and registered Nutanix clusters.