TAKE Nutanix Certified Professional (NCP) NCP-DB PRACTICE QUESTIONS FOR AMAZING RESULTS
Nutanix NCP-DB Exam Dumps Are Essential To Get Good Marks
NEW QUESTION # 32
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. Update Nutanix Cluster
- B. Set VM-Host Affinity
- C. Remove Nutanix Cluster
- D. Unset VM-Host Affinity
Answer: B
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 # 33
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. Disable the replica set while patching.
- C. Apply the patch to all nodes at once.
- D. Perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member.
Answer: D
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 # 34
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. Create a role with only those privileges, assign the role to the Jr DBA user.
- B. Clone the Database Admin role, and add the desired privileges.
- C. Clone the Database Admin role, and remove all but the desired privileges.
- D. Create a user for the Jr DBA, and assign only those privileges.
Answer: A
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 # 35
What are two status values that can be set within the Alerts Dashboard? (Choose two.)
- A. Auto
- B. Data Resiliency
- C. Resolved
- D. Acknowledged
Answer: C,D
Explanation:
The correct answer is B and D because these are the two status values that can be set within the Alerts Dashboard in NDB. Resolved means that the alert has been fixed and no longer requires attention.
Acknowledged means that the alert has been seen and is being worked on. Option A is incorrect because Auto is not a status value, but a mode that automatically resolves alerts based on predefined rules. Option C is incorrect because Data Resiliency is not a status value, but a feature that ensures the availability and integrity of the data in NDB.
References: The following sources provide more information about the Alerts Dashboard and its status values in NDB:
* Nutanix Database Management & Automation (NDMA) course, Module 3: Monitoring Alerts and Storage Usage Within an NDB Implementation, Lesson 3.1: Monitoring Alerts
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section
3 - Monitor Alerts and Storage Usage Within an NDB Implementation
* Nutanix Database Service (NDB) User Guide, Chapter 3: Monitoring Alerts and Storage Usage Within an NDB Implementation, Section 3.1: Monitoring Alerts
* [Nutanix Support & Insights], Resolving All Alerts Related to a Database or Database Server VM in NDB
NEW QUESTION # 36
An administrator has been tasked with restoring an Oracle database that has recently failed. The administrator must restore the database to the prior day's state.
Which two restore options could be used? (Choose two.)
- A. Snapshot
- B. Tail Logs Backup
- C. Most Recent Time Available
- D. Point in Time
Answer: A,D
Explanation:
The correct answer is B and D because they are the two restore options that can be used to restore an Oracle database to the prior day's state using Nutanix Era. A snapshot is a point-in-time copy of a database that is stored in the Era Time Machine, which is a distributed file system that collects logs and snapshots from databases. A point in time is a specific moment in time within the retention period of the SLA policy that is applied to the database. By using either of these options, the administrator can select the snapshot or the point in time that corresponds to the prior day's state and restore the database from it. The other options are not correct because they are not restore options that are available in Nutanix Era. Option A is not correct because Most Recent Time Available is not a restore option, but a clone option that creates a clone of the database from the most recent snapshot or log backup. Option C is not correct because Tail Logs Backup is not a restore option, but a backup option that captures thetransaction logs of the database that have not been backed up by the SLA policy. 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 Database Services: Database modernization with Era - Now available]
NEW QUESTION # 37
Within NDB, an administrator needs to register a PostgreSQL database server VM with a database.
Where should the database data and log files be located in order to successfully complete this task?
- A. On the same disk as the operating system
- B. On the same mount point
- C. On the same disk as the binary installation
- D. On a separate mount point
Answer: D
Explanation:
To register a PostgreSQL database server VM with a database on NDB, the database data and log files must be located on a separate mount point from the operating system and the binary installation. This is because NDB uses the mount point as the identifier for the database server VM and the database. If the data and log files are on the same mount point as the operating system or the binary installation, NDB will not be able to recognize them as a valid database server VM or database. Therefore, the administrator should create a separate mount point for the data and log files and specify it during the registration process. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [How to Allow Remote Access to PostgreSQL database], [5 Ways to Host PostgreSQL Databases], [Starting the Database Server].
NEW QUESTION # 38
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. Network
- B. Windows Domain
- C. Software
- D. Database Parameter
Answer: B
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 # 39
What does a Time Machine frozen status indicate?
- A. The NDB agent is stopped on the database VM.
- B. The database is paused on the database VM.
- C. The Time Machine is paused and all automatic snapshot and log catch-up activities are halted.
- 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 # 40
An administrator needs to create a custom PostgreSQL HA software profile.
Which software component manages the state of the cluster and handles failover?
- A. keepa lived
- B. HAProxy
- C. Patroni
- D. etcd
Answer: C
Explanation:
NDB supports PostgreSQL HA software profiles for provisioning PostgreSQL databases with high availability. PostgreSQL HA software profiles consist of three components: etcd, HAProxy, and Patroni.
etcd is a distributed key-value store that provides a reliable way to store configuration data across a cluster of machines. etcd is used by Patroni to store and synchronize the cluster state and configuration.
HAProxy is a load balancer that distributes incoming requests to the PostgreSQL nodes. HAProxy is used to expose a single endpoint for database connections even as the roles of the individual nodes change.
Patroni is a template for PostgreSQL high availability. Patroni is responsible for managing the state of the cluster and handling failover. Patroni uses etcd as the distributed configuration store and relies on HAProxy for load balancing.
Therefore, the software component that manages the state of the cluster and handles failover is Patroni.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 2.4: Provisioning PostgreSQL Databases
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.4: Provision PostgreSQL Databases
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.4: Provisioning PostgreSQL Databases
* [Nutanix Database Automation (NCP-DB) User Guide], Section 2.4: Provision PostgreSQL Databases
* [PostgreSQL High Availability: Under the Hood - Nutanix.dev]
NEW QUESTION # 41
What is the minimum frequency in minutes configurable for NDB Log Catch-up operation?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: D
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 # 42
What happens to the primary member in a MongoDB Server Cluster during the NDB patching process?
- A. It is patched last and is restored to its original state.
- B. It is patched first and then becomes a secondary member.
- C. It is skipped during the patching process to ensure no downtime.
- D. It becomes a read-only member during the patching process.
Answer: B
Explanation:
According to the NDB documentation, the NDB patching process for MongoDB Server Cluster follows these steps1:
* NDB identifies the primary member of the MongoDB Server Cluster and patches it first.
* NDB triggers a failover to elect a new primary member from the remaining secondary members.
* NDB patches the former primary member, which becomes a secondary member after the failover.
* NDB patches the remaining secondary members one by one.
* NDB verifies the patching status and the cluster health.
This process ensures that the MongoDB Server Cluster always has a primary member available to handle write operations, while minimizing the downtime and the impact on the cluster performance.
References: Nutanix Support & Insights, section "Patching a MongoDB Server Cluster"
NEW QUESTION # 43
Which ports are used by the NDB database agent for API calls?
- A. 443 and 9440
- B. 5985 and 9389
- C. 3205 and 3260
- D. 443 and 8080
Answer: A
Explanation:
The NDB database agent is a service that runs on each database server VM and communicates with the NDB instance. It uses port 443 for HTTPS API calls and port 9440 for Nutanix cluster API calls. These ports are required to be open on the database server VMs for NDB to function properly. References: Nutanix Database Management & Automation (NDMA), page 9; Ports and Protocols Reference Chart | Nutanix Community, section "Nutanix Database Service (NDB)"
NEW QUESTION # 44
An administrator is tasked with auditing NDB SLAs. What data will the administrator be reviewing?
- A. Clone Management
- B. Data retention policies
- C. Snapshot schedules
- D. Recovery Time Objective
Answer: B
Explanation:
NDB SLAs are service level agreements that define the data protection and recovery objectives for NDB-managed databases. NDB SLAs consist of data retention policies that specify how long the snapshots and log backups of a database are kept in the Time Machine. Data retention policies can be customized to meet different business and compliance requirements, such as daily, weekly, monthly, or yearly retention periods.NDB SLAs also determine the frequency and schedule of the snapshots and log backups, as well as the storage location and replication options. An administrator who is tasked with auditing NDB SLAs will be reviewing the data retention policies of each database and Time Machine, as well as the snapshot and log backup history and status. The administrator will also be able to monitor the storage usage and performance of the NDB SLAs, and modify or delete the SLAs as needed. The other options are not part of the NDB SLAs, but rather separate features or concepts of NDB. Snapshot schedules are the intervals at which NDB takes snapshots of the databases, which are determined by the SLAs. Clone management is the process of creating, refreshing, or deleting database clones from the Time Machine. Recovery time objective (RTO) is the maximum acceptable time for restoring a database after a failure, which is influenced by the SLAs, but not defined by them. 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: SLA Concepts
* Nutanix Database Service (NDB) User Guide, Chapter 6: SLAs, Section: SLA Overview
NEW QUESTION # 45
What is purpose of the NDB Database Agent service?
- A. Temporarily stores the transaction logs.
- B. Hosts one or more source databases for the same time machine.
- C. Contains an instance of the database engine software.
- D. Schedules and monitors the NDB-related operations.
Answer: D
Explanation:
The correct answer is C because the NDB Database Agent service is responsible for scheduling and monitoring the NDB-related operations, such as provisioning, patching, cloning, and restoring databases. The NDB Database Agent service is deployed on the NDB server and on each of the database server VMs provisioned by NDB. It contains the tools required to perform each task and communicates with the NDB server through the NDB API. The other options are not correct because they describe different components or functions of the NDB solution. Option A is not correct because the transaction logs are not stored by the NDB Database Agent service, but by the NDB Time Machine service, which is a distributed file system that stores the database snapshots and logs. Option B is not correct because the source databases are not hosted by the NDB Database Agent service, but by the database server VMs, which are virtual machines that contain an instance of the database engine software and the database files. Option D is not correct because the NDB Database Agent service does not contain an instance of the database engine software, but only the tools required to perform the NDB-related operations. The database engine software is installed on the database server VMs, which are provisioned by NDB using the profiles defined by the administrator. 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 Support & Insights
NEW QUESTION # 46
An administrator needs to distribute NDB management plane components.
Which NDB HA VM needs to be deployed on the same L2 network?
- A. API Server
- B. Repository VMs
- C. NDB Agent
- D. HA Proxy VMs
Answer: D
Explanation:
NDB High Availability (HA) is a feature that ensures the availability and reliability of the NDB management plane components, such as the API Server, the Repository VMs, and the NDB Agents. To enable NDB HA, you need to deploy at least three HA Proxy VMs on the same L2 network as the NDB Server VM. The HA Proxy VMs act as load balancers and health monitors for the NDB management plane components, and they also provide a single endpoint for accessing the NDB APIs and UI. References:
* Nutanix Certified Professional - Database Automation (NCP-DB), Section 2 - Deploy and Configure an NDB Solution
* Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 7, Objective 2.3
* Nutanix Database Management & Automation (NDMA) course, Module 2, Lesson 2.3 - NDB High Availability
NEW QUESTION # 47
Refer to the exhibit.
A request is received to provision a new Oracle SIHA DB & VM to test ASMLIB on OEL79 and Oracle 19c.
When walking through the provisioning workflow, only ASMFD is available in the ASM Driver drop down.
What is necessary to provision the requested SIHA DB and DB VM with ASMLIB?
- A. Install ASMLIB on the database server.
- B. Update the NDB driver config to enable ASMLIB for Oracle.
- C. Update the software profile to include the ASMLIB driver.
- D. Install ASMLIB on the NDB server.
Answer: C
Explanation:
In the context of Nutanix Database Automation (NCP-DB), when provisioning a new Oracle SIHA DB & VM, if only ASMFD is available in the ASM Driver drop-down, it indicates that ASMLIB is not included in the current software profile. To provision the requested SIHA DB and DB VM with ASMLIB, it's essential to update the software profile to include the ASMLIB driver. This action will enable ASMLIB as an option in the ASM Driver drop-down during the provisioning workflow.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 2.3: Provisioning Oracle Databases
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.3: Provision Oracle Databases
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.3: Provisioning Oracle Databases
* [Nutanix Database Automation (NCP-DB) User Guide], Section 2.3: Provision Oracle Databases
NEW QUESTION # 48
An administrator needs to provide the least-privilege access to a newly-hired engineer whose task is to add new VLANs or IP Pools in NDB.
Which role should the administrator select to complete this task?
- A. Database Infrastructure Administrator
- B. Database Administrator
- C. Infrastructure Administrator
- D. Super Administrator
Answer: C
Explanation:
An Infrastructure Administrator is a role in NDB that has the permission to manage network and storage resources, such as VLANs, IP Pools, and Storage Containers. This role is suitable for the engineer who needs to add new VLANs or IP Pools in NDB. The other roles have either more or less privileges than required for this task. A Database Administrator can manage databases and database server VMs, but not network and storage resources. A Super Administrator can manage all aspects of NDB, but this is more than the least-privilege access needed. A Database Infrastructure Administrator can manage both databases and network and storage resources, but this is also more than the least-privilege access needed.
References: Nutanix Support & Insights, section "NDB Roles and Permissions"
NEW QUESTION # 49
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 Super Admin account.
- B. Only users in the domain admins group can create local users.
- C. An email address is required for the Super Admin account.
- D. The administrator is logged in with the Database Admin account.
Answer: D
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 # 50
Which disk is omitted from a Software Profile?
- A. System Database
- B. System Page File
- C. SQL Installation
- D. User Database
Answer: B
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 # 51
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. Update the Removal schedule to the desired date.
- B. Update the Removal schedule to the end of the month.
- C. Remove the Removal schedule, then add the desired removal schedule.
- D. Select Update and modify the Removal schedule.
Answer: D
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 # 52
An administrator needs to patch a PostgreSQL database server VM from version 13.4 to 13.8.
What is the first step within the NDB patching workflow to accomplish this task?
- A. Create a new Software Profile with PostgreSQL 13.8.
- B. Create a maintenance window and add this PostgreSQL server 13.8 to the queue.
- C. Create a new Database Parameters profile for PostgreSQL server 13.8.
- D. Create a Software Profile Version with PostgreSQL 13.8.
Answer: D
Explanation:
NDB supports patching for PostgreSQL database instances. Patching for PostgreSQL is validated on VMs provisioned by NDB (greenfield deployments). To patch PostgreSQL database server VMs, you must create a software profile version by uploading the PostgreSQL update file in NDB. You can then use the PostgreSQL update to patch other database server VMs or provision a new database server VM with the updated software profile. The first step in the NDB patching workflow is to create a software profile version with the desired PostgreSQL version.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 4.1: NDB Patching Overview
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.1: Perform Database Patching
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.1: NDB Patching Overview
* Nutanix Database Automation (NCP-DB) User Guide, Section 4.4: Patch PostgreSQL Database Software
NEW QUESTION # 53
......
Latest Nutanix NCP-DB Dumps with Test Engine and PDF (New Questions): https://www.passleader.top/Nutanix/NCP-DB-exam-braindumps.html
Pass Your NCP-DB Exam Easily - Real NCP-DB Practice Dump Updated: https://drive.google.com/open?id=1BkxSz-ngsorM4ics08KEu3RNwFz5fd0l