Grab latest Nutanix NCP-DB Dumps as PDF Updated on 2025 [Q149-Q164]

Grab latest Nutanix NCP-DB Dumps as PDF Updated on 2025

Newly Released NCP-DB Dumps for Nutanix Certified Professional (NCP) Certified

Nutanix NCP-DB Exam Syllabus Topics:

NEW QUESTION # 149
A request is received to refresh a database clone from a new manual snapshot. When the administrator attempts to create the new snapshot from the Time Machine, it is in a Frozen state.
What causes a Time Machine to enter the Frozen state and what are the administrator's options to complete the request?

• A. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
  Resolution: To complete the request the database must be re-registered in NDB, create a new Time Machine and create a new clone.
• B. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
  Resolution: To complete the request the database must be re-registered in NDB, this thaws the Time Machine and it resumes operation so the clone can be refreshed.
• C. Cause: The Time Machine enters a Frozen state after too many snapshot or log catchup failures.Resolution: Remediate the snapshot or log catchup failures, this thaws the Time Machine, allowing normal operations to continue and the request can be completed.
• D. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
  Resolution: The Time Machine must be paused, then the database re-registered with a new Time Machine and a new clone created.

Answer: B

Explanation:
A Time Machine is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention.When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de-registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze. 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: Time Machine Concepts
* Nutanix Support & Insights, TN-2101: Nutanix Database Service Time Machine Under the Hood, Section: Time Machine States and Transitions

NEW QUESTION # 150
An administrator needs to roll back an Oracle patch on a database server VM using NDB. What is required for this action to be successful?

• A. The database must be shut down.
• B. The patch must have been applied on Grid home only using NDB.
• C. The patch must have been applied using NDB.
• D. The database must be in read-only mode.

Answer: C

Explanation:
To roll back an Oracle patch on a database server VM using NDB, the patch must have been applied using NDB in the first place. This is because NDB maintains a patch inventory and history for each database server VM and database that it manages. NDB uses this information to determine which patches can be rolled back and how to revert the changes made by the patch. If the patch was applied outside of NDB, NDB would not have the patch information and would not be able to roll back the patch. Therefore, the patch must have been applied using NDB for the rollback action to be successful. The other options are not required for the rollback action. The database does not need to be shut down or in read-only mode, as NDB can perform the rollback operation online. The patch does not need to be applied on Grid home only, as NDB can roll back patches applied on both Grid home and Database home. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 4 - Operate and Maintain an NDB Environment, Objective 4.4: Determine the correct method to apply Linux OS patches
* Nutanix Database Management & Automation (NDMA) Course, Module 5: Nutanix Database Service (NDB) Patching, Lesson 5.1: Patching Overview, Topic: Patching Concepts
* [Nutanix Database Service (NDB) User Guide], Chapter 7: Patching, Section: Rolling Back a Patch

NEW QUESTION # 151
An administrator selected Bronze SLA for Era Time Machine during database registration.
Which two capabilities are supported by the Time Machine for this database? (Choose two,)

• A. Cloning
• B. Provwonng
• C. Snapshots
• D. Log Catch up

Answer: C,D

Explanation:
The Nutanix Era Time Machine provides various capabilities depending on the Service Level Agreement (SLA) selected during database registration1. For a database with a Bronze SLA, the Time Machine supports both "Log Catch up" and "Snapshots"2. "Log Catch up" allows the Time Machine to keep up with the latest changes in the database by capturing log data2. "Snapshots" are point-in-time copies of the database that can be used for recovery or cloning2.

NEW QUESTION # 152
What minimum account access level is required in Prism Element to deploy NDB?

• A. Cluster Administrator
• B. Backup Administrator
• C. User Administrator
• D. Viewer

Answer: A

Explanation:
To deploy Nutanix Database Service (NDB) in Prism Element, the minimum account access level required is Cluster Administrator. This role provides the necessary permissions to manage cluster resources (e.g., storage, networking, and VMs) required for NDB deployment, including registering the cluster with NDB, configuring storage containers, and deploying NDB components. Lower roles like Viewer or Backup Administrator lack the scope to perform these tasks, and User Administrator is focused on user management, not deployment.
Other options are insufficient:
* A. User Administrator: Manages users and roles, not cluster operations.
* C. Viewer: Read-only access, inadequate for deployment.
* D. Backup Administrator: Limited to backup tasks, not deployment.
Thus, the verified answer is B, aligning with NDB deployment prerequisites.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix Cluster (applicable to v6.
10).
* Nutanix NDB Installation Guide: "Prism Element Role Requirements" section.

