Apr 18, 2024 Detailed New NCP-DB Exam Questions for Concept Clearance
NCP-DB Exam Preparation Material with New NCP-DB Dumps Questions.
NEW QUESTION # 31
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 software profile to include the ASMLIB driver.
- C. Update the NDB driver config to enable ASMLIB for Oracle.
- D. Install ASMLIB on the NDB server.
Answer: B
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 # 32
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 maintenance window and add this PostgreSQL server 13.8 to the queue.
- B. Create a new Software Profile with PostgreSQL 13.8.
- C. Create a Software Profile Version with PostgreSQL 13.8.
- D. Create a new Database Parameters profile for PostgreSQL server 13.8.
Answer: C
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 # 33
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. Only users in the domain admins group can create local users.
- B. The administrator is logged in with the Database Admin account.
- C. The administrator is logged in with the Super Admin account.
- D. An email address is required for the Super Admin account.
Answer: B
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 # 34
The NDB user interface can display which language option?
- A. Japanese
- B. German
- C. French
- D. Korean
Answer: A
Explanation:
The NDB user interface supports multiple languages, including English, Chinese, and Japanese. You can change the language preference in the NDB settings page. The NDB user interface does not support Korean, French, or German languages at this time. References:
* Nutanix Database Management & Automation Training Course, Module 1: Introduction to Nutanix Era, Lesson 1: Nutanix Era Overview, Slide 7: NDB User Interface
* Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 1: Describe NDB Concepts, Objective 1.6: Languages
NEW QUESTION # 35
An administrator needs to maintain five days of time-travel capability to any second, plus an additional seven days of discrete recovery at a daily interval.
How should the administrator define the Frequency and retention on the SLA?
- A. * Daily snapshot retention (days): 7
* Continuous log retention (days): 5 - B. * Weekly snapshot retention (weeks): 1
* Continuous log retention (days): 7 - C. * Continuous log retention (days): 7
* Daily snapshot retention (days): 5 - D. * Continuous log retention (days): 5
* Weekly snapshot retention (weeks): 1
Answer: A
Explanation:
The correct answer is D because it meets the requirements of maintaining five days of time-travel capability to any second and an additional seven days of discrete recovery at a daily interval. Continuous log retention allows the administrator to restore the database to any point in time within the specified number of days, while snapshot retention allows the administrator to restore the database to a specific point in time at a fixed interval.
Therefore, by setting the daily snapshot retention to 7 days, the administrator can ensure that there is a discrete recovery point for each day of the week. By setting the continuous log retention to 5 days, the administrator can ensure that there is a time-travel capability to any second within the last five days. The other options do not meet the requirements because they either have less than five days of continuous log retention or less than seven days of snapshot retention. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Certified Professional - Database Automation (NCP-DB) datasheet
NEW QUESTION # 36
An administrator needs to distribute NDB management plane components.
Which NDB HA VM needs to be deployed on the same L2 network?
- A. HA Proxy VMs
- B. NDB Agent
- C. API Server
- D. Repository VMs
Answer: A
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 # 37
Which two encryption methods can be used when configuring an SMTP server? (Choose two.)
- A. TLS
- B. SSL
- C. S/MIME
- D. IPsec
Answer: A,B
Explanation:
NDB supports SMTP server configuration for sending email notifications and alerts. SMTP server configuration requires specifying the SMTP server address, port, username, password, and encryption method.
The encryption method determines how the email messages are secured during transmission. NDB supports two encryption methods for SMTP server configuration: TLS and SSL.
TLS (Transport Layer Security) is a protocol that encrypts and authenticates data between the email client and the SMTP server. TLS can operate in two modes: explicit and implicit. In explicit mode, the email client and the SMTP server negotiate the encryption method and parameters after establishing a plain text connection.
This mode typically uses port 587. In implicit mode, the email client and the SMTP server assume that the connection is encrypted from the start, without any negotiation. This mode typically uses port 465.
SSL (Secure Sockets Layer) is a predecessor of TLS that also encrypts and authenticates data between the email client and the SMTP server. SSL operates in implicit mode only, and uses port 465 by default. SSL is less secure than TLS, but it is still widely used and supported by many email providers.
S/MIME (Secure/Multipurpose Internet Mail Extensions) is a standard that encrypts and signs email messages at the application layer, rather than the transport layer. S/MIME requires the use of digital certificates and public key cryptography to ensure the confidentiality and integrity of email messages. S/MIME is not a valid encryption method for SMTP server configuration, as it does not affect the connection between the email client and the SMTP server.
IPsec (Internet Protocol Security) is a suite of protocols that secures IP packets at the network layer, rather than the application or transport layer. IPsec can encrypt and authenticate data between any two IP endpoints, such as routers, firewalls, or hosts. IPsec is not a valid encryption method for SMTP server configuration, as it does not apply to the specific protocol or port used by SMTP.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 1.4: NDB Alerts and Notifications
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 1.4: Configure NDB Alerts and Notifications
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 1.4: NDB Alerts and Notifications
* [Nutanix Database Automation (NCP-DB) User Guide], Section 1.4: Configure SMTP Server Settings
NEW QUESTION # 38
What is causing this issue?
- A. TheVLANisDHCP
- B. The VLAN is static
- C. The VLAN is stretched
- D. The VLAN is IPAM
Answer: C
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 # 39
A request is received to refresh a database clone from a new manual snapshot. When the administrator attempts to create the new snapshot from the Time Machine, it is in a Frozen state.
What causes a Time Machine to enter the Frozen state and what are the administrator's options to complete the request?
- A. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: To complete the request the database must be re-registered in NDB, this thaws the Time Machine and it resumes operation so the clone can be refreshed. - B. Cause: The Time Machine enters a Frozen state after too many snapshot or log catchup failures.Resolution: Remediate the snapshot or log catchup failures, this thaws the Time Machine, allowing normal operations to continue and the request can be completed.
- C. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: The Time Machine must be paused, then the database re-registered with a new Time Machine and a new clone created. - D. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: To complete the request the database must be re-registered in NDB, create a new Time Machine and create a new clone.
Answer: A
Explanation:
A Time Machine is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention.When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de-registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 5 - Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies
* Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: Time Machine Concepts
* Nutanix Support & Insights, TN-2101: Nutanix Database Service Time Machine Under the Hood, Section: Time Machine States and Transitions
NEW QUESTION # 40
When provisioning an PostgreSQL HA Instance, what are the minimum and maximum number of DB server VMs that can be deployed in a cluster?
- A. Min 2, Max 6
- B. Min 1. Max 3
- C. Min 3, Max 5
- D. Min 2, Max 4
Answer: D
Explanation:
When provisioning a PostgreSQL HA Instance using NDB, the minimum and maximum number of DB server VMs that can be deployed in a cluster are 2 and 4, respectively. A PostgreSQL HA Instance is a database instance that provides high availability and fault tolerance for PostgreSQL databases using the Patroni framework. Patroni is a Python-based tool that manages PostgreSQL configuration and performs automatic failover and switchover operations. Patroni relies on a distributed consensus store, such as etcd, Consul, or ZooKeeper, to store and synchronize the cluster state and leader information. NDB supports etcd as the consensus store for PostgreSQL HA Instances. NDB allows the administrator to provision PostgreSQL HA Instances with different sizes and configurations, such as small, medium, large, or custom. The size of thePostgreSQL HA Instance determines the number of DB server VMs, the number of etcd nodes, the CPU, memory, and disk resources, and the replication factor of the database. The minimum number of DB server VMs for a PostgreSQL HA Instance is 2, which corresponds to a small size instance. This configuration provides one leader and one follower DB server VM, and one etcd node. The maximum number of DB server VMs for a PostgreSQL HA Instance is 4, which corresponds to a large size instance. This configuration provides one leader and three follower DB server VMs, and three etcd nodes. The other options are not valid for a PostgreSQL HA Instance, as they either do not provide enough redundancy or exceed the supported limit of DB server VMs. 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: Provisioning PostgreSQL HA Instances
* Nutanix Database Service (NDB) User Guide, Chapter 4: Provisioning Databases, Section: Provisioning PostgreSQL HA Instances
* [PostgreSQL High Availability: Under the Hood - Nutanix.dev], Section: PostgreSQL HA Architecture and Components
NEW QUESTION # 41
What is purpose of the NDB Database Agent service?
- A. Hosts one or more source databases for the same time machine.
- B. Schedules and monitors the NDB-related operations.
- C. Contains an instance of the database engine software.
- D. Temporarily stores the transaction logs.
Answer: B
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 # 42
While adding Time Machine data access to a Nutanix cluster, when is a storage container mapping needed
- A. When the source database and NDB provisioning container are the same.
- B. When the source database and NDB VM are on the same container.
- C. When the source database and NDB Server containers are different.
- D. When the source and destination database containers are different.
Answer: C
Explanation:
Time Machine data access is a feature of Nutanix Database Service (NDB) that allows you to access a point-in-time snapshot of a database without restoring it. To use this feature, you need to create a Data Access Management (DAM) policy that defines the access mode, the source database, the destination cluster, and the storage container mapping. The storage container mapping is needed when the source database and the NDB Server containers are different, because NDB needs to know where to store the metadata and the clone of the source database. If the source database and the NDB Server containers are the same, then NDB will use the same container for both the metadata and the clone. References:
* Nutanix Certified Professional - Database Automation (NCP-DB), Section 5 - Protect NDB-managed Databases Using Time Machine
* Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 9, Objective 5.6
* Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.2 - Data Access Management
NEW QUESTION # 43
Which statement is true regarding the NDB alert retention feature?
- A. NDB supports alert retention globally.
- B. NDB supports retention at the grouped policy.
- C. NDB supports retention at the individual policy.
- D. NDB supports retention at the registered cluster.
Answer: A
Explanation:
The NDB alert retention feature allows the database administrator to configure the duration for which the NDB alerts are stored and displayed in the NDB instance. The NDB alert retention feature supports alert retention globally, meaning that the same retention period applies to all the alerts generated by the NDB instance, regardless of the source cluster, policy, or operation. The database administrator can set the alert retention period from 1 day to 365 days, or choose to retain the alerts indefinitely. The NDB alert retention feature helps to manage the storage space and the visibility of the NDB alerts.
The NDB alert retention feature does not support retention at the individual policy, grouped policy, or registered cluster level. The NDB alert retention feature applies to all the alerts uniformly, and does not allow the database administrator to specify different retention periods for different policies or clusters.
References:
* Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment, Lesson 3.2: Nutanix Era Deployment, slide 11.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slide 6.
NEW QUESTION # 44
An administrator is tasked with auditing NDB SLAs. What data will the administrator be reviewing?
- A. Snapshot schedules
- B. Clone Management
- C. Recovery Time Objective
- D. Data retention policies
Answer: D
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
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. Update the cluster's Data Access & select the remote cluster.
- C. Add Data Access to each Nutanix cluster and assign a DAM policy.
- D. Update the SLA on the Time Machine & schedule the remote replication.
Answer: C
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 # 46
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. Remove the Removal schedule, then add the desired removal schedule.
- C. Select Update and modify the Removal schedule.
- D. Update the Removal schedule to the end of the month.
Answer: C
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 # 47
......
NCP-DB 2024 Training With 77 QA's: https://www.prep4king.com/NCP-DB-exam-prep-material.html
Nutanix NCP-DB Certification Exam Questions: https://drive.google.com/open?id=1YMCcA3e1gMArUWYqeBOWRzCFZGln6jIu
