NCP-DB Exam PDF [2024] Tests Free Updated Today with Correct 77 Questions
Nutanix NCP-DB Exam Preparation Guide and PDF Download
NEW QUESTION # 13
Which response shows two ways to upgrade an NDB Server?
- A. Out-of-Place Upgrade and In-place Upgrade
- B. One-click Upgrade and Offline Upgrade
- C. Upgrade and Manual Upgrade
- D. One-click Upgrade and In-place Upgrade Auto
Answer: B
Explanation:
There are two ways to upgrade an NDB Server: one-click upgrade and offline upgrade. One-click upgrade is the recommended method, as it automatically downloads and installs the latest NDB software version from the Nutanix portal. Offline upgrade is an alternative method, which requires you to manually download the NDB software bundle and upload it to the NDB Server VM. Both methods require you to have a valid Nutanix account and an internet connection. References:
* Nutanix Certified Professional - Database Automation (NCP-DB), Section 6 - Administer an NDB Environment
* Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 10, Objective 6.2
* Nutanix Database Management & Automation (NDMA) course, Module 6, Lesson 6.1 - NDB Software Upgrade
NEW QUESTION # 14
An administrator needs to perform patching on a MongoDB server cluster within an NDB environment.
How should the administrator accomplish this task?
- A. Perform a rolling upgrade, applying the patch to the primary member first, followed by the secondary members.
- B. Apply the patch to all nodes at once.
- C. Perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member.
- D. Disable the replica set while patching.
Answer: C
Explanation:
The administrator should perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, to accomplish the task of patching a MongoDB server cluster within an NDB environment. A rolling upgrade is a method of applying patches or updates to a cluster without downtime or interruption of service. The administrator can use the NDB patching feature to perform a rolling upgrade on a MongoDB server cluster, which consists of a primary member and one or more secondary members that form a replica set. The NDB patching feature allows the administrator to select the software profile version, the database parameters profile, and the network profile for the patching operation. The NDB patching feature also automates the steps of the rolling upgrade, such as:
* Step 1: The administrator initiates the patching operation on the NDB instance, and selects the MongoDB server cluster to be patched.
* Step 2: The NDB instance verifies the prerequisites and compatibility of the patching operation, and creates a pre-patch snapshot of the MongoDB server cluster.
* Step 3: The NDB instance applies the patch to the first secondary member of the MongoDB server cluster, and waits for the patching to complete successfully.
* Step 4: The NDB instance verifies the status and functionality of the patched secondary member, and repeats the patching process for the remaining secondary members of the MongoDB server cluster, one at a time.
* Step 5: The NDB instance performs a failover of the primary member to one of the patched secondary members, and applies the patch to the original primary member.
* Step 6: The NDB instance verifies the status and functionality of the patched primary member, and performs a failback of the primary member to the original primary member, if desired.
* Step 7: The NDB instance creates a post-patch snapshot of the MongoDB server cluster, and completes the patching operation.
Performing a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, is the recommended and best practice method of patching a MongoDB server cluster within an NDB environment, as it ensures the high availability, consistency, and performance of the MongoDB server cluster and the databases.
Performing a rolling upgrade, applying the patch to the primary member first, followed by the secondary members, is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to the primary member first would disrupt the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to restore the MongoDB server cluster to a functional state.
Applying the patch to all nodes at once is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to all nodes at once would require shutting down the entire MongoDB server cluster, and would expose the MongoDB server cluster and the databases to potential errors, failures, and corruption during the patching process.
Disabling the replica set while patching is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Disabling the replica set while patching would break the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to re-enable the replica set and restore the MongoDB server cluster to a functional state.
References:
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 11-12, 15-16.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.3: Nutanix Era Patching, slides 5-9.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.4: Nutanix Era Patching Lab, slides 5-10.
* Nutanix Database Management & Automation Training Course, Module 7: Nutanix Era Troubleshooting, Lesson 7.1: Nutanix Era Troubleshooting, slide 6.
NEW QUESTION # 15
An administrator needs to perform LCM upgrades on an AHV cluster registered with NDB. The cluster hosts NDB-provisioned database server VMs that are part of a database server cluster.
What should the administrator do to allow the DB Server VMs to stay available while the cluster is being upgraded?
- A. Unset VM-Host Affinity
- B. Update Nutanix Cluster
- C. Remove Nutanix Cluster
- D. Set VM-Host Affinity
Answer: D
Explanation:
The correct answer is B because setting VM-Host affinity ensures that the DB Server VMs are not migrated to another host during the LCM upgrade process. This way, the DB Server VMs can continue to serve the database requests without interruption. Option A is incorrect because updating the Nutanix cluster does not prevent the DB Server VMs from being moved to another host. Option C is incorrect because removing the Nutanix cluster from NDB will make the DB Server VMs unmanaged by NDB and lose thebenefits of NDB features. Option D is incorrect because unsetting VM-Host affinity will allow the DB Server VMs to be migrated to another host during the LCM upgrade process, which may cause downtime or performance degradation.
References: The following sources provide more information about the LCM upgrades and VM-Host affinity in NDB:
* Nutanix Database Management & Automation (NDMA) course, Module 6: Administering an NDB Environment, Lesson 6.3: Performing NDB Software Upgrades
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section
6 - Administer an NDB Environment
* Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section
8.3: Performing NDB Software Upgrades
* Nutanix Support & Insights, Your guide to the Upgrades, LCM Design
* Nutanix Life Cycle Manager Guide, Chapter 3: Upgrading Software and Firmware, Section 3.2:
Preparing for an Upgrade, VM-Host Affinity
NEW QUESTION # 16
An administrator is interested in using profiles to simplify the database provisioning process. The profile needs to include information related to the SQL service startup account, and the NDB worker service account.
Which profile would help the administrator accomplish this task?
- A. Windows Domain
- B. Software
- C. Database Parameter
- D. Network
Answer: A
Explanation:
The correct answer is A because the Windows Domain profile is the profile that includes information related to the SQL service startup account and the NDB worker service account. A Windows Domain profile is a collection of settings that define how NDB manages Windows-based database servers and databases. It contains the following information:
* The domain name and credentials to join the database server VMs to the domain
* The SQL service startup account and password to run the SQL Server service on the database server VMs
* The NDB worker service account and password to run the NDB Database Agent service on the database server VMs
* The SQL Server authentication mode to use for the databases
By using a Windows Domain profile, the administrator can simplify the database provisioning process by applying the same settings to multiple database server VMs and databases, without having to manually enter them each time. The other options are not correct because they describe different types of profiles that do not include information related to the SQL service startup account and the NDB worker service account. Option B is not correct because the Network profile is a profile that defines the network settings for the database server VMs, such as the IP address, subnet mask, gateway, DNS, and VLAN. Option C is not correct because the Database Parameter profile is a profile that defines the database parameters for the databases, such as the memory, CPU, storage, and performance settings. Option D is not correct because the Software profile is a profile that defines the software settings for the database server VMs and databases, such as the database engine version, edition, and features. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DBCertification Exam Syllabus and Study Guide, Nutanix Database Services: Database modernization with Era - Now available
NEW QUESTION # 17
An administrator created a database clone that is scheduled for removal on the last day of the month.
A request has been received to keep the clone for an additional 14 days.
After selecting the desired clone, how should the administrator satisfy this task?
- A. Select Update and modify the Removal schedule.
- B. Remove the Removal schedule, then add the desired removal schedule.
- C. Update the Removal schedule to the end of the month.
- D. Update the Removal schedule to the desired date.
Answer: A
Explanation:
The Removal schedule is a feature of Nutanix Era that allows you to specify when a database clone will be automatically deleted. You can modify the Removal schedule of an existing clone by selecting the clone from the Clones page, clicking on the Update button, and changing the Removal schedule option to the desired date.
This way, you can extend or shorten the lifespan of a clone as per your requirements. You do not need to remove the existing Removal schedule and add a new one, as this would be an unnecessary step. You also do not need to update the Removal schedule to the end of the month, as this would not meet the request of keeping the clone for an additional 14 days. References:
* Nutanix Database Management & Automation Training Course, Module 4: Protecting Databases Using Time Machine, Lesson 3: Cloning Databases, Slide 10: Clone Removal Schedule
* Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 5: Protect NDB-managed Databases Using Time Machine, Objective 5.3: Given business requirements, perform a database clone
NEW QUESTION # 18
An administrator is tasked with providing a Jr DBA with access to NBD with limited capabilities.
This user should only be able to:
* Provision Databases
* Provision Database Servers
* Create Ones
* Refresh Clones
* Patch Database Servers
How can the administrator complete this task?
- A. Clone the Database Admin role, and remove all but the desired privileges.
- B. Create a user for the Jr DBA, and assign only those privileges.
- C. Clone the Database Admin role, and add the desired privileges.
- D. Create a role with only those privileges, assign the role to the Jr DBA user.
Answer: D
Explanation:
The correct answer is B because it allows the administrator to create a custom role with the specific privileges that the Jr DBA user needs, and then assign that role to the user. This way, the administrator can control the access level of the Jr DBA user without affecting the existing roles or users in NDB. Option A is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then adding more privileges, which is unnecessary and redundant. Option C is incorrect because it involves creating a user for the Jr DBA, but not assigning a role to the user, which means the user will not have any privileges in NDB. Option D is incorrect because it involves cloning the Database Admin role, which has more privileges than the Jr DBA user requires, and then removing some of the privileges, which is inefficient and risky.
References: The following sources provide more information about the user roles and privileges in NDB:
* Nutanix Database Management & Automation (NDMA) course, Module 8: Administering an NDB Environment, Lesson 8.6: Managing Access Controls in NDB
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section
6 - Administer an NDB Environment
* Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section
8.6: Managing Access Controls in NDB
NEW QUESTION # 19
What is the purpose of Data Access Management policies in NDBMulti-Cluster?
- A. To manage time machine data availability across all registered Nutanix clusters in NDB
- B. To remove data accessibility of a time machine across all registered Nutanix clusters in NDB
- C. To register multiple Nutanix clusters in NDB
- D. To perform snapshot operations on a single Nutanix cluster
Answer: A
Explanation:
Data Access Management (DAM) policies are a feature of NDB Multi-Cluster that allows you to control the access and availability of time machine data across different Nutanix clusters. You can use DAM policies to specify which clusters can access the time machine data of a source database, and which clusters can replicate the time machine data for backup or disaster recovery purposes. DAM policies help you to optimize the storage and network resources, as well as ensure the security and compliance of your database workloads. The purpose of DAM policies is not to register multiple Nutanix clusters in NDB, as this is done by using the Add Cluster option in the NDB settings page. The purpose of DAM policies is also not to perform snapshot operations on a single Nutanix cluster, as this is done by using the Time Machine feature in the NDB dashboard. The purpose of DAM policies is also not to remove data accessibility of a time machine across all registered Nutanix clusters in NDB, as this is done by using the Delete option in the Time Machine page. References:
* Nutanix Database Management & Automation Training Course, Module 6: Managing NDB Multi-Cluster, Lesson 2: Data Access Management Policies, Slide 3: Data Access Management Policies
* Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 6: Administer an NDB Environment, Objective 6.5: Apply procedural concepts to create Data Access Management (DAM) policies
NEW QUESTION # 20
An administrator needs to patch an Oracle Database Server VM and must ensure Grid home is allocated sufficient storage space.
At a minimum, how much space must be available for Grid home prior to completing this task?
- A. 20 GB
- B. 5 GB
- C. 10GB
- D. 15GB
Answer: C
Explanation:
When patching an Oracle Database Server VM, it's important to ensure that there is sufficient storage space allocated for the Grid home. A minimum of 10GB space is required for this purpose to accommodate the patching process without storage constraints.References:Nutanix Database Automation documentation, particularly in the sections discussing Oracle database server VM management and patching requirements.
NEW QUESTION # 21
What is the first step to add Time Machine (TM) data access to a Nutanix cluster?
- A. Delete the TM data from the source database.
- B. Register the required Nutanix clusters in ND8.
- C. Disable multi-cluster in ND8.
- D. Enable multi-cluster in NDB.
Answer: B
Explanation:
To add Time Machine data access to a Nutanix cluster, the first step is to register the cluster in NDB. This will allow NDB to discover and manage the databases and snapshots on the cluster. You can register multiple Nutanix clusters in NDB using the Add Cluster option in the NDB settings page. You can also specify the cluster role, such as source, target, or both, depending on the data access and replication needs. Enabling or disabling multi-cluster in NDB is not the first step, as this is a global setting that affects the entire NDB instance. Deleting the TM data from the source database is not the first step, as this will remove the data protection and availability of the database. References:
* Nutanix Database Management & Automation Training Course, Module 6: Managing NDB Multi-Cluster, Lesson 1: NDB Multi-Cluster Overview, Slide 5: Registering Nutanix Clusters
* Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 6: Administer an NDB Environment, Objective 6.4: Apply procedural concepts to add Nutanix clusters to NDB
NEW QUESTION # 22
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. database
- B. update
- C. extend_storage
- D. data_percent
Answer: C
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 # 23
Which disk is omitted from a Software Profile?
- A. System Page File
- B. SQL Installation
- C. System Database
- D. User Database
Answer: A
Explanation:
According to the Nutanix Database Automation (NCP-DB) course, a Software Profile is a template that defines the configuration of the database engine, such as the version, edition, features, and parameters1. It also specifies the disk layout for the database installation, such as the size, type, and mount point of each disk1. However, the System Page File disk is omitted from the Software Profile, as it is automatically created by the NDB service based on the memory size of the database server VM1. The other options are included in the Software Profile, as they are essential for the database operation and performance1. References:
* 1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.3:
Software Profiles, slide 5
NEW QUESTION # 24
How can HA drivers for a Database VM be upgraded?
- A. Database software patching
- B. One-click software upgrade
- C. LCM driver upgrade
- D. Database VM OS patching
Answer: C
Explanation:
HA drivers are software components that enable high availability features for database VMs, such as failover, fencing, and heartbeat. HA drivers can be upgraded using the Life Cycle Management (LCM) feature of Nutanix Prism. LCM can detect the available updates for HA drivers and apply them to the database VMs in a non-disruptive manner. LCM can also perform health checks and pre-upgrade validations to ensure the successful completion of the upgrade process. One-click software upgrade is a feature of Nutanix Era that allows you to upgrade the Era software itself, not the HA drivers. Database VM OS patching is a feature of Nutanix Era that allows you to patch the operating system of the database VMs, not the HA drivers. Database software patching is a feature of Nutanix Era that allows you to patch the database software of the database VMs, not the HA drivers. References:
* Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 3: Configuring NDB High Availability, Slide 9: HA Driver Upgrade
* Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.4: Upgrade databases
NEW QUESTION # 25
What does a Time Machine frozen status indicate?
- A. The Time Machine is paused and all automatic snapshot and log catch-up activities are halted.
- B. The NDB agent is stopped on the database VM.
- C. The database is paused on the database VM.
- D. The database was de-registered fromNDB withoutremoving the associated time machine.
Answer: D
Explanation:
A Time Machine frozen status indicates that the database that was associated with the Time Machine has been de-registered from NDB, but the Time Machine itself has not been deleted. This means that the Time Machine still contains the snapshots and logs of the de-registered database, but it cannot perform any further operations on it. To resume the normal functioning of the Time Machine, the administrator can either re-register the database with NDB, or delete the Time Machine and free up the storage space.
References: Nutanix Support & Insights, section "Resolving All Alerts for a Time Machine"
NEW QUESTION # 26
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 in read-only mode.
- B. The patch must have been applied using NDB.
- C. The patch must have been applied on Grid home only using NDB.
- D. The database must be shut down.
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 # 27
A database administrator wants to define initialization variables for different types of database engines and workloads, like OLTP and DW.
What type of profile would be used?
- A. Software Profile Version
- B. Network
- C. Compute
- D. Database Parameters
Answer: D
Explanation:
The database parameters profile is used to define the initialization variables for different types of database engines and workloads, such as OLTP and DW. The database parameters profile allows the database administrator to customize the configuration settings for each database engine, such as Oracle, SQL Server, PostgreSQL, and MySQL. The database parameters profile can also be applied to different database operations, such as provisioning, cloning, and patching. The database parameters profile helps to optimize the performance and functionality of the databases according to the specific requirements and best practices of each database engine and workload.
The software profile version is used to define the software version and edition for each database engine, such as Oracle 19c Enterprise Edition or SQL Server 2019 Standard Edition. The software profile version is required for provisioning new databases and patching existing databases. The software profile version helps to ensure the compatibility and compliance of the databases with the supported software versions and editions.
The network profile is used to define the network configuration and security settings for the database server VMs and the databases, such as the IP address, subnet mask, gateway, DNS, firewall rules, and SSL certificates. The network profile is required for registering new database server VMs and provisioning new databases. The network profile helps to ensure the connectivity and protection of the database server VMs and the databases within the network environment.
The compute profile is used to define the compute resources and storage policies for the database server VMs and the databases, such as the CPU, memory, disk size, disk type, compression, deduplication, and replication factor. The compute profile is required for provisioning new databases and cloning existing databases. The compute profile helps to ensure the availability and efficiency of the database server VMs and the databases within the Nutanix cluster.
References:
* Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slides 6-9.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 5-8, 11-12, 15-16.
NEW QUESTION # 28
A development team has requested that an administrator provide them a copy of the production Finance database. The business requires that any financial data is masked before going into development.
How should the administrator create a clone with masked data for the development environment?
- A. From the Time Machine, create a clone and paste the masking commands in the pre-clone field of the Pre-Post Commands section.
- B. 1. Create a masking script on the source DB VM, Dev VM or SW Profile VM.
2. Create the clone from the Time Machine and define the post-clone option with the full path\name of the masking script. - C. 1. Create a script to mask the data.
2. Create the clone from the Time Machine and define the post-clone option with the full path\name of the masking script. - D. From the Time Machine, create a clone and paste the masking commands in the post-clone field of the Pre-Post Commands section.
Answer: B
Explanation:
According to the Nutanix Database Automation (NCP-DB) course, the Pre-Post Commands section allows the administrator to specify custom scripts that can be executed before or after the clone operation1. The masking script can be created on any of the VMs that have access to the source database, such as the source DB VM, the Dev VM, or the SW Profile VM2. The script should contain the commands to mask the sensitive data in the Finance database, such as replacing the real values with dummy values or encrypting the data2. The administrator can then create the clone from the Time Machine and define the post-clone option with the full path and name of the masking script1. This will ensure that the script is executed after the clone is created, and the data is masked before it is available for the development team1. The other options are not correct, as they either use the wrong field (pre-clone instead of post-clone), or do not specify where to create or store the masking script. References:
* 1: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 5
* 2: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 7
NEW QUESTION # 29
......
Verified & Correct NCP-DB Practice Test Reliable Source Apr 03, 2024 Updated: https://www.dumpsreview.com/NCP-DB-exam-dumps-review.html
Free Nutanix NCP-DB Exam Files Downloaded Instantly: https://drive.google.com/open?id=1xa79FF2UuJiMrUrWFzmzr32Q0gUD5Jc-