NEW QUESTION # 153
An administrator needs to add multiple databases to an existing PostgreSQL instance.
How should the administrator satisfy this requirement?

• A. Modify parameter profile using post script.
• B. Modify parameter profile using the GUI.
• C. Modify parameter profile using ncli.
• D. Modify parameter profile using NDB CLI.

Answer: B

Explanation:
To add multiple databases to an existing PostgreSQL instance managed by NDB, the administrator should use the NDB graphical user interface (GUI). The GUI provides a user-friendly way to modify the parameter profile associated with the PostgreSQL instance, allowing the addition of new databases by adjusting settings such as database names, sizes, or configurations. This process typically involves navigating to the "Databases" or "Instances" section, selecting the PostgreSQL instance, and editing the parameter profile to include additional databases.
Other options are less appropriate:
* A. Modify parameter profile using ncli: The ncli (Nutanix Command Line Interface) is used for cluster-level management in Prism, not for NDB database configuration.
* C. Modify parameter profile using post script: Post-scripts are used for custom actions post- provisioning, not for modifying parameter profiles to add databases.
* D. Modify parameter profile using NDB CLI: While NDB has a CLI, the GUI is the recommended and supported method for such configuration changes, offering a guided workflow and validation.
Thus, the verified answer is B, leveraging the NDB GUI for ease and compliance with best practices.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.4: Modifying Database Configurations.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
3: Manage NDB Solutions, Objective 3.3: Modify Parameter Profiles (applicable to v6.10).
* Nutanix NDB Administration Guide: "Managing PostgreSQL Instances" section, detailing GUI-based modifications.

NEW QUESTION # 154
An administrator needs to maintain five days of time-travel capability to any second, plus an additional seven days of discrete recovery at a daily interval.
How should the administrator define the Frequency and retention on the SLA?

• A. * Continuous log retention (days): 5
  * Weekly snapshot retention (weeks): 1
• B. * Continuous log retention (days): 7
  * Daily snapshot retention (days): 5
• C. * Weekly snapshot retention (weeks): 1
  * Continuous log retention (days): 7
• D. * Daily snapshot retention (days): 7
  * Continuous log retention (days): 5

Answer: D

Explanation:
The correct answer is D because it meets the requirements of maintaining five days of time-travel capability to any second and an additional seven days of discrete recovery at a daily interval. Continuous log retention allows the administrator to restore the database to any point in time within the specified number of days, while snapshot retention allows the administrator to restore the database to a specific point in time at a fixed interval.
Therefore, by setting the daily snapshot retention to 7 days, the administrator can ensure that there is a discrete recovery point for each day of the week. By setting the continuous log retention to 5 days, the administrator can ensure that there is a time-travel capability to any second within the last five days. The other options do not meet the requirements because they either have less than five days of continuous log retention or less than seven days of snapshot retention. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Certified Professional - Database Automation (NCP-DB) datasheet

NEW QUESTION # 155
While adding Time Machine data access to a Nutanix cluster, when is a storage container mapping needed

• A. When the source database and NDB provisioning container are the same.
• B. When the source database and NDB VM are on the same container.
• C. When the source database and NDB Server containers are different.
• D. When the source and destination database containers are different.

Answer: C

Explanation:
Time Machine data access is a feature of Nutanix Database Service (NDB) that allows you to access a point-in-time snapshot of a database without restoring it. To use this feature, you need to create a Data Access Management (DAM) policy that defines the access mode, the source database, the destination cluster, and the storage container mapping. The storage container mapping is needed when the source database and the NDB Server containers are different, because NDB needs to know where to store the metadata and the clone of the source database. If the source database and the NDB Server containers are the same, then NDB will use the same container for both the metadata and the clone. References:
* Nutanix Certified Professional - Database Automation (NCP-DB), Section 5 - Protect NDB-managed Databases Using Time Machine
* Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 9, Objective 5.6
* Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.2 - Data Access Management

NEW QUESTION # 156
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?

• A. Oracle
• B. MySQL
• C. PostgreSQL
• D. Microsoft SQL

Answer: B

Explanation:
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

NEW QUESTION # 157
How should a patch be downloaded to perform a One-Click Upgrade of an NDB Environment with access to the Internet?

• A. Open Prism Central and deploy the current version of NDB from the Apps and Marketplace section.
• B. Open Prism Element and use LCM to update the software.
• C. Download the patch from the Nutanix Support Portal and upload via the NDB CLI.
• D. Download the patch in the Administrator > Maintenance section of NDB.

Answer: D

Explanation:
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) v6.5 Knowledge Objectives, Section
2: Deploy and Configure an NDB Solution, Objective 2.3: Perform NDB Updates (applicable to v6.10).
* Nutanix NDB Administration Guide: "One-Click Upgrade Process" section.

NEW QUESTION # 158
Which two network prerequisites are required to deploy an Era instance in production? (Choose two.)

• A. NTP, DNS servers, gateway, and subnet mask must be available and visible to Ere,
• B. One static IP address must be available and changed using CLI after VM deployment.
• C. An SMTP server and details must be provided for notifications.
• D. A storage container must be available es a prerequisite.

Answer: A,B

Explanation:
* Option A: Nutanix Era requires network prerequisites like NTP, DNS servers, gateway, and subnet mask to be available and visible. These are essential for the proper functioning of the Era instance1.
* Option B: One static IP address must be available and can be changed using CLI after VM deployment. This is necessary for the Era VM to communicate with other components in the network1.
* Option C: While a storage container is necessary for Nutanix infrastructure, it is not a network prerequisite specifically for deploying an Era instance.
* Option D: An SMTP server and details are typically used for sending notifications, but they are not a network prerequisite for deploying an Era instance. They are more related to the operational aspect post-deployment.

NEW QUESTION # 159
An NDB environment has been deployed with three Nutanix clusters. An administrator has been asked to create a Microsoft SQL Server software profile for each of these clusters.
Which is a requirement to create the above-mentioned profiles?

• A. Each cluster must host a VM with the DB engine.
• B. Enable High Availability for the current NDB Service.
• C. Compute profile must be created first on every cluster.
• D. Enable Multi-cluster capabilities for NDB.

Answer: A

Explanation:
To create a Microsoft SQL Server software profile for each of the three Nutanix clusters in an NDB environment, a key requirement is that each cluster must host at least one VM with the Microsoft SQL Server database engine installed. NDB uses these VMs to discover, validate, and generate software profiles tailored to the specific SQL Server versions and configurations present on each cluster. This ensures that the profiles are compatible with the cluster's environment and can be used for provisioning or patching.
* Option A (Compute profile must be created first on every cluster) is incorrect because compute profiles are optional and not a prerequisite for creating software profiles.
* Option B (Enable Multi-cluster capabilities for NDB) is incorrect as multi-cluster support is already implied by the deployment across three clusters, but it's not a specific requirement for profile creation.
* Option C (Enable High Availability for the current NDB Service) is incorrect because HA is a separate configuration and not required to create software profiles.
* Option D (Each cluster must host a VM with the DB engine) is correct as it aligns with NDB's requirement to have a reference VM for profile generation.
This setup ensures accurate and cluster-specific software profile creation.
References
* Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section:
Creating Software Profiles
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles

NEW QUESTION # 160
A request is received to refresh a database clone from a new manual snapshot. When the administrator attempts to create the new snapshot from the Time Machine, it is in a Frozen state.
What causes a Time Machine to enter the Frozen state and what are the administrator's options to complete the request?

• A. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
  Resolution: To complete the request the database must be re-registered in NDB, create a new Time Machine and create a new clone.
• B. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
  Resolution: To complete the request the database must be re-registered in NDB, this thaws the Time Machine and it resumes operation so the clone can be refreshed.
• C. Cause: The Time Machine enters a Frozen state after too many snapshot or log catchup failures.Resolution: Remediate the snapshot or log catchup failures, this thaws the Time Machine, allowing normal operations to continue and the request can be completed.
• D. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
  Resolution: The Time Machine must be paused, then the database re-registered with a new Time Machine and a new clone created.

Answer: B

Explanation:
A Time Machine is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention. When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de-registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze. 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: Time Machine Concepts
* Nutanix Support & Insights, TN-2101: Nutanix Database Service Time Machine Under the Hood, Section: Time Machine States and Transitions

NEW QUESTION # 161
Which Time Machine feature allows developers to automate the data refresh for their clones?

• A. Manual Backup
• B. Log Catchup
• C. Schedule
• D. update

Answer: C

Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, the Schedule feature of the Time Machine allows developers to automate the data refresh for their clones1. This feature eliminates the time-consuming, complex process of database clone/refresh, allowing admins to create database clones
/refresh to any point in time in just a few minutes1. Please refer to the official Nutanix documentation and training materials for more detailed information2.

NEW QUESTION # 162

An administrator has opened the Enable Multi-Cluster configuration for an NDB instance, but the wizard does not present the VLAN, as shown in the exhibit.
Which configuration allows to choose a VLAN in the drop-down box?

• A. Verify if subnet leverages advanced network control.
• B. A network profile must be created first.
• C. IP address pool must be managed in NDB.
• D. VLAN subnet must use IP address management.

Answer: B

Explanation:
The provided exhibit shows the "Enable Multi-Cluster" configuration wizard in NDB, where the VLAN dropdown is empty with a "Nothing found" message, indicating that no VLANs are available for selection.
This issue arises because NDB requires a network profile to be created before provisioning the NDB Agent VM and enabling multi-cluster support. A network profile defines the static VLANs managed by NDB, which are essential for network configuration during multi-cluster setup. The warning in the exhibit ("An NDB managed static vLAN is required to provision the NDB Agent VM. Add an NDB managed static vLAN using the Networks page to continue.") reinforces that the administrator must create a network profile via the Networks page to populate the VLAN dropdown.
* Option A (A network profile must be created first) is correct as it addresses the root cause by ensuring VLANs are defined in a network profile.
* Option B (Verify if subnet leverages advanced network control) is incorrect because advanced network control is not a prerequisite for VLAN selection in this context.
* Option C (IP address pool must be managed in NDB) is incorrect because IP address pools are managed separately and not required for VLAN selection at this stage.
* Option D (VLAN subnet must use IP address management) is incorrect because IP address management is not a direct requirement for enabling VLAN selection in the wizard.
After creating the network profile, the administrator can proceed with the multi-cluster enablement.
References
* Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section:
Configuring Network Profiles for Multi-Cluster
* Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting VLAN Issues in NDB Multi- Cluster Setup"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

NEW QUESTION # 163
An administrator is attempting to enable high availability (HA) for NDB across three Nutanix clusters located in separate data centers. If the network latency between two clusters exceeds 25ms RTT, what impact might this have on the NDB HA setup?

• A. The clusters will not synchronize.
• B. HA cannot be enabled due to the latency.
• C. There will be no impact on HA functionality.
• D. HA will operate with increased delay.

Answer: B

Explanation:
NDB supports high availability (HA) across multiple Nutanix clusters, including those in separate data centers, by replicating data and ensuring failover capabilities. However, NDB imposes strict network latency requirements for HA. The official documentation specifies that the round-trip time (RTT) latency between clusters should not exceed 25ms for HA to function effectively. If the latency between two clusters exceeds this threshold (e.g., due to geographic distance or network issues), HA cannot be enabled, as the synchronization and failover mechanisms rely on low-latency communication to maintain consistency and performance.
Impact of other options:
* A. HA will operate with increased delay: While latency might cause delays, exceeding 25ms RTT prevents HA setup entirely, not just delays its operation.
* C. The clusters will not synchronize: Synchronization issues may occur as a symptom, but the primary impact is HA enablement failure.
* D. There will be no impact on HA functionality: This is incorrect, as latency beyond 25ms RTT violates HA prerequisites.
Thus, the verified answer is B, reflecting NDB's latency constraints for HA across clusters.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 4: High Availability and Disaster Recovery, Lesson 4.2: Configuring Multi-Cluster HA.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
4: Troubleshoot NDB Solutions, Objective 4.3: Configure HA Across Clusters (applicable to v6.10).
* Nutanix NDB Administration Guide: "High Availability Configuration Requirements" section, specifying latency limits.

NEW QUESTION # 164
......

Latest NCP-DB Exam Dumps Nutanix Exam from Training: https://exams4sure.pdftorrent.com/NCP-DB-latest-dumps.html