Get Sep-2025 updated NCP-DB Certification Exam Sample Questions
NCP-DB Study Guide Cover to Cover as Literally
Nutanix NCP-DB Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 148
Which default roles are available within Era for Role-Based Access Control?
- A. Super Admin
Database Admin
Database Infrastructure Admin
prism Infrastructure Admin - B. Era Oracle Admin
Era SQLServer Admin
* Era PostgreSQL Admin
Era Mariadb Admin - C. Super Admin
Database Admin
Database Infrastructure Admin
* Infrastructure Admin - D. prism Admin
* Era Super Admin
* Era Database Admin
Era Infrastructure Admin
Answer: D
Explanation:
Nutanix Era offers Role-Based Access Control capabilities by organically embedding them in the product. It provides the ability to add and remove users from Era, create and assign roles to users, and associate various privileges with a role1. The default roles available within Era for Role-Based Access Control are:
* prism Admin
* Era Super Admin
* Era Database Admin
* Era Infrastructure Admin1 These roles allow for the management of both physical resources like IP addresses and VLANs along with database entities like databases, time-machines, clones, and so on1.
NEW QUESTION # 149
An administrator needs to increase storage for a MongoDB database provisioned using NDB. After launching the NDB CLI, the administrator begins with creating the input file for this operation.
Which parameter should the administrator include within the input file?
- A. extend_storage
- B. database
- C. update
- D. data_percent
Answer: A
Explanation:
To increase storage for a MongoDB database provisioned using NDB, the administrator needs to use the extend_storage parameter in the input file for the NDB CLI. This parameter specifies the amount of additional storage to be added to the database server VM in GB. For example, if the current storage size is 100 GB and the administrator wants to increase it to 150 GB, the input file should contain the following line:
extend_storage: 50
The other parameters are not relevant for this operation. The update parameter is used to update the database software version, the database parameter is used to specify the database name, and the data_percent parameter is used to specify the percentage of data to be copied during a clone operation. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [Nutanix Database Automation User Guide].
NEW QUESTION # 150
Refer to the exhibit.
An administrator, whose accounts are shown in the exhibit, is trying to add a new database admin as a local user to NDB, but is unable to complete the task.
What is most likely the cause of the issue?
- A. The administrator is logged in with the Database Admin account.
- B. An email address is required for the Super Admin account.
- C. The administrator is logged in with the Super Admin account.
- D. Only users in the domain admins group can create local users.
Answer: A
Explanation:
Based on the exhibit, the administrator is logged in with the Database Admin account ([email protected]), which does not have the permission to create local users on NDB. Only the Super Admin account (bsmith) has this permission, as indicated by the User type column. Therefore, the administrator needs to log out and log in again with the Super Admin account to add a new database admin as a local user to NDB. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, Nutanix Database Automation User Guide.
NEW QUESTION # 151
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 patch must have been applied on Grid home only using NDB.
- B. The patch must have been applied using NDB.
- C. The database must be shut down.
- D. The database must be in read-only mode.
Answer: B
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 # 152
A new web application performs up to 200 concurrent connections to a PostgreSQL database. An administrator needs to configure the system to provision those DB servers.
Which action would easily help the administrator achieving this goal?
- A. Provision a PostqreSQL HA Instance.
- B. Create a new Database Parameters profile.
- C. Use Post Create Command when provisioning the DB.
- D. Edit the API equivalent shell script to apply the setting.
Answer: A
Explanation:
A new web application with up to 200 concurrent connections to a PostgreSQL database requires a robust and scalable configuration. Provisioning a PostgreSQL HA (High Availability) instance in NDB is the most effective action to achieve this goal. An HA instance leverages replication (e.g., streaming replication) to distribute load and ensure availability, accommodating high concurrency by allowing multiple nodes to handle traffic. This approach simplifies configuration compared to manual scripting or parameter adjustments.
* Option A (Use Post Create Command when provisioning the DB) is incorrect because post-create commands are for custom scripts, not optimal for handling concurrent connections.
* Option B (Create a new Database Parameters profile) is incorrect because while it can tune settings, it's less efficient than HA for scaling concurrency.
* Option C (Edit the API equivalent shell script) is incorrect as it's a manual and error-prone method compared to HA provisioning.
* Option D is correct because a PostgreSQL HA instance natively supports high concurrency and availability.
Note: The typo "PostqreSQL" is assumed to mean "PostgreSQL."
References
* Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Engines, Section:
Provisioning HA Instances
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Engines
NEW QUESTION # 153
An administrator would like to replicate database snapshots to remote Nutanix clusters.
What should the administrator do to manage Time Machine data availability across all registered Nutanix clusters in NDB?
- A. Select the snapshots & replicate them to each Nutanix cluster.
- B. Add Data Access to each Nutanix cluster and assign a DAM policy.
- C. Update the cluster's Data Access & select the remote cluster.
- D. Update the SLA on the Time Machine & schedule the remote replication.
Answer: B
Explanation:
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.
References: Nutanix Support & Insights, section "NDB Data Access"
NEW QUESTION # 154
Which site needs to be reachable to ensure an NDB server can send periodic telemetry data to the central Nutanix repository over port 443?
- A. developers.nutanix.com
- B. download.nutanix.com
- C. portal.nutanix.com
- D. insights.nutanix.com
Answer: D
Explanation:
To ensure an NDB server can send periodic telemetry data to the central Nutanix repository, the server must be able to communicate with the Nutanix Insights platform over port 443 (HTTPS). The insights.nutanix.com site is the designated endpoint for telemetry data, which includes usage statistics, health metrics, and other operational data sent to Nutanix for support and analytics purposes. This connectivity is a standard requirement for NDB to comply with Nutanix's telemetry and support framework, and port 443 is used for secure transmission.
* Option A (download.nutanix.com) is incorrect because this site is used for downloading software updates, not telemetry data.
* Option B (developers.nutanix.com) is incorrect as it is a resource for developers, not a telemetry endpoint.
* Option C (portal.nutanix.com) is incorrect because this is the Nutanix customer portal for account management, not telemetry submission.
* Option D (insights.nutanix.com) is correct as it is the specific site for sending telemetry data.
The administrator should ensure network policies allow outbound traffic to this site on port 443.
References
* Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Telemetry and Connectivity Requirements
* Nutanix Support & Insights, Knowledge Base Article: "Configuring Telemetry for NDB"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 6: Administer an NDB Environment
NEW QUESTION # 155
How would an administrator enter the NDB command line to change the static IP address on the NDB VM?
- A. cerebro_cli
- B. era
- C. arithmos cli
- D. era-server
Answer: A
Explanation:
To change the static IP address on the NDB VM, an administrator would need to enter the NDB command line using the cerebro_cli command. The cerebro_cli command is used to access the Cerebro service, which is responsible for managing the NDB instance and its components. The cerebro_cli command can be run from the NDB VM or from any other VM that has network connectivity to the NDB VM. The cerebro_cli command has various subcommands and options to perform different tasks, such as changing the IP address, hostname, password, or certificate of the NDB VM. To change the static IP address, the administrator would need to use the cerebro_cli network update subcommand with the appropriate parameters, such as the new IP address, netmask, gateway, and DNS servers. The cerebro_cli network update subcommand also requires the administrator to provide the current password of the NDB VM for authentication. After changing the IP address, the administrator would need to restart the NDB VM for the changes to take effect. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.2: Configure an NDB Instance
* Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.2: Configuring NDB, Topic: Changing the IP Address of the NDB VM
* Nutanix Database Service (NDB) Command Line Interface Guide, Chapter 2: Cerebro CLI, Section:
cerebro_cli network update
NEW QUESTION # 156
While registering an Always on Availability Group database, an administrator selects the following option:
Multiple Databases as a Group with One Time Machine
Which statement is true regarding this chosen option?
- A. PITR-based SLAs are supported for database groups containing mixed Recovery Model.
- B. Point in Time Clones are not supported by Database Groups.
- C. PITR-based SLAs are not supported for database groups.
- D. PITR-based SLAs are not supported for database groups containing mixed Recovery Model
Answer: D
Explanation:
Nutanix Database Automation (NCP-DB) introduces the concept of MS SQL Server database groups, which allows multiple databases running in the same database instance to be grouped as one Time Machine entity1. This applies to both single DB Server VM setups, standalone databases, as well as to Availability Group databases1. However, it does not support Point In Time Recovery (PITR)-based Service Level Agreements (SLAs) for database groups containing mixed Recovery Models. This means that if the databases within the group have different recovery models, PITR-based SLAs cannot be applied to the group as a whole.
NEW QUESTION # 157
An administrator would like to leverage the Oracle restore feature within NDB for a RAC database.
Prior to the restoration operation, what must the administrator do?
- A. Ensure more than one node of the RAC is reachable.
- B. Ensure the database is registered with NDB.
- C. Ensure the database is in an Up state.
- D. Ensure the database is in a Down state.
Answer: B
Explanation:
To leverage the Oracle restore feature within Nutanix Database Service (NDB) for a Real Application Clusters (RAC) database, the administrator must ensure that the database is registered with NDB prior to initiating the restoration operation. Registration allows NDB to recognize the RAC database, manage its metadata, and perform operations like restore using Time Machine snapshots or backups. Without registration, NDB cannot access the necessary configuration details or protection data, rendering the restore feature unavailable.
* Option A (Ensure the database is in a Down state) is incorrect because the database state (Up or Down) is not a prerequisite for initiating a restore; the process handles state transitions.
* Option B (Ensure the database is registered with NDB) is correct as registration is the foundational requirement for NDB to manage and restore the RAC database.
* Option C (Ensure the database is in an Up state) is incorrect because an Up state is not required; restore can proceed regardless of the current state.
* Option D (Ensure more than one node of the RAC is reachable) is incorrect because while RAC node availability is important for HA, it is not a mandatory prerequisite for the restore operation itself.
This ensures the restore process can proceed with the necessary NDB oversight.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Restoring RAC Databases
* Nutanix Support & Insights, Knowledge Base Article: "Preparing Oracle RAC for Restore in NDB"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
NEW QUESTION # 158
Which command can be used to assign a static IP address to the Era VM on ESXi?
set
era-server > era
era-server >
An administrator is trying to register an Oracle Database Server VM to Era.
Which dependency must be met?
- A. /TEMP folder must have read-only permissions
- B. SUDO NOPASS access is required
- C. set path = /sbin:/bin:/usr/sbin:/usr/bin
- D. Enable reQUIREetty setting on the source database
Answer: B
Explanation:
To register an Oracle Database Server VM to Era in Nutanix Database Automation (NCP-DB), certain dependencies must be met. One of these is that SUDO NOPASS access is required1. This allows the Era service to perform necessary operations on the Oracle Database Server VM. As for assigning a static IP address to the Era VM on ESXi, you can use the vSphere Client to configure static IP settings2. However, this is not directly related to the registration of an Oracle Database Server VM to Era. 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 # 159
What is causing this issue?
- A. The VLAN is static
- B. The VLAN is stretched
- C. The VLAN is IPAM
- D. TheVLANisDHCP
Answer: B
Explanation:
The correct answer is C because a stretched VLAN is a VLAN that spans across multiple Nutanix clusters, which may cause network conflicts or latency issues when starting the database server. Option A is incorrect because a DHCP VLAN is a VLAN that uses dynamic IP address allocation, which does not affect the database server startup. Option B is incorrect because a static VLAN is a VLAN that uses fixed IP address allocation, which also does not affect the database server startup. Option D is incorrect because IPAM is not a type of VLAN, but a feature of NDB that allows managing IP addresses for database servers and databases.
References: The following sources provide more information about the VLAN and IPAM concepts and configuration in NDB:
* Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Configuring NDB High Availability
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section
2 - Deploy and Configure an NDB Solution
* Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section 2.4: Configuring NDB High Availability
* Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section
8.5: Managing Networks in NDB
* Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section
8.6: Managing IP Addresses in NDB
NEW QUESTION # 160
An administrator wants to test the provisioning capabilities after a new NDB deployment. Which database instance would be available to accomplish this task?
- A. MongoDB
- B. Oracle DB
- C. MSSQL Server
- D. PostgreSQL
Answer: D
Explanation:
After a new NDB deployment, the administrator can test the provisioning capabilities using a database instance that is fully supported and readily configurable out of the box. PostgreSQL is the most suitable option because it is one of the core database engines supported by NDB from the initial deployment, with built-in provisioning templates and HA capabilities. NDB provides a streamlined process to provision PostgreSQL instances, making it an ideal choice for testing provisioning workflows, including VM creation, storage allocation, and network configuration.
Other options may require additional setup or licensing:
* B. Oracle DB: Requires specific licensing and additional configuration, not typically available for initial testing.
* C. MSSQL Server: Supported but may need Microsoft licensing and setup, less immediate than PostgreSQL.
* D. MongoDB: Supported but less commonly used for initial testing due to its NoSQL nature and additional configuration needs.
Thus, the verified answer is A, reflecting PostgreSQL's accessibility for testing.
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) v6.5 Knowledge Objectives, Section
3: Manage NDB Solutions, Objective 3.1: Provision Database Instances (applicable to v6.10).
* Nutanix NDB Administration Guide: "Supported Databases for Provisioning" section, noting PostgreSQL availability.
NEW QUESTION # 161
A database is de-registered without removing the associated Time Machine. What is the status of the Time Machine?
- A. Frozen
- B. Paused
- C. Active
- D. Ready
Answer: A
Explanation:
When a database is de-registered from NDB without removing the associated Time Machine, the Time Machine enters a "Frozen" state. In this state, the Time Machine retains all existing snapshots and protection data but ceases to perform new snapshot captures or log catch-up operations. This allows the administrator to preserve the historical data for potential future use (e.g., auditing or recovery) while halting active management. The Frozen state prevents further modifications until the database is re-registered or the Time Machine is explicitly deleted.
* Option A (Ready) is incorrect because "Ready" implies the Time Machine is active and prepared for new operations, which is not the case post-de-registration.
* Option B (Frozen) is correct as it reflects the paused protection state after de-registration without removal.
* Option C (Paused) is incorrect because "Paused" is not a formal Time Machine state in NDB;
"Frozen" is the specific term.
* Option D (Active) is incorrect because the Time Machine cannot remain active without an associated registered database.
This state provides flexibility for data retention without ongoing resource use.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Time Machine States
* Nutanix Support & Insights, Knowledge Base Article: "Understanding Time Machine States After De- registration"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
NEW QUESTION # 162
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 # 163
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 deletes the cloned database VM.
- B. NDB marks the cloned database as offline.
- C. NDB de-registers the cloned database.
- D. NDB deletes the cloned database.
Answer: C,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 # 164
An administrator needs to protect a database with a Point In Time Recovery (PITR) SLA that provides a minimum of seven days of log recovery.
What is the minimum Default SLA that meets this requirement?
- A. DEFAULT_008 GOLD SLA
- B. DEFAULT_008 SILVER SLA
- C. DEFAULT_008 BRONZE SLA
- D. DEFAULT_008 BRASS SLA
Answer: B
Explanation:
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.
References:
* Nutanix Era User Guide/SLA Management: https://portal.nutanix.com/page/documents/details?
targetId=Nutanix-NDB-User-Guide-v2_5:top-sla-management-c.html ]
NEW QUESTION # 165
Which Era component collects logs and snapshots from the database?
- A. Profiles
- B. Time Machine
- C. SLAs
- D. Era Database Agent
Answer: B
Explanation:
The Era copy data management service includes several components, one of which is the Time Machine. The Time Machine is responsible for collecting logs and snapshots from the database123. This functionality allows for granular clone and refresh operations, making it a crucial part of the Nutanix Era's database as a service (DBaaS) solution1.
NEW QUESTION # 166
What is the minimum frequency in minutes configurable for NDB Log Catch-up operation?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: A
Explanation:
The minimum frequency configurable for the NDB Log Catch-up operation is 15 minutes. This setting determines how frequently the log catch-up process runs, which is crucial for maintaining data integrity and ensuring up-to-date database states.References:Nutanix Database Automation documentation, focusing on log management and catch-up operation settings.
NEW QUESTION # 167
Which statement describes a user in Era with the Database Infrastructure Admin role?
- A. The user is able to manage software profiles, Network Profiles. database parameter profiles end Time Machine SLAs,
- B. The user is able to manage software profiles, Network Profiles. database Instance parameter profiles and time machine SLA
- C. The user is able to manage database profiles, Network Profiles, database Instance parameter profiles and time machine SLA
- D. The user is able to manage software profiles, database parameter profiles and SLAs
Answer: A
Explanation:
The size of a database Time Machine in Nutanix Era is defined by the size of all snapshots and/or transaction logs maintained by Era1. The Time Machine leverages Nutanix's efficient snapshot technology to capture the state of the database at different points in time1. These snapshots, along with transaction logs that record changes between snapshots, constitute the data maintained by the Time Machine1. Therefore, the size of the Time Machine is determined by the total size of these snapshots and transaction logs1.
NEW QUESTION # 168
What feature of Era allows an administrator to create Time Machine policies in a Multi-Cluster configuration?
- A. Data Access Management
- B. Global Service Level Agreement
- C. Time Machine Cloud Orchestration
- D. Global Data Protection
Answer: B
Explanation:
The Global Service Level Agreement (SLA) feature of Era allows an administrator to create Time Machine policies in a Multi-Cluster configuration1. This feature provides a unified way to manage and enforce backup and replication policies across multiple clusters, ensuring consistent data protection and recovery across the entire environment1.
NEW QUESTION # 169
What is the first step to install NDB on a Nutanix AHV cluster?
- A. Run LCM update to get the latest version of NDB.
- B. Download the QCOW2 image file of NDB and upload it to Prism Element.
- C. NDB is offered as a SaaS service and doesn't require any installations.
- D. Open Prism Central and enable the NDB VM in the settings menu.
Answer: B
Explanation:
To install NDB on a Nutanix AHV cluster, you need to download the QCOW2 image file of NDB from the Nutanix Support Portal and upload it to Prism Element. This image file contains the NDB software and the CentOS operating system. After uploading the image, you need to create a VM from the image and configure the network settings. Then, you need to register the NDB VM with Prism Central and enable the NDB service in the settings menu. References: Nutanix Support & Insights, Professional Services: NDB Database Cloning
NEW QUESTION # 170
An administrator needs to restore a database provisioned on Storage Spaces. The virtual disks are shared with multiple databases.
Which restore method is supported?
- A. Disk-based restore via NDB GUI
- B. Disk-based restore via NDB CLI
- C. Copy-based restore via NDB CLI
- D. Copy-based restore via NDB GUI
Answer: D
Explanation:
For restoring a database provisioned on Storage Spaces, especially when virtual disks are shared among multiple databases, the supported method is a copy-based restore via the NDB GUI. This method allows for a precise and controlled restoration process suitable for shared storage environments.References:Nutanix Database Automation documentation, specifically in the section on database restoration methods and storage spaces.
NEW QUESTION # 171
......
100% Real & Accurate NCP-DB Questions and Answers with Free and Fast Updates: https://protechtraining.actualtestsit.com/Nutanix/NCP-DB-exam-prep-dumps.html