2025 Easy Success Nutanix NCP-DB Exam in First Try
Best NCP-DB Exam Dumps for the Preparation of Latest Exam Questions
Nutanix NCP-DB Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
NEW QUESTION # 79
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. The administrator is logged in with the Database Admin account.
- C. Only users in the domain admins group can create local users.
- 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 # 80
What is the maximum number of days allowed for alert retention?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: A
Explanation:
In Nutanix Database Service (NDB), alert retention is a configurable setting that determines how long alerts (e.g., system issues, performance warnings, or database events) are stored in the system for review and analysis. Based on NDB's design and administrative policies, the maximum number of days allowed for alert retention is 180 days. This duration allows administrators to maintain a reasonable historical view of system health while preventing excessive data accumulation that could impact performance. This value is typically set as a default maximum in the NDB settings or via Prism Central integration, and administrators can adjust retention periods within this limit based on organizational needs.
* Option A (90) is incorrect as it represents a shorter retention period, which may be a configurable minimum or intermediate value but not the maximum.
* Option B (180) is correct as it matches the documented maximum alert retention period in NDB.
* Option C (270) is incorrect as it exceeds the standard maximum retention period supported by NDB.
* Option D (306) is incorrect as it is not a supported retention limit in NDB's configuration options.
Administrators should verify this setting in the NDB UI under alert management or consult Nutanix support for custom configurations.
References
* Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Configuring Alert Settings
* Nutanix Support & Insights, Technical Note: "Alert Retention and Management in NDB"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 6: Administer an NDB Environment
NEW QUESTION # 81
It becomes necessary to remove an existing database clone. "To minimize the impact of that removal to users, an administrator would like to schedule this operation for weekend hours.
When scheduling this removal, other than the specified date/time, which option in the Update Removal Schedule is pre-selected as non-optional?
- A. Create an alert before removal.
- B. Unregister the database clone from NDB.
- C. Delete supporting snapshot from NDB.
- D. Delete the database clone from the VM.
Answer: C
Explanation:
When an administrator schedules the removal of an existing database clone to minimize user impact (e.g., during weekend hours), the "Update Removal Schedule" feature in NDB allows for planning the operation.
Among the options, the "Delete supporting snapshot from NDB" is pre-selected as a non-optional action. This ensures that the snapshot data associated with the clone is removed along with the clone itself, maintaining storage efficiency and consistency in the Time Machine framework. Other options may be selectable but are not mandatory by default.
* Option A (Create an alert before removal) is incorrect because alerts are optional notifications, not a required action.
* Option B (Delete supporting snapshot from NDB) is correct as it is a default, non-optional step to clean up snapshot data.
* Option C (Unregister the database clone from NDB) is incorrect because unregistration is an optional administrative step, not pre-selected.
* Option D (Delete the database clone from the VM) is incorrect because the clone deletion itself is the primary action, but snapshot deletion is the non-optional supporting task.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Clone Removal
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
NEW QUESTION # 82
An administrator has been asked to add a new Nutanix AHV cluster to the current single default container for DB provisioning.
Which configuration should be performed before enabling NDB multi-cluster?
- A. Add both clusters under Prism Central management and verify NDB is registered to the same Prism Central Instance. environment using a storage container as the
- B. Enable High Availability for NDB service on the Administration page.
- C. Configure datastore mapping within Prism Element Protection Domains.
- D. Deploy Nutanix Self Service VM and use blueprints to allow NDB to deploy databases on multiple clusters.
Answer: A
Explanation:
To add a new Nutanix AHV cluster to the current single default container for database provisioning and enable NDB multi-cluster functionality, the administrator must ensure a unified management framework.
Nutanix Prism Central serves as the centralized management platform for multi-cluster environments, allowing NDB to manage multiple clusters (in this case, the existing cluster and the new AHV cluster) under a single instance. Before enabling multi-cluster support in NDB, both clusters must be registered with the same Prism Central instance, and NDB must be confirmed as registered to that instance. This ensures consistent policy enforcement, resource visibility, and database provisioning across clusters using the default container.
* Option A (Deploy Nutanix Self Service VM and use blueprints) is incorrect because Nutanix Self Service is an optional tool for end-user provisioning and not a prerequisite for multi-cluster enablement.
* Option B (Configure datastore mapping within Prism Element Protection Domains) is incorrect because datastore mapping is a lower-level configuration and not directly required for multi-cluster setup in NDB.
* Option C (Enable High Availability for NDB service on the Administration page) is incorrect because HA is a separate configuration for NDB resilience, not a prerequisite for multi-cluster support.
* Option D is correct as it aligns with NDB's requirement for Prism Central integration to manage multiple clusters effectively.
This configuration ensures seamless multi-cluster operation.
References
* Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section:
Multi-Cluster Configuration
* Nutanix Prism Central Administration Guide, Section: Managing Multiple Clusters
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment
NEW QUESTION # 83
A NDB non-administrative user wants to provision an Oracle database leveraging a Software Profile that the administrator created. What must the administrator do to ensure that this user has access to the Oracle Software Profile?
- A. Replicate the Software Profile to other Nutanix clusters for all users to access.
- B. Promote the Software Profile to Published to be available by other NDB users.
- C. Ensure that specified users have access to the Software Profile using Access Control.
- D. Ensure that the Software Profile has been properly versioned to the latest release of Oracle.
Answer: B
Explanation:
To allow a non-administrative NDB user to provision an Oracle database using a Software Profile created by an administrator, the administrator must promote the Software Profile to Published. In NDB, Software Profiles define the database software version and configuration (e.g., Oracle binaries). By default, a newly created profile is in a draft or private state. Promoting it to "Published" makes it available for use by other NDB users, including non-administrative ones, within the access control framework. This ensures the profile is validated and accessible without requiring individual user assignments.
Other options are incorrect:
* A. Ensure that specified users have access to the Software Profile using Access Control: Access Control manages user permissions but does not make the profile available unless it is published.
* B. Replicate the Software Profile to other Nutanix clusters: Replication is for HA or disaster recovery, not user access.
* C. Ensure that the Software Profile has been properly versioned to the latest release of Oracle:
Versioning ensures compatibility but does not grant user access.
Thus, the verified answer is D, aligning with NDB's profile management workflow.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Managing Software Profiles.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
3: Manage NDB Solutions, Objective 3.1: Configure Software Profiles (applicable to v6.10).
* Nutanix NDB Administration Guide: "Publishing Software Profiles" section.
NEW QUESTION # 84
How can an administrator exclude Kernel patches for the Linux OS using the most efficient means?
- A. Define a pre-script to disable the repositories in the Maintenance Window advanced options.
- B. Exclude the appropriate repositories on the VM and reboot prior to patching.
- C. Define a pre-script to disable the repositories inthe Patch Now advanced options
- D. Exclude the appropriate repositories on the VM prior to patching.
Answer: D
Explanation:
NDB supports Linux OS patching for database server VMs. Linux OS patching is performed by using the yum or apt package managers, depending on the Linux distribution. To exclude Kernel patches for the Linux OS, the administrator can disable or exclude the appropriate repositories on the VM prior to patching. This can be done by editing the yum.conf or apt.conf files, or by using the --disablerepo or --exclude options in the yum or apt commands. This way, the administrator can control which patches are applied to the VM without affecting other VMs or requiring additional scripts or reboots.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 4.2: NDB Linux OS Patching
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.2: Perform Linux OS Patching
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.2: NDB Linux OS Patching
* Nutanix Database Automation (NCP-DB) User Guide, Section 4.5: Patch Linux OS Software
NEW QUESTION # 85
Which two processes should an administrator take to create a software profile version for a newly-released Oracle ISc patch? (Choose two.)
- A. 1. Create new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era Gul.
2. Mark the original patch profile as hidden. - B. 1. Download the required patch from Microsoft Support.
2. Apply the patch to the Oracle Home/Grid Home on e cloned VM of the gold image using OPatchAuto utiliv.
3. Ensure success of patch application. - C. 1. Download the required patch from MyOracle Support
2. Apply the patch to the Oracle Home Grid Home on a cloned VM of the gold image using O PatchAuto
3. Ensure success of patch application - D. 1. Create new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era Gul.
2. Mark the original patch profile as deprecated.
Answer: A,C
Explanation:
To create a software profile version for a newly-released Oracle ISc patch, an administrator should follow these steps:
* Download the required patch from MyOracle Support1. This is because Oracle patches are typically available from MyOracle Support, not Microsoft Support.
* Apply the patch to the Oracle Home/Grid Home on a cloned VM of the gold image using OPatchAuto1.
OPatchAuto is a utility provided by Oracle that automates the process of applying patches to a database.
* Ensure success of patch application1. It's important to verify that the patch has been applied successfully to avoid any issues down the line.
* Create a new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era GUI1. This step is necessary to ensure that the new patch is included in the software profile.
* Mark the original patch profile as hidden1. This step is optional but can be useful for keeping the software profile clean and organized.
Please note that these answers are based on the information available as of my last update in 2021 and may need to be verified with the most recent Nutanix Database Automation (NCP-DB) documentation or resources.
NEW QUESTION # 86
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 # 87
An administrator has created a new SQL Server software profile version to apply the latest cumulative update.
What should the administrator do to make it available to all users?
- A. Deprecate the existing software profile version and use the new one.
- B. Update the software profile version and set the status to Published.
- C. Set the status of the existing software profile version to Unpublished.
- D. Select the software profile version with the update and optimization,
Answer: B
Explanation:
When an administrator creates a new SQL Server software profile version to apply the latest cumulative update, they should update the software profile version and set the status to Published1. This makes the new profile version available to all users. NDB will show available updates for any database server using the software profile as soon as the new profile version is published1.
NEW QUESTION # 88
What behavior is observed when applying patch profiles as a Super Admin?
- A. Hidden patches can be applied.
- B. Deprecated patches can be applied.
- C. Published patches cannot be applied if currently deprecated.
- D. Unpublished patches can be applied.
Answer: C
Explanation:
In the context of Nutanix Database Automation (NCP-DB), a Super Admin has the authority to apply patch profiles. However, if a patch is marked as deprecated, even if it's published, it cannot be applied. This is because deprecation is a status that indicates the patch is outdated or has been superseded by a newer version, and thus should not be used1. This behavior ensures that only the most up-to-date and secure patches are applied to the system, maintaining the integrity and security of the database environment1.
NEW QUESTION # 89
An administrator needs to add a stretched VLAN across two clusters in NDB Which two prerequisites should be met prior to completing this action? (Choose two.)
- A. VLAN must be IPAM.
- B. Nutanix Cluster Management must be enabled.
- C. VLAN must be static.
- D. Both clusters must be registered in NDB.
Answer: C,D
Explanation:
A stretched VLAN is a virtual network that spans across multiple Nutanix clusters and allows the communication between VMs on different clusters using the same subnet. A stretched VLAN can be used to provide high availability and load balancing for NDB components, such as HAProxy VMs, that require a virtual IP address (VIP) to be accessible from any cluster. To add a stretched VLAN across two clusters in NDB, the administrator needs to meet two prerequisites: the VLAN must be static and both clusters must be registered in NDB. A static VLAN is a VLAN that is manually created and configured by the administrator, as opposed to an IPAM VLAN that is automatically created and managed by NDB. A static VLAN can be added to a stretched VLAN in NDB, while an IPAM VLAN cannot. Both clusters must be registered in NDB before adding a stretched VLAN, as NDB needs to have the information and access to the clusters and their networks. The administrator can register the clusters in NDB using the Prism Element details, agent network configuration, and storage container information. The other option, Nutanix Cluster Management, is not a prerequisite for adding a stretched VLAN in NDB. Nutanix Cluster Management is a feature that allows the administrator to manage multiple Nutanix clusters from a single NDB UI, such as creating or deleting clusters, adding or removing nodes, or performing cluster operations. Nutanix Cluster Management is not required for adding a stretched VLAN, as the VLANs are created and configured in Prism Element, not in NDB. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.3: Configure NDB High Availability
* Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.3: Configuring NDB High Availability, Topic: NDB HA Architecture and Components
* Nutanix Database Service High Availability Deployment Overview, Section: HAProxy VMs and Stretched VLANs
* [Configuring a Virtual NIC to Operate in Access or Trunk Mode - Nutanix], Section: Creating a vNIC in Access or Trunk Mode
NEW QUESTION # 90
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 BRASS SLA
- C. DEFAULT_008 BRONZE SLA
- D. DEFAULT_008 SILVER SLA
Answer: D
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 # 91
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 3, Max 5
- B. Min 2, Max 6
- C. Min 1. Max 3
- 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 the PostgreSQL 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 # 92
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. Software
- C. Database Parameter
- D. Windows Domain
Answer: D
NEW QUESTION # 93
What step should be taken to make the profile available to all users:
- A. Update the profile and set the status to Published.
- B. Update the profile and set available state to All.
- C. Create an Access Control group with the desired users and grant it the Database Admin role.
- D. Create an Access Control role with the Create Profile right and assign to all users.
Answer: B
Explanation:
The correct answer is D because it allows the administrator to make the profile available to all users without requiring any additional permissions or roles. A profile is a collection of settings that define how NDB manages a database server or a database. By default, a profile is only available to the user who created it and the Database Admin role. To make a profile available to all users, the administrator can update the profile and set the available state to All. This will enable all users to view and use the profile for their database operations.
The other options are not correct because they either require additional steps or do not achieve the desired outcome. Option A is not correct because creating an Access Control role with the Create Profile right and assigning it to all users will only allow them to create their own profiles, not use the existing one. Option B is not correct because creating an Access Control group with the desired users and granting it the Database Admin role will only make the profile available to those users, not all users. Option C is not correct because updating the profile and setting the status to Published will not change the availability of the profile, only the state of the profile. A published profile is a profile that has been tested and verified by the administrator and is ready for use. Adraft profile is a profile that is still under development or testing and is not ready for use. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Certified Professional - Database Automation (NCP-DB) datasheet
NEW QUESTION # 94
In order to configure and begin taking advantage of the Data Access Management feature of Time Machine, which action should an administrator take first?
- A. Enable NDB HA to protect the metadata associated with the configuration.
- B. Enable NDB multi-cluster and register required Nutanix cluster(s).
- C. Ensure that the source database has been provisioned on the remote Nutanix cluster.
- D. Take an application consistent snapshot of the source database.
Answer: B
Explanation:
To configure and begin taking advantage of the Data Access Management feature of Time Machine, the administrator must first enable NDB multi-cluster and register the required Nutanix cluster(s). Data Access Management allows controlled access to data (e.g., snapshots, clones) across multiple clusters, requiring a multi-cluster setup. This involves enabling multi-cluster support in NDB and registering remote clusters to facilitate data replication and access policies.
Other actions are prerequisites or subsequent steps:
* A. Enable NDB HA to protect the metadata associated with the configuration: HA is beneficial but not the first step for Data Access Management.
* C. Take an application consistent snapshot of the source database: This is a later step after multi- cluster setup.
* D. Ensure that the source database has been provisioned on the remote Nutanix cluster:
Provisioning follows multi-cluster registration.
Thus, the verified answer is B, establishing the multi-cluster foundation.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.3: Configuring Data Access Management.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
5: Protect Databases Using NDB, Objective 5.3: Configure Data Access (applicable to v6.10).
* Nutanix NDB Administration Guide: "Data Access Management Setup" section.
NEW QUESTION # 95
What two reference resources are available for Nutanix Era APIs? (Choose two.)
- A. Nutanix.dev API Reference
- B. Era GitHub API Repository
- C. Era API Explorer
- D. Nutanix Support Portal
Answer: A,C
Explanation:
The Nutanix Era API documentation is available on the Nutanix.dev API Reference page12. This documentation outlines the operations that are possible with the Era APIs2. In addition to the API reference, the NutanixDev code samples repo provides working code that implements the practices shown in the documentation1. The Era API Explorer is another resource that provides a comprehensive view of the available APIs, allowing users to interactively explore and test the APIs. However, there is no mention of a specific "Era GitHub API Repository" or the "Nutanix Support Portal" being used as a reference resource for Nutanix Era APIs in the provided resources. Therefore, the correct answers are B. Nutanix.dev API Reference and C. Era API Explorer.
NEW QUESTION # 96
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. Microsoft SQL
- B. MySQL
- C. Oracle
- D. PostgreSQL
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 # 97
When provisioning a new database, which two options are available for the target? (Choose two.)
- A. Provision database to a new database sender\cluster.
- B. Provision database to an existing registered
- C. Provision databases to e new container.
- D. Provision database to an existing container.
Answer: B,C
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, when provisioning a new database, there are two options available for the target12:
* Provision database to an existing registered: This option allows you to provision a database to an existing registered database server. This is useful when you want to add a database to a server that is already being managed by Nutanix Era1.
* Provision databases to a new container: This option allows you to provision a database to a new container. This is useful when you want to create a new isolated environment for your database1.
NEW QUESTION # 98
When running the Linux prerequisites script, an administrator discovers that the only required argument is -t.
What does the -t argument specify?
- A. NDB server IP
- B. Timeout interval
- C. Database engine
- D. Operating System type
Answer: B
Explanation:
When running the Linux prerequisites script for NDB, the -t argument is a required parameter that specifies the timeout interval. This argument defines the maximum time (in seconds) the script will wait for certain operations (e.g., connectivity checks, package installations) to complete before timing out. This is critical during the preinstallation phase to ensure the environment is properly configured and responsive, avoiding indefinite hangs. Other options are not associated with -t:
* A. Operating System type: This is not a typical argument for the prerequisites script.
* C. NDB server IP: This would be specified separately (e.g., via -s or a similar flag).
* D. Database engine: This is irrelevant to the prerequisites script, which focuses on system setup.
Thus, the verified answer is B, aligning with the script's purpose of managing execution timeouts.
Official Nutanix Database Automation References
* Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.1: Running Prerequisites Scripts.
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section
2: Deploy and Configure an NDB Solution, Objective 2.1: Prepare Hosts (applicable to v6.10).
* Nutanix NDB Installation Guide: "Running the Linux Prerequisites Script" section, detailing -t usage.
NEW QUESTION # 99
An administrator has configured NDB HA across multiple Nutanix clusters.
Which failure scenario will require manual interaction for the recovery?
- A. One repository VM is down.
- B. NDB Server process is down.
- C. More than one HA proxy VM is down.
- D. More than one API Server VM is down.
Answer: D
Explanation:
NDB HA is a feature that provides high availability and resilience for the NDB service and its components.
NDB HA creates a cluster of API server VMs, repository VMs, and HAProxy VMs across multiple Nutanix clusters. Each component has a leader and a set of followers that are synchronized and can take over the leader role in case of a failure. NDB HA also monitors the health and status of the NDB components and performs automatic failover and recovery actions when possible. However, some failure scenarios may require manual intervention from the administrator to restore the NDB service. One such scenario is when more than one API server VM is down. The API server VMs are responsible for handling the requests from the NDB UI and CLI, as well as communicating with the repository VMs and the HAProxy VMs. If more than one API server VM is down, the NDB service may become unavailable or unstable, and the administrator will need to manually restart or redeploy the affected API server VMs. The other options do not require manual interaction for the recovery, as NDB HA can handle them automatically. If one repository VM is down, NDB HA will fail over to another repository VM that has the latest data. If more than one HAProxy VM is down, NDB HA will route the traffic to the remaining HAProxy VMs. If the NDB server process is down, NDB HA will restart the process or fail over to another API server VM. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.3: Configure NDB High Availability
* Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.3: Configuring NDB High Availability, Topic: NDB HA Architecture and Components
* Nutanix Support & Insights, RA-2035: Nutanix Database Service High Availability, Section: NDB HA Failure Scenarios and Recovery Actions
NEW QUESTION # 100
......
NCP-DB Study Material, Preparation Guide and PDF Download: https://www.itpassleader.com/Nutanix/NCP-DB-dumps-pass-exam.html
NCP-DB Actual Questions 100% Same Braindumps with Actual Exam: https://drive.google.com/open?id=1AItC7CnB5P8EBY7cl6MU0llXjIYBwGzz