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

NDB deployments on NC2 use overlay networking created with Nutanix Flow Virtual Networking. Consequently, an appropriate Flow overlay subnet must be created for NDB and the database server VMs that it will manage. A floating IP address must also be created or assigned to the NDB VM so that the NDB interface and services are reachable through the cloud networking environment. A Flow underlay subnet is not the supported network type for this deployment. Although an NC2 environment ultimately operates within AWS networking infrastructure, creating a native AWS VPC is not the NDB-specific deployment step requested by the question. Nutanix’s NC2 networking documentation identifies Flow-created overlay networks, while the Flow integration guidance describes assigning a floating IP address to the NDB VM.

Prism Central registration is the prerequisite that makes Nutanix Objects discoverable and manageable by NDB. Nutanix states that one or more Prism Central domains must be registered with NDB before an Object Store can be provisioned or registered. Once that relationship exists, the administrator can select the appropriate Prism Central and Object Store from the NDB workflow and then configure the store for database log backups. Registering an S3-compatible store is a later object-store onboarding step, not the initial prerequisite. An NC2 deployment is optional, and directly registering only the Prism Element instance hosting Objects does not satisfy the documented integration sequence. Therefore, option C is correct. The candidate file’s supplied answer D conflicts with the official prerequisite and has been corrected. Nutanix Prism Central registration documentation

The NDB GUI allows an administrator to set the schedule interval for a database log catch up, which is the process of collecting transaction logs periodically from the source databases and storing them in the time machine. The shortest possible value for this interval is 15 minutes, as per the NDB documentation1. This means that the NDB time machine will capture the database logs every 15 minutes and use them for backup, restore, clone, and refresh operations. References: Nutanix Database Management & Automation (NDMA), page 29; Nutanix Support & Insights, section “Log Catch-up”

The Storage Usage widget on the NDB dashboard provides the required entity-level storage information. It displays the percentage of storage consumed by registered Nutanix clusters and NDB entities, including source databases, database clones, and Time Machines. Administrators can use this information to distinguish production database capacity from space consumed by protected copies and downstream clones. NDB periodically collects and stores historical usage information, which also supports storage-trend analysis and capacity forecasting. Prism Element and Prism Central provide infrastructure-level capacity information, but they do not present the same NDB-aware classification of source databases, clones, and Time Machines. NCM reporting is therefore unnecessary for this specific requirement. The official NDB Dashboard reference identifies Storage Usage as the dashboard widget that reports consumption for clusters, data sources, clones, and Time Machines.

When an Oracle database is upgraded using Era, the type of upgrade category is an “In-place upgrade”. This method involves upgrading the database software within the same Oracle home as the existing database. The AutoUpgrade utility is used to automate the upgrade process, both before starting upgrades, during upgrade deployments, and during post-upgrade checks and configuration migration1. This method is preferred due to its simplicity and efficiency1.

To create a software profile version for a newly-released Oracle ISc patch, an administrator should follow these steps:

Download the required patch from MyOracle Support1. This is because Oracle patches are typically available from MyOracle Support, not Microsoft Support.

Apply the patch to the Oracle Home/Grid Home on a cloned VM of the gold image using OPatchAuto1. OPatchAuto is a utility provided by Oracle that automates the process of applying patches to a database.

Ensure success of patch application1. It’s important to verify that the patch has been applied successfully to avoid any issues down the line.

Create a new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era GUI1. This step is necessary to ensure that the new patch is included in the software profile.

Mark the original patch profile as hidden1. This step is optional but can be useful for keeping the software profile clean and organized.

Please note that these answers are based on the information available as of my last update in 2021 and may need to be verified with the most recent Nutanix Database Automation (NCP-DB) documentation or resources.

To replicate database snapshots to remote Nutanix clusters, the administrator needs to add Data Access to each Nutanix cluster and assign a Data Availability Management (DAM) policy. Data Access is a feature of NDB that enables cross-cluster data mobility and protection. A DAM policy defines the replication frequency, retention period, and priority of the database snapshots across the clusters. By adding Data Access to each Nutanix cluster and assigning a DAM policy, the administrator can manage the Time Machine data availability across all registered Nutanix clusters in NDB.

 Nutanix Support & Insights, section “NDB Data Access”

To allow a non-administrative NDB user to provision an Oracle database using a Software Profile created by an administrator, the administrator must promote the Software Profile to Published. In NDB, Software Profiles define the database software version and configuration (e.g., Oracle binaries). By default, a newly created profile is in a draft or private state. Promoting it to "Published" makes it available for use by other NDB users, including non-administrative ones, within the access control framework. This ensures the profile is validated and accessible without requiring individual user assignments.

Other options are incorrect:

A. Ensure that specified users have access to the Software Profile using Access Control: Access Control manages user permissions but does not make the profile available unless it is published.

B. Replicate the Software Profile to other Nutanix clusters: Replication is for HA or disaster recovery, not user access.

C. Ensure that the Software Profile has been properly versioned to the latest release of Oracle: Versioning ensures compatibility but does not grant user access.

Thus, the verified answer is D, aligning with NDB’s profile management workflow.

Official Nutanix Database Automation References

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

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

Nutanix NDB Administration Guide: "Publishing Software Profiles" section.

NDB Agents handle log backups for database instances, but storing these backups locally can lead to bottlenecks (e.g., disk I/O, storage capacity). To alleviate this, integrating NDB with Nutanix Objects is the recommended solution. Nutanix Objects is an S3-compatible object storage service within the Nutanix ecosystem, ideal for offloading log backups from NDB Agents to a scalable, centralized storage platform. This reduces local storage pressure, improves performance, and ensures strict SLAs for database recovery by leveraging efficient backup retrieval.

Other options are less effective:

A: Integrating with AWS S3 or Azure Blob is possible but requires external connectivity and introduces latency, complexity, and cost compared to Nutanix Objects.

B: Adding NDB Agent VMs increases management overhead and doesn’t address the root storage bottleneck.

D: Increasing RAM/CPU on NDB Agents may help processing but doesn’t solve storage capacity or I/O issues for log backups.

Thus, C is the verified answer, aligning with Nutanix’s integrated ecosystem approach.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.3: Configuring Log Backup Storage.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.3: Configure Backup Storage Options (applicable to v7.5).

Nutanix NDB Administration Guide: "Integrating NDB with Nutanix Objects for Log Backups" section.

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”