[Feb 10, 2026] Uplift Your NCP-DB Exam Marks With The Help of NCP-DB Dumps [Q116-Q133]

Share

[Feb 10, 2026] Uplift Your NCP-DB Exam Marks With The Help of NCP-DB Dumps

Use Nutanix NCP-DB Dumps To Succeed Instantly in NCP-DB Exam

NEW QUESTION # 116
It becomes necessary to remove an existing database clone. "To minimize the impact of that removal to users, an administrator would like to schedule this operation for weekend hours.
When scheduling this removal, other than the specified date/time, which option in the Update Removal Schedule is pre-selected as non-optional?

  • A. Unregister the database clone from NDB.
  • B. Create an alert before removal.
  • C. Delete supporting snapshot from NDB.
  • D. Delete the database clone from the VM.

Answer: C

Explanation:
When an administrator schedules the removal of an existing database clone to minimize user impact (e.g., during weekend hours), the "Update Removal Schedule" feature in NDB allows for planning the operation.
Among the options, the "Delete supporting snapshot from NDB" is pre-selected as a non-optional action. This ensures that the snapshot data associated with the clone is removed along with the clone itself, maintaining storage efficiency and consistency in the Time Machine framework. Other options may be selectable but are not mandatory by default.
* Option A (Create an alert before removal) is incorrect because alerts are optional notifications, not a required action.
* Option B (Delete supporting snapshot from NDB) is correct as it is a default, non-optional step to clean up snapshot data.
* Option C (Unregister the database clone from NDB) is incorrect because unregistration is an optional administrative step, not pre-selected.
* Option D (Delete the database clone from the VM) is incorrect because the clone deletion itself is the primary action, but snapshot deletion is the non-optional supporting task.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Clone Removal
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine


NEW QUESTION # 117
How can NDB updates be downloaded for a dark site?

  • A. Change the network that NDB is hosted on so it has access to https://download.nutanix.com.
  • B. Download the upgrade bundle from the Nutanix Support portal and manually upload it to the NDB server.
  • C. Download the upgrade bundle from the Nutanix support Portal and upload it to Prism Element > Images
  • D. Go into the Administrator > Maintenance section in NDB and download the most recent version.

Answer: B

Explanation:
A "dark site" refers to an environment with no internet connectivity, requiring manual processes for software updates. For Nutanix Database Service (NDB) in such a setup, updates cannot be downloaded automatically from the internet. The correct procedure is to:
* Download the upgrade bundle: Access the Nutanix Support Portal from a system with internet access and download the NDB upgrade bundle specific to the version (e.g., v6.10 or later).
* Manually upload it to the NDB server: Transfer the bundle to the NDB server (e.g., via SCP or USB) and upload it through the NDB interface under the "Software Updates" or "Maintenance" section.
Other options are incorrect in a dark site context:
* B: The "Administrator > Maintenance" section allows initiating updates, but it cannot download files without internet access.
* C: Changing the network to access https://download.nutanix.com defeats the dark site's isolation and is impractical.
* D: Uploading to Prism Element > Images is for VM images or other Prism-specific content, not NDB software updates.
Thus, the verified answer is A, aligning with Nutanix's documented process for dark site updates.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Updating NDB in Dark Sites.
* 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: "Updating NDB in a Dark Site Environment" section.


NEW QUESTION # 118
Which two processes should an administrator take to create a software profile version for a newly-released Oracle ISc patch? (Choose two.)

  • A. 1. Download the required patch from MyOracle Support
    2. Apply the patch to the Oracle Home Grid Home on a cloned VM of the gold image using O PatchAuto
    3. Ensure success of patch application
  • B. 1. Download the required patch from Microsoft Support.
    2. Apply the patch to the Oracle Home/Grid Home on e cloned VM of the gold image using OPatchAuto utiliv.
    3. Ensure success of patch application.
  • C. 1. Create new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era Gul.
    2. Mark the original patch profile as deprecated.
  • D. 1. Create new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era Gul.
    2. Mark the original patch profile as hidden.

Answer: A,D

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


NEW QUESTION # 119
What step should be taken to make the profile available to all users:

  • A. Create an Access Control role with the Create Profile right and assign to all users.
  • B. Create an Access Control group with the desired users and grant it the Database Admin role.
  • C. Update the profile and set the status to Published.
  • D. Update the profile and set available state to All.

Answer: D

Explanation:
The correct answer is D because it allows the administrator to make the profile available to all users without requiring any additional permissions or roles. A profile is a collection of settings that define how NDB manages a database server or a database. By default, a profile is only available to the user who created it and the Database Admin role. To make a profile available to all users, the administrator can update the profile and set the available state to All. This will enable all users to view and use the profile for their database operations.
The other options are not correct because they either require additional steps or do not achieve the desired outcome. Option A is not correct because creating an Access Control role with the Create Profile right and assigning it to all users will only allow them to create their own profiles, not use the existing one. Option B is not correct because creating an Access Control group with the desired users and granting it the Database Admin role will only make the profile available to those users, not all users. Option C is not correct because updating the profile and setting the status to Published will not change the availability of the profile, only the state of the profile. A published profile is a profile that has been tested and verified by the administrator and is ready for use. Adraft profile is a profile that is still under development or testing and is not ready for use. 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 # 120
What is the most efficient way to get information on REST APIs for a task in Era?

  • A. Navigate to and look for the desired
  • B. Log into Ere VM end run to list ell the REST APIs.
  • C. Navigate to Swagger REST in Era GI-II.
  • D. use API equivalent button in a workflow.

Answer: D

Explanation:
This is because it allows the database to be refreshed at the exact time specified (9:30 PM) with the most recent data. The other options either perform the snapshot before the desired time or do not specify when the snapshot would occur. Please note that the exact answer might depend on the specific database system and its capabilities. Always refer to the database's documentation for the most accurate information.


NEW QUESTION # 121
A database administrator is working with a cloned database and creates a clone removal schedule.
Which two default actions are taken on the cloned database? (Choose two.]

  • A. NDB marks the cloned database as offline.
  • B. NDB de-registers the cloned database.
  • C. NDB deletes the cloned database VM.
  • D. NDB deletes the cloned database.

Answer: B,D

Explanation:
When a database administrator creates a clone removal schedule in NDB, the system automates the cleanup of cloned databases based on the defined schedule (e.g., after a set retention period). The two default actions taken on the cloned database are:
* A. NDB deletes the cloned database: The clone's data is removed from storage to free up space.
* B. NDB de-registers the cloned database: The clone is removed from NDB's management inventory, ensuring it no longer appears in the GUI or is tracked.
Other options are not default actions:
* C. NDB marks the cloned database as offline: This is a temporary state, not a removal action.
* D. NDB deletes the cloned database VM: Deleting the VM is not automatic; it depends on the clone type (e.g., linked clones retain the VM).
Thus, the verified answers are A and B, aligning with NDB's clone management.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Clones and Removal Schedules.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
5: Protect Databases Using NDB, Objective 5.2: Manage Clone Removal (applicable to v6.10).
* Nutanix NDB Administration Guide: "Clone Removal Schedule Actions" section.


NEW QUESTION # 122
An administrator was asked to change the snapshot schedule for a given database. The administrator discovered that the time machine is in a paused state.
How should the administrator change the schedule?

  • A. Select the Time Machine; under Action select Update end define an appropriate schedule.
  • B. Clone the Time Machine and define an appropriate schedule for the clone.
  • C. Select Time Machine: Under actions Resume the Time Machine and then Update to define an appropriate schedule.
  • D. Clone the database and define an appropriate schedule for the clone.

Answer: A

Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, an administrator can change the snapshot schedule for a given database by selecting the Time Machine, then under Action, select Update and define an appropriate schedule1. This is because the Time Machine in Nutanix Era allows you to specify the number of backups or snapshots the time machine should take, the time of day it takes those snapshots, and the day of the week it takes weekly or monthly backups1. These options help you build a complete schedule of time machine capture operations1. Even if the Time Machine is in a paused state, the administrator can still update the schedule1. Cloning the Time Machine or the database is not necessary for changing the snapshot schedule1.


NEW QUESTION # 123
Which statement describes what the Time Machine Heal function can be used for?

  • A. Patches a Time Machine to the latest NDB levels.
  • B. Removes gaps in the Time Machine's restore capability.
  • C. Restores a Time Machine from snapshot in the event of malware.
  • D. Refreshes a database clone in Time Machine.

Answer: B

Explanation:
The Time Machine Heal function in NDB is designed to address inconsistencies or gaps in the Time Machine's restore point chain, ensuring a continuous and reliable recovery history. It identifies and repairs missing log backups or snapshots that may have been skipped due to failures (e.g., network issues or agent errors), thereby removing gaps in the restore capability. This function does not patch software, refresh clones, or restore from malware but focuses on maintaining the integrity of the Time Machine's data protection timeline.
Other options are incorrect:
* A. Patches a Time Machine to the latest NDB levels: This is a software update, not a heal function's purpose.
* C. Refreshes a database clone in Time Machine: Clone refresh is a separate operation, not related to healing.
* D. Restores a Time Machine from snapshot in the event of malware: Restoration is a distinct action, while heal addresses data gaps.
Thus, the verified answer is B, reflecting the heal function's role in restore continuity.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.4: Managing Time Machine Operations.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
5: Protect Databases Using NDB, Objective 5.4: Use Time Machine Features (applicable to v6.10).
* Nutanix NDB Administration Guide: "Time Machine Heal Function" section.


NEW QUESTION # 124
How should an administrator modify the Alert Severity level within Era?

  • A. From the dropdown menu choose Alerts > Policies. Then choose Update next to Alert Retention,
  • B. From the dropdown menu choose Alerts Policies. Chose the Poliq to be modified and chose either Set Enabled or Set Disabled,
  • C. From the dropdown menu choose Alerts > List. Select the message to be changed end choose Set Status to Resolved or Set Status to Acknowledged.
  • D. From the dropdown menu choose Alerts Policies. Choose the Policy to be modified and set the desired severity level.

Answer: D

Explanation:
In Nutanix Era, an administrator can modify the Alert Severity level by navigating to the Alerts Policies from the dropdown menu. Once there, they can select the Policy that needs to be modified and set the desired severity level1. This allows the administrator to customize the alerts according to their requirements, ensuring that they are notified of the most critical events in their environment21.


NEW QUESTION # 125
Which two statements best describe the features and functionality of Era Oracle patching? (Choose two.)

  • A. Era patching can be automated using REST API/CLI for scheduled patching many Oracle servers in a fleet patching scenario,
  • B. Era patching for Oracle databases has automatic rollback if any of the steps in the patching workflow fails.
  • C. Era Oracle fleet patching can be rolled back if issues ere encountered after successful patching.
  • D. Era does not require native Oracle Utility OpatchAuto to create the patch profile,

Answer: A,B

Explanation:
Nutanix Era provides a unified database operating model that delivers simplicity, performance, availability, and security across private and public clouds1. It standardizes your Oracle database ecosystem by mass patching the databases with one-click simplicity2. This includes the following features:
* Automated Patching: Era patching can be automated using REST API/CLI for scheduled patching many Oracle servers in a fleet patching scenario1. This allows for the standardization of your Oracle database ecosystem by mass patching the databases with one-click simplicity2.
* Automatic Rollback: Era patching for Oracle databases has automatic rollback if any of the steps in the patching workflow fails1. This ensures that your databases remain secure and functional even if an issue arises during the patching process1.


NEW QUESTION # 126

An administrator needs to restore a source database from a point in time at 21:50, but the restore option is not available.
What could explain the matter?

  • A. Change to snapshot option.
  • B. Selected Restore time is not available.
  • C. Logs to Backup must be run first.
  • D. Point in time must be within the most recent range.

Answer: C

Explanation:
The provided exhibit shows the NDB Time Machine restore interface for October 31, 2024, with a Point-in- Time (PIT) restore option selected at 21:50. However, the restore option is unavailable, as indicated by the question. The exhibit includes a warning: "Logs to Backup: The database may contain additional logs. Backup any remaining logs before restore or they will be lost." This suggests that PIT restore requires continuous log retention, and if logs since the last snapshot (at 01:10:00) are not backed up, the restore to 21:50 cannot proceed. Running the "Logs to Backup" operation ensures all transaction logs are captured, enabling PIT restore by allowing NDB to replay logs to the desired point.
* Option A (Point in time must be within the most recent range) is incorrect because the selected 21:
50 is within the log retention period shown (up to the current time), but logs need to be backed up.
* Option B (Selected Restore time is not available) is incorrect because 21:50 is a valid time within the log range, but log backup is the issue.
* Option C (Change to snapshot option) is incorrect because switching to a snapshot limits the restore to the snapshot time (01:10:00), not 21:50.
* Option D (Logs to Backup must be run first) is correct as the warning indicates that backing up remaining logs is necessary for PIT restore.
After running the backup, the administrator can proceed with the PIT restore.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Point- in-Time Restore Requirements
* Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting PIT Restore Issues in NDB"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine


NEW QUESTION # 127
Which statement is true regarding the NDB alert retention feature?

  • A. NDB supports retention at the grouped policy.
  • B. NDB supports retention at the individual policy.
  • C. NDB supports retention at the registered cluster.
  • D. NDB supports alert retention globally.

Answer: D

Explanation:
The NDB alert retention feature allows the database administrator to configure the duration for which the NDB alerts are stored and displayed in the NDB instance. The NDB alert retention feature supports alert retention globally, meaning that the same retention period applies to all the alerts generated by the NDB instance, regardless of the source cluster, policy, or operation. The database administrator can set the alert retention period from 1 day to 365 days, or choose to retain the alerts indefinitely. The NDB alert retention feature helps to manage the storage space and the visibility of the NDB alerts.
The NDB alert retention feature does not support retention at the individual policy, grouped policy, or registered cluster level. The NDB alert retention feature applies to all the alerts uniformly, and does not allow the database administrator to specify different retention periods for different policies or clusters.
References:
* Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment, Lesson 3.2: Nutanix Era Deployment, slide 11.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slide 6.


NEW QUESTION # 128
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 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.
  • C. 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.
  • D. 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.

Answer: D

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 # 129
Because of a cost reduction program, many Microsoft SQL server instances will be consolidated on DB server VMs managed by NDB using a medium compute profile. Database administrators are concerned about DB storage capacity and are looking to expand it.
Which NDB task should be performed?

  • A. Scale the source database.
  • B. Update the compute profile.
  • C. Update the Database server VMs.
  • D. Expand vDisk in Prism Element.

Answer: C

Explanation:
When consolidating Microsoft SQL Server instances on database server VMs managed by NDB using a medium compute profile, concerns about DB storage capacity can arise due to increased demand. In NDB, the appropriate task to address this is to "Update the Database Server VMs," which allows the administrator to adjust resource allocations, including storage capacity, for the VMs hosting the databases. This task can be performed within the NDB interface to expand disk space or reconfigure storage settings without altering the compute profile or requiring external tools.
* Option A (Update the Database server VMs) is correct as it provides a direct method in NDB to modify VM resources, including storage.
* Option B (Expand vDisk in Prism Element) is incorrect because NDB manages database VMs holistically, and storage expansion should be handled through NDB's Update task rather than Prism Element directly.
* Option C (Update the compute profile) is incorrect because compute profiles define CPU and memory, not storage capacity.
* Option D (Scale the source database) is incorrect as scaling typically refers to database-level adjustments (e.g., adding nodes), not VM storage expansion.
This approach ensures seamless integration with NDB's management framework.
References
* Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section:
Updating Database Server VMs
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Servers


NEW QUESTION # 130
What behavior is observed when applying patch profiles as a Super Admin?

  • A. Published patches cannot be applied if currently deprecated.
  • B. Unpublished patches can be applied.
  • C. Hidden patches can be applied.
  • D. Deprecated patches can be applied.

Answer: A

Explanation:
In the context of Nutanix Database Automation (NCP-DB), a Super Admin has the authority to apply patch profiles. However, if a patch is marked as deprecated, even if it's published, it cannot be applied. This is because deprecation is a status that indicates the patch is outdated or has been superseded by a newer version, and thus should not be used1. This behavior ensures that only the most up-to-date and secure patches are applied to the system, maintaining the integrity and security of the database environment1.


NEW QUESTION # 131
While using Time Machine (TM) to restore a source database, the option to restore data to Point in Time is not available. What should an administrator do to restore databases to Point in Time?

  • A. Restore Source DB using a snapshot
  • B. Create DB clone using a snapshot.
  • C. Update TM SLA to BRASS or lower.
  • D. Update TM SLA to BRONZE or higher.

Answer: D

Explanation:
In Nutanix Database Service (NDB), the Time Machine (TM) feature allows restores, including Point-in-Time (PIT) restores, which require continuous log retention to replay transaction logs to a specific moment. If the option to restore data to a Point in Time is unavailable, it indicates that the current Time Machine Service Level Agreement (SLA) does not support continuous log retention. NDB SLAs are categorized (e.g., BRONZE, SILVER, GOLD), with BRONZE or higher levels required to enable PIT restore by including continuous log retention. The administrator must update the TM SLA to at least BRONZE to enable this feature, ensuring logs are retained for PIT operations.
* Option A (Restore Source DB using a snapshot) is incorrect because a snapshot-only restore does not support PIT; it restores to the snapshot time only.
* Option B (Update TM SLA to BRONZE or higher) is correct as it enables continuous log retention necessary for PIT restores.
* Option C (Create DB clone using a snapshot) is incorrect because cloning from a snapshot does not provide PIT capability without log retention.
* Option D (Update TM SLA to BRASS or lower) is incorrect because "BRASS" is not a valid SLA tier, and lowering the SLA would not enable PIT.
This adjustment ensures PIT restore functionality.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Configuring SLAs for Point-in-Time Restore
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine


NEW QUESTION # 132
An administrator needs to register a Nutanix cluster with NDB.
Which condition requires the administrator to create a manual storage mapping between the remote container and NDB provisioning container?

  • A. Disaster Recovery Network Segmentation is enabled on the cluster.
  • B. DB VMs are stored in the NDB Server or NDB Provisioning container.
  • C. Nutanix Database Service High Availability is enabled on the cluster.
  • D. NDB Server container and NDB Provisioning container are separate.

Answer: D

Explanation:
When registering a Nutanix cluster with NDB, a manual storage mapping between the remote container and the NDB provisioning container is required if the NDB Server container and NDB Provisioning container are separate. This separation occurs when the storage containers used by the NDB server (for its own operations) and the provisioning container (for database VMs) are distinct, either due to multi-cluster setups or custom configurations. Manual mapping ensures NDB can correctly allocate storage resources and manage database provisioning across these containers.
Other conditions do not necessitate manual mapping:
* B. Disaster Recovery Network Segmentation is enabled on the cluster: This affects networking, not storage mapping.
* C. Nutanix Database Service High Availability is enabled on the cluster: HA configurations handle replication, not container mapping.
* D. DB VMs are stored in the NDB Server or NDB Provisioning container: This is a typical setup and does not require manual mapping unless containers differ.
Thus, the verified answer is A, addressing storage container separation.
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 Administration Guide: "Storage Container Mapping" section.


NEW QUESTION # 133
......

Nutanix Dumps - Learn How To Deal With The Exam Anxiety: https://www.passreview.com/NCP-DB_exam-braindumps.html

Ultimate Guide to NCP-DB Dumps - Enhance Your Future Career Now: https://drive.google.com/open?id=1WOB6FMimzTwvy2eW5KRE_bpdb1vGQtP1