Practice Free NCP-DB-6.5 Exam Online Questions
Question #11
What must be configured in Prism Element to allow the NDB server and CVMs to facilitate iSCSI connections?
- A . Virtual IP
- B . Data Services IP
- C . Secondary DNS IP
- D . Backplane IP
Correct Answer: B
B
Explanation:
To enable iSCSI connections between the Nutanix Database Service (NDB) server, Controller VMs (CVMs), and Prism Element, a Data Services IP must be configured in Prism Element. The Data Services IP acts as a cluster-wide address that facilitates iSCSI target discovery and connectivity. It is used by Nutanix Volumes (a block storage service) to present storage to external clients or services, such as the NDB server, via the iSCSI protocol. This IP ensures that iSCSI traffic is routed correctly and remains available even if a CVM fails, as ownership of the Data Services IP can move to another CVM in the cluster.
Configuring the Data Services IP is a prerequisite for integrating NDB with a Nutanix cluster, as NDB relies on iSCSI to manage database storage operations like provisioning and cloning. Without this configuration, the NDB server cannot establish the necessary connections to the CVMs for database-related tasks. Options like Virtual IP, Secondary DNS IP, and Backplane IP are not relevant in this context:
Virtual IP: This is typically associated with high-availability setups for applications, not iSCSI connectivity.
Secondary DNS IP: This pertains to network resolution, not storage connectivity.
Backplane IP: This is an internal network IP for cluster communication, not for external iSCSI access.
Thus, the correct and verified answer is the Data Services IP.
Official Nutanix Database Automation
Reference: Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring
an NDB Solution, Lesson 2.2: Configuring NDB Prerequisites.
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution (applicable to v6.10 as foundational concepts remain consistent).
Nutanix Support & Insights Portal: "Configuring iSCSI Data Services IP for Nutanix Volumes" (general Volumes configuration applicable to NDB).
B
Explanation:
To enable iSCSI connections between the Nutanix Database Service (NDB) server, Controller VMs (CVMs), and Prism Element, a Data Services IP must be configured in Prism Element. The Data Services IP acts as a cluster-wide address that facilitates iSCSI target discovery and connectivity. It is used by Nutanix Volumes (a block storage service) to present storage to external clients or services, such as the NDB server, via the iSCSI protocol. This IP ensures that iSCSI traffic is routed correctly and remains available even if a CVM fails, as ownership of the Data Services IP can move to another CVM in the cluster.
Configuring the Data Services IP is a prerequisite for integrating NDB with a Nutanix cluster, as NDB relies on iSCSI to manage database storage operations like provisioning and cloning. Without this configuration, the NDB server cannot establish the necessary connections to the CVMs for database-related tasks. Options like Virtual IP, Secondary DNS IP, and Backplane IP are not relevant in this context:
Virtual IP: This is typically associated with high-availability setups for applications, not iSCSI connectivity.
Secondary DNS IP: This pertains to network resolution, not storage connectivity.
Backplane IP: This is an internal network IP for cluster communication, not for external iSCSI access.
Thus, the correct and verified answer is the Data Services IP.
Official Nutanix Database Automation
Reference: Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring
an NDB Solution, Lesson 2.2: Configuring NDB Prerequisites.
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution (applicable to v6.10 as foundational concepts remain consistent).
Nutanix Support & Insights Portal: "Configuring iSCSI Data Services IP for Nutanix Volumes" (general Volumes configuration applicable to NDB).
Question #12
An NDB environment has been deployed with three Nutanix clusters. An administrator has been asked to create a Microsoft SQL Server software profile for each of these clusters.
Which is a requirement to create the above-mentioned profiles?
- A . Compute profile must be created first on every cluster.
- B . Enable Multi-cluster capabilities for NDB.
- C . Enable High Availability for the current NDB Service.
- D . Each cluster must host a VM with the DB engine.
Correct Answer: D
D
Explanation:
To create a Microsoft SQL Server software profile for each of the three Nutanix clusters in an NDB environment, a key requirement is that each cluster must host at least one VM with the Microsoft SQL Server database engine installed. NDB uses these VMs to discover, validate, and generate software profiles tailored to the specific SQL Server versions and configurations present on each cluster. This ensures that the profiles are compatible with the cluster’s environment and can be used for provisioning or patching.
Option A (Compute profile must be created first on every cluster) is incorrect because compute profiles are optional and not a prerequisite for creating software profiles.
Option B (Enable Multi-cluster capabilities for NDB) is incorrect as multi-cluster support is already implied by the deployment across three clusters, but it’s not a specific requirement for profile creation.
Option C (Enable High Availability for the current NDB Service) is incorrect because HA is a separate configuration and not required to create software profiles.
Option D (Each cluster must host a VM with the DB engine) is correct as it aligns with NDB’s requirement to have a
Reference: VM for profile generation.
This setup ensures accurate and cluster-specific software profile creation.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section:
Creating Software Profiles
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles
D
Explanation:
To create a Microsoft SQL Server software profile for each of the three Nutanix clusters in an NDB environment, a key requirement is that each cluster must host at least one VM with the Microsoft SQL Server database engine installed. NDB uses these VMs to discover, validate, and generate software profiles tailored to the specific SQL Server versions and configurations present on each cluster. This ensures that the profiles are compatible with the cluster’s environment and can be used for provisioning or patching.
Option A (Compute profile must be created first on every cluster) is incorrect because compute profiles are optional and not a prerequisite for creating software profiles.
Option B (Enable Multi-cluster capabilities for NDB) is incorrect as multi-cluster support is already implied by the deployment across three clusters, but it’s not a specific requirement for profile creation.
Option C (Enable High Availability for the current NDB Service) is incorrect because HA is a separate configuration and not required to create software profiles.
Option D (Each cluster must host a VM with the DB engine) is correct as it aligns with NDB’s requirement to have a
Reference: VM for profile generation.
This setup ensures accurate and cluster-specific software profile creation.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section:
Creating Software Profiles
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles
Question #13
What is the maximum number of days allowed for alert retention?
- A . 90
- B . 180
- C . 270
- D . 306
Correct Answer: B
B
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.
Reference: 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
B
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.
Reference: 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
Question #14
Which statement describes a user in Era with the Database Infrastructure Admin role?
- A . The user is able to manage software profiles, Network Profiles. database Instance parameter profiles and time machine SLA
- B . The user is able to manage software profiles, Network Profiles. database parameter profiles end Time Machine SLAs,
- C . The user is able to manage database profiles, Network Profiles, database Instance parameter profiles and time machine SLA
- D . The user is able to manage software profiles, database parameter profiles and SLAs
Correct Answer: B
B
Explanation:
The size of a database Time Machine in Nutanix Era is defined by the size of all snapshots and/or transaction logs maintained by Era1. The Time Machine leverages Nutanix’s efficient snapshot technology to capture the state of the database at different points in time1. These snapshots, along with transaction logs that record changes between snapshots, constitute the data maintained by the Time Machine1. Therefore, the size of the Time Machine is determined by the total size of these snapshots and transaction logs1.
B
Explanation:
The size of a database Time Machine in Nutanix Era is defined by the size of all snapshots and/or transaction logs maintained by Era1. The Time Machine leverages Nutanix’s efficient snapshot technology to capture the state of the database at different points in time1. These snapshots, along with transaction logs that record changes between snapshots, constitute the data maintained by the Time Machine1. Therefore, the size of the Time Machine is determined by the total size of these snapshots and transaction logs1.
Question #15
What does an NDB compute profile contain?
- A . vCPUs, cores per vCPU, and the amount of memory for the database server VM.
- B . Windows domain name (FQDN), domain user, and password.
- C . VLAN that the new database server VM will use.
- D . An image of the database and operating system generated from the registered database server VM.
Correct Answer: A
A
Explanation:
An NDB compute profile defines the CPU and memory resources for the database server VMs that are provisioned using NDB. It does not include any information about the network, domain, or software of the database server VMs. Those are specified in separate profiles, such as network profile, domain profile, and software profile.
Reference: Nutanix Support & Insights, section “NDB Compute”
A
Explanation:
An NDB compute profile defines the CPU and memory resources for the database server VMs that are provisioned using NDB. It does not include any information about the network, domain, or software of the database server VMs. Those are specified in separate profiles, such as network profile, domain profile, and software profile.
Reference: Nutanix Support & Insights, section “NDB Compute”
Question #15
What does an NDB compute profile contain?
- A . vCPUs, cores per vCPU, and the amount of memory for the database server VM.
- B . Windows domain name (FQDN), domain user, and password.
- C . VLAN that the new database server VM will use.
- D . An image of the database and operating system generated from the registered database server VM.
Correct Answer: A
A
Explanation:
An NDB compute profile defines the CPU and memory resources for the database server VMs that are provisioned using NDB. It does not include any information about the network, domain, or software of the database server VMs. Those are specified in separate profiles, such as network profile, domain profile, and software profile.
Reference: Nutanix Support & Insights, section “NDB Compute”
A
Explanation:
An NDB compute profile defines the CPU and memory resources for the database server VMs that are provisioned using NDB. It does not include any information about the network, domain, or software of the database server VMs. Those are specified in separate profiles, such as network profile, domain profile, and software profile.
Reference: Nutanix Support & Insights, section “NDB Compute”
Question #17
An administrator is trying to register a Nutanix cluster for Multi-Cluster provisioning.
The Era cluster is setup with following configuration:
• Era Multi-Cluster is enabled.
Era Server storage container and Era provisioning container are different on the Era cluster.
What should the administrator configure?
- A . Storage mapping between Era server container end remote container thet is used for provisioning DBs,
- B . Disks that span across Era Server storage container and Era provisioning container.
- C . Storage mapping between Era container and a remote container that is not used for provisioning databases.
- D . Separate remote containers for provisioning Era Agent VM end database Server VMs.
Correct Answer: A
A
Explanation:
In a Nutanix Era setup where Multi-Cluster is enabled and the Era Server storage container and Era provisioning container are different on the Era cluster, the administrator should configure a storage mapping between the Era server container and the remote container that is used for provisioning databases1. This is because Nutanix Era uses the storage container specified during the registration of the Nutanix cluster for provisioning databases1. Therefore, a storage mapping needs to be established between the Era server container and the remote container used for provisioning to ensure that the databases are provisioned correctly1.
A
Explanation:
In a Nutanix Era setup where Multi-Cluster is enabled and the Era Server storage container and Era provisioning container are different on the Era cluster, the administrator should configure a storage mapping between the Era server container and the remote container that is used for provisioning databases1. This is because Nutanix Era uses the storage container specified during the registration of the Nutanix cluster for provisioning databases1. Therefore, a storage mapping needs to be established between the Era server container and the remote container used for provisioning to ensure that the databases are provisioned correctly1.
Question #18
An administrator is initially setting up Time Machine for a newly-provisioned database.
What is the maximum number of snapshots per day that can be configured in the GUI?
- A . 4
- B . 6
- C . 8
- D . 12
Correct Answer: B
B
Explanation:
When setting up a Time Machine for a newly-provisioned database in NDB, the GUI allows the administrator to configure the frequency of snapshots for data protection. The maximum number of snapshots per day that can be configured in the NDB GUI is 6. This limit ensures a balance between data granularity (for point-in-time recovery) and storage overhead, preventing excessive resource consumption. The administrator can schedule these snapshots at regular intervals (e.g., every 4 hours) within the Time Machine configuration wizard.
Other options are incorrect based on NDB’s design:
B
Explanation:
When setting up a Time Machine for a newly-provisioned database in NDB, the GUI allows the administrator to configure the frequency of snapshots for data protection. The maximum number of snapshots per day that can be configured in the NDB GUI is 6. This limit ensures a balance between data granularity (for point-in-time recovery) and storage overhead, preventing excessive resource consumption. The administrator can schedule these snapshots at regular intervals (e.g., every 4 hours) within the Time Machine configuration wizard.
Other options are incorrect based on NDB’s design:
Question #19
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.
Correct Answer: D
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.
Reference:
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
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.
Reference:
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
Question #20
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 . Deploy Nutanix Self Service VM and use blueprints to allow NDB to deploy databases on multiple clusters.
- B . Configure datastore mapping within Prism Element Protection Domains.
- C . Enable High Availability for NDB service on the Administration page.
- D . 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
Correct Answer: D
D
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.
Reference: 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
D
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.
Reference: 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