Practice Free NCP-DB-6.5 Exam Online Questions
Question #31
Which disk is omitted from a Software Profile?
- A . System Page File
- B . SQL Installation
- C . User Database
- D . System Database
Correct Answer: A
A
Explanation:
According to the Nutanix Database Automation (NCP-DB) course, a Software Profile is a template that defines the configuration of the database engine, such as the version, edition, features, and parameters1. It also specifies the disk layout for the database installation, such as the size, type, and mount point of each disk1. However, the System Page File disk is omitted from the Software Profile, as it is automatically created by the NDB service based on the memory size of the database server VM1. The other options are included in the Software Profile, as they are essential for the database operation and performance1.
Reference:
1: Nutanix Database Automation (NCP-DB) course, Module
2: Database Provisioning, Lesson 2.3: Software Profiles, slide 5
A
Explanation:
According to the Nutanix Database Automation (NCP-DB) course, a Software Profile is a template that defines the configuration of the database engine, such as the version, edition, features, and parameters1. It also specifies the disk layout for the database installation, such as the size, type, and mount point of each disk1. However, the System Page File disk is omitted from the Software Profile, as it is automatically created by the NDB service based on the memory size of the database server VM1. The other options are included in the Software Profile, as they are essential for the database operation and performance1.
Reference:
1: Nutanix Database Automation (NCP-DB) course, Module
2: Database Provisioning, Lesson 2.3: Software Profiles, slide 5
Question #32
A Linux OS is running a PostgreSQL instance that is managed by NDB. This instance is not working properly after a manual OS update, so an administrator has prepared a new Linux DB server VM that is ready to host the data from the broken DB.
Which action should the administrator perform to migrate data to the new DB server VM?
- A . Provision a new PostgreSQL instance from the Databases page.
- B . From The Machine policy, Authorize Database Sever VMs.
- C . Follow the Provision a PostgreSQL Instance wizard.
- D . Register the new DB Server VM in NDB.
Correct Answer: D
D
Explanation:
In this scenario, a PostgreSQL instance managed by NDB on a Linux VM is malfunctioning after a manual OS update, and a new Linux DB server VM has been prepared to host the data. To migrate the data to the new VM, the administrator must integrate the new VM into NDB’s management framework. The correct action is to register the new DB Server VM in NDB, which allows NDB to recognize and manage the VM as a database server. Once registered, the administrator can use NDB’s features (e.g., cloning, restoring, or reprovisioning) to migrate the data from the broken instance to the new VM.
Here’s why the other options are incorrect:
D
Explanation:
In this scenario, a PostgreSQL instance managed by NDB on a Linux VM is malfunctioning after a manual OS update, and a new Linux DB server VM has been prepared to host the data. To migrate the data to the new VM, the administrator must integrate the new VM into NDB’s management framework. The correct action is to register the new DB Server VM in NDB, which allows NDB to recognize and manage the VM as a database server. Once registered, the administrator can use NDB’s features (e.g., cloning, restoring, or reprovisioning) to migrate the data from the broken instance to the new VM.
Here’s why the other options are incorrect:
Question #33
An administrator needs to replace the default Nutanix self-signed certificates in Era.
Which SSL Certificate file format is supported?
- A . PKCS#7
- B . DER encoded binary X.509
- C . Base-64 encoded X 509
- D . PKCS#12
Correct Answer: C
C
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era supports x509 certificates in Base-64 encoded PEM format1. This format is used when an administrator needs to replace the default Nutanix self-signed certificates in Era1.
C
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era supports x509 certificates in Base-64 encoded PEM format1. This format is used when an administrator needs to replace the default Nutanix self-signed certificates in Era1.
Question #34
An administrator has been tasked with OS and database patching in a Nutanix NDB environment. The administrator wishes to automate these activities.
What should the administrator configure to accomplish this task?
- A . Access Control
- B . Pulse
- C . Maintenance Window
- D . SMTP Server
Correct Answer: C
C
Explanation:
To automate OS and database patching in a Nutanix NDB environment, the administrator should configure a Maintenance Window. A Maintenance Window in NDB allows the administrator to schedule automated patching tasks (e.g., OS updates and database software updates) during specified time periods, minimizing disruption to production workloads. This feature integrates with software profiles and can be set to run periodically or on-demand, ensuring patches are applied efficiently and consistently across the environment.
Option A (Access Control) is incorrect because Access Control manages user permissions, not automation of patching.
Option B (Pulse) is incorrect because Pulse is a monitoring tool, not a scheduling mechanism for patching.
Option C (Maintenance Window) is correct as it provides the scheduling and automation framework for patching activities.
Option D (SMTP Server) is incorrect because SMTP is for email notifications, not patching automation.
This configuration enhances operational efficiency and reliability.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section:
Scheduling Maintenance Windows
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles
C
Explanation:
To automate OS and database patching in a Nutanix NDB environment, the administrator should configure a Maintenance Window. A Maintenance Window in NDB allows the administrator to schedule automated patching tasks (e.g., OS updates and database software updates) during specified time periods, minimizing disruption to production workloads. This feature integrates with software profiles and can be set to run periodically or on-demand, ensuring patches are applied efficiently and consistently across the environment.
Option A (Access Control) is incorrect because Access Control manages user permissions, not automation of patching.
Option B (Pulse) is incorrect because Pulse is a monitoring tool, not a scheduling mechanism for patching.
Option C (Maintenance Window) is correct as it provides the scheduling and automation framework for patching activities.
Option D (SMTP Server) is incorrect because SMTP is for email notifications, not patching automation.
This configuration enhances operational efficiency and reliability.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section:
Scheduling Maintenance Windows
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles
Question #35
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 . Take an application consistent snapshot of the source database.
- D . Ensure that the source database has been provisioned on the remote Nutanix cluster.
Correct Answer: B
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:
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:
Question #36
A database is de-registered without removing the associated Time Machine.
What is the status of the Time Machine?
- A . Ready
- B . Frozen
- C . Paused
- D . Active
Correct Answer: B
B
Explanation:
When a database is de-registered from NDB without removing the associated Time Machine, the Time Machine enters a "Frozen" state. In this state, the Time Machine retains all existing snapshots and protection data but ceases to perform new snapshot captures or log catch-up operations. This allows the administrator to preserve the historical data for potential future use (e.g., auditing or recovery) while halting active management. The Frozen state prevents further modifications until the database is re-registered or the Time Machine is explicitly deleted.
Option A (Ready) is incorrect because "Ready" implies the Time Machine is active and prepared for new operations, which is not the case post-de-registration.
Option B (Frozen) is correct as it reflects the paused protection state after de-registration without removal.
Option C (Paused) is incorrect because "Paused" is not a formal Time Machine state in NDB; "Frozen" is the specific term.
Option D (Active) is incorrect because the Time Machine cannot remain active without an associated registered database.
This state provides flexibility for data retention without ongoing resource use.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Time Machine States
Nutanix Support & Insights, Knowledge Base Article: "Understanding Time Machine States After De-registration"
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
B
Explanation:
When a database is de-registered from NDB without removing the associated Time Machine, the Time Machine enters a "Frozen" state. In this state, the Time Machine retains all existing snapshots and protection data but ceases to perform new snapshot captures or log catch-up operations. This allows the administrator to preserve the historical data for potential future use (e.g., auditing or recovery) while halting active management. The Frozen state prevents further modifications until the database is re-registered or the Time Machine is explicitly deleted.
Option A (Ready) is incorrect because "Ready" implies the Time Machine is active and prepared for new operations, which is not the case post-de-registration.
Option B (Frozen) is correct as it reflects the paused protection state after de-registration without removal.
Option C (Paused) is incorrect because "Paused" is not a formal Time Machine state in NDB; "Frozen" is the specific term.
Option D (Active) is incorrect because the Time Machine cannot remain active without an associated registered database.
This state provides flexibility for data retention without ongoing resource use.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Time Machine States
Nutanix Support & Insights, Knowledge Base Article: "Understanding Time Machine States After De-registration"
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
Question #36
A database is de-registered without removing the associated Time Machine.
What is the status of the Time Machine?
- A . Ready
- B . Frozen
- C . Paused
- D . Active
Correct Answer: B
B
Explanation:
When a database is de-registered from NDB without removing the associated Time Machine, the Time Machine enters a "Frozen" state. In this state, the Time Machine retains all existing snapshots and protection data but ceases to perform new snapshot captures or log catch-up operations. This allows the administrator to preserve the historical data for potential future use (e.g., auditing or recovery) while halting active management. The Frozen state prevents further modifications until the database is re-registered or the Time Machine is explicitly deleted.
Option A (Ready) is incorrect because "Ready" implies the Time Machine is active and prepared for new operations, which is not the case post-de-registration.
Option B (Frozen) is correct as it reflects the paused protection state after de-registration without removal.
Option C (Paused) is incorrect because "Paused" is not a formal Time Machine state in NDB; "Frozen" is the specific term.
Option D (Active) is incorrect because the Time Machine cannot remain active without an associated registered database.
This state provides flexibility for data retention without ongoing resource use.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Time Machine States
Nutanix Support & Insights, Knowledge Base Article: "Understanding Time Machine States After De-registration"
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
B
Explanation:
When a database is de-registered from NDB without removing the associated Time Machine, the Time Machine enters a "Frozen" state. In this state, the Time Machine retains all existing snapshots and protection data but ceases to perform new snapshot captures or log catch-up operations. This allows the administrator to preserve the historical data for potential future use (e.g., auditing or recovery) while halting active management. The Frozen state prevents further modifications until the database is re-registered or the Time Machine is explicitly deleted.
Option A (Ready) is incorrect because "Ready" implies the Time Machine is active and prepared for new operations, which is not the case post-de-registration.
Option B (Frozen) is correct as it reflects the paused protection state after de-registration without removal.
Option C (Paused) is incorrect because "Paused" is not a formal Time Machine state in NDB; "Frozen" is the specific term.
Option D (Active) is incorrect because the Time Machine cannot remain active without an associated registered database.
This state provides flexibility for data retention without ongoing resource use.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Time Machine States
Nutanix Support & Insights, Knowledge Base Article: "Understanding Time Machine States After De-registration"
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
Question #38
Which Era component collects logs and snapshots from the database?
- A . Profiles
- B . Era Database Agent
- C . SLAs
- D . Time Machine
Correct Answer: D
D
Explanation:
The Era copy data management service includes several components, one of which is the Time Machine. The Time Machine is responsible for collecting logs and snapshots from the database123. This functionality allows for granular clone and refresh operations, making it a crucial part of the Nutanix Era’s database as a service (DBaaS) solution1.
D
Explanation:
The Era copy data management service includes several components, one of which is the Time Machine. The Time Machine is responsible for collecting logs and snapshots from the database123. This functionality allows for granular clone and refresh operations, making it a crucial part of the Nutanix Era’s database as a service (DBaaS) solution1.
Question #39
While using Time Machine (TM) to restore a source database, the option to restore data to Point in Time is not available.
What should an administrator do to restore databases to Point in Time?
- A . Restore Source DB using a snapshot
- B . Update TM SLA to BRONZE or higher.
- C . Create DB clone using a snapshot.
- D . Update TM SLA to BRASS or lower.
Correct Answer: B
B
Explanation:
In Nutanix Database Service (NDB), the Time Machine (TM) feature allows restores, including Point-in-Time (PIT) restores, which require continuous log retention to replay transaction logs to a specific moment. If the option to restore data to a Point in Time is unavailable, it indicates that the current Time Machine Service Level Agreement (SLA) does not support continuous log retention. NDB SLAs are categorized (e.g., BRONZE, SILVER, GOLD), with BRONZE or higher levels required to enable PIT restore by including continuous log retention. The administrator must update the TM SLA to at least BRONZE to enable this feature, ensuring logs are retained for PIT operations.
Option A (Restore Source DB using a snapshot) is incorrect because a snapshot-only restore does not support PIT; it restores to the snapshot time only.
Option B (Update TM SLA to BRONZE or higher) is correct as it enables continuous log retention necessary for PIT restores.
Option C (Create DB clone using a snapshot) is incorrect because cloning from a snapshot does not provide PIT capability without log retention.
Option D (Update TM SLA to BRASS or lower) is incorrect because "BRASS" is not a valid SLA tier, and lowering the SLA would not enable PIT.
This adjustment ensures PIT restore functionality.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Configuring SLAs for Point-in-Time Restore
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
B
Explanation:
In Nutanix Database Service (NDB), the Time Machine (TM) feature allows restores, including Point-in-Time (PIT) restores, which require continuous log retention to replay transaction logs to a specific moment. If the option to restore data to a Point in Time is unavailable, it indicates that the current Time Machine Service Level Agreement (SLA) does not support continuous log retention. NDB SLAs are categorized (e.g., BRONZE, SILVER, GOLD), with BRONZE or higher levels required to enable PIT restore by including continuous log retention. The administrator must update the TM SLA to at least BRONZE to enable this feature, ensuring logs are retained for PIT operations.
Option A (Restore Source DB using a snapshot) is incorrect because a snapshot-only restore does not support PIT; it restores to the snapshot time only.
Option B (Update TM SLA to BRONZE or higher) is correct as it enables continuous log retention necessary for PIT restores.
Option C (Create DB clone using a snapshot) is incorrect because cloning from a snapshot does not provide PIT capability without log retention.
Option D (Update TM SLA to BRASS or lower) is incorrect because "BRASS" is not a valid SLA tier, and lowering the SLA would not enable PIT.
This adjustment ensures PIT restore functionality.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Configuring SLAs for Point-in-Time Restore
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
Question #40
An administrator needs to register a Nutanix cluster with NDB.
Which condition requires the administrator to create a manual storage mapping between the remote container and NDB provisioning container?
- A . NDB Server container and NDB Provisioning container are separate.
- B . Disaster Recovery Network Segmentation is enabled on the cluster.
- C . Nutanix Database Service High Availability is enabled on the cluster.
- D . DB VMs are stored in the NDB Server or NDB Provisioning container.
Correct Answer: A
A
Explanation:
When registering a Nutanix cluster with NDB, a manual storage mapping between the remote container and the NDB provisioning container is required if the NDB Server container and NDB Provisioning container are separate. This separation occurs when the storage containers used by the NDB server (for its own operations) and the provisioning container (for database VMs) are distinct, either due to multi-cluster setups or custom configurations. Manual mapping ensures NDB can correctly allocate storage resources and manage database provisioning across these containers.
Other conditions do not necessitate manual mapping:
B. Disaster Recovery Network Segmentation is enabled on the cluster: This affects networking, not storage mapping.
C. Nutanix Database Service High Availability is enabled on the cluster: HA configurations handle replication, not container mapping.
D. DB VMs are stored in the NDB Server or NDB Provisioning container: This is a typical setup and does not require manual mapping unless containers differ.
Thus, the verified answer is A, addressing storage container separation.
Official Nutanix Database Automation
Reference: Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring
an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster.
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix Cluster (applicable to v6.10).
Nutanix NDB Administration Guide: "Storage Container Mapping" section.
A
Explanation:
When registering a Nutanix cluster with NDB, a manual storage mapping between the remote container and the NDB provisioning container is required if the NDB Server container and NDB Provisioning container are separate. This separation occurs when the storage containers used by the NDB server (for its own operations) and the provisioning container (for database VMs) are distinct, either due to multi-cluster setups or custom configurations. Manual mapping ensures NDB can correctly allocate storage resources and manage database provisioning across these containers.
Other conditions do not necessitate manual mapping:
B. Disaster Recovery Network Segmentation is enabled on the cluster: This affects networking, not storage mapping.
C. Nutanix Database Service High Availability is enabled on the cluster: HA configurations handle replication, not container mapping.
D. DB VMs are stored in the NDB Server or NDB Provisioning container: This is a typical setup and does not require manual mapping unless containers differ.
Thus, the verified answer is A, addressing storage container separation.
Official Nutanix Database Automation
Reference: Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring
an NDB Solution, Lesson 2.3: Registering a Nutanix Cluster.
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.2: Register a Nutanix Cluster (applicable to v6.10).
Nutanix NDB Administration Guide: "Storage Container Mapping" section.