Practice Free NCP-DB-6.5 Exam Online Questions
Question #61
What is used to temporarily store the transaction logs of the source database before they are copied to the log?
- A . Database Agent
- B . NDB Drive
- C . Time Machine
- D . NDB Profiles
Correct Answer: A
A
Explanation:
The Database Agent is used to temporarily store the transaction logs of the source database before they are copied to the log. This is a critical component for ensuring data consistency and recovery in database operations.
Reference: Nutanix Database Automation documentation, focusing on database agents and their roles in transaction log management.
A
Explanation:
The Database Agent is used to temporarily store the transaction logs of the source database before they are copied to the log. This is a critical component for ensuring data consistency and recovery in database operations.
Reference: Nutanix Database Automation documentation, focusing on database agents and their roles in transaction log management.
Question #62
An administrator wants to migrate an existing MSSQL Server database to NDB.
How should the administrator complete this migration?
- A . Use Nutanix Move to migrate the database server VM.
- B . Provision a new database server VM and database then migrate the data.
- C . Create a new database server VM and database then register it with NDB.
- D . Backup your database VM and import it into Nutanix.
Correct Answer: B
B
Explanation:
To migrate an existing Microsoft SQL Server (MSSQL) database to NDB, the recommended approach is to:
Provision a new database server VM and database: Use the NDB interface to provision a new VM and configure an MSSQL database instance on the Nutanix platform. This leverages NDB’s automated provisioning capabilities to ensure compatibility with Nutanix infrastructure.
Migrate the data: Transfer the data from the existing MSSQL database to the newly provisioned database. This can be achieved using native MSSQL tools (e.g., backup/restore, log shipping, or replication) or NDB’s data migration features, such as cloning or restoring from a backup, depending on the source environment.
Other options are incorrect or incomplete:
B
Explanation:
To migrate an existing Microsoft SQL Server (MSSQL) database to NDB, the recommended approach is to:
Provision a new database server VM and database: Use the NDB interface to provision a new VM and configure an MSSQL database instance on the Nutanix platform. This leverages NDB’s automated provisioning capabilities to ensure compatibility with Nutanix infrastructure.
Migrate the data: Transfer the data from the existing MSSQL database to the newly provisioned database. This can be achieved using native MSSQL tools (e.g., backup/restore, log shipping, or replication) or NDB’s data migration features, such as cloning or restoring from a backup, depending on the source environment.
Other options are incorrect or incomplete:
Question #63
Which two network prerequisites are required to deploy an Era instance in production? (Choose two.)
- A . NTP, DNS servers, gateway, and subnet mask must be available and visible to Ere,
- B . One static IP address must be available and changed using CLI after VM deployment.
- C . A storage container must be available es a prerequisite.
- D . An SMTP server and details must be provided for notifications.
Correct Answer: A, B
A, B
Explanation:
Option A: Nutanix Era requires network prerequisites like NTP, DNS servers, gateway, and subnet mask to be available and visible. These are essential for the proper functioning of the Era instance1.
Option B: One static IP address must be available and can be changed using CLI after VM deployment. This is necessary for the Era VM to communicate with other components in the network1.
Option C: While a storage container is necessary for Nutanix infrastructure, it is not a network prerequisite specifically for deploying an Era instance.
Option D: An SMTP server and details are typically used for sending notifications, but they are not a network prerequisite for deploying an Era instance. They are more related to the operational aspect post-deployment.
A, B
Explanation:
Option A: Nutanix Era requires network prerequisites like NTP, DNS servers, gateway, and subnet mask to be available and visible. These are essential for the proper functioning of the Era instance1.
Option B: One static IP address must be available and can be changed using CLI after VM deployment. This is necessary for the Era VM to communicate with other components in the network1.
Option C: While a storage container is necessary for Nutanix infrastructure, it is not a network prerequisite specifically for deploying an Era instance.
Option D: An SMTP server and details are typically used for sending notifications, but they are not a network prerequisite for deploying an Era instance. They are more related to the operational aspect post-deployment.
Question #64
An administrator wants to test the provisioning capabilities after a new NDB deployment.
Which database instance would be available to accomplish this task?
- A . PostgreSQL
- B . Oracle DB
- C . MSSQL Server
- D . MongoDB
Correct Answer: A
A
Explanation:
After a new NDB deployment, the administrator can test the provisioning capabilities using a database instance that is fully supported and readily configurable out of the box. PostgreSQL is the most suitable option because it is one of the core database engines supported by NDB from the initial deployment, with built-in provisioning templates and HA capabilities. NDB provides a streamlined process to provision PostgreSQL instances, making it an ideal choice for testing provisioning workflows, including VM creation, storage allocation, and network configuration.
Other options may require additional setup or licensing:
B. Oracle DB: Requires specific licensing and additional configuration, not typically available for initial testing.
C. MSSQL Server: Supported but may need Microsoft licensing and setup, less immediate than PostgreSQL.
D. MongoDB: Supported but less commonly used for initial testing due to its NoSQL nature and additional configuration needs.
Thus, the verified answer is A, reflecting PostgreSQL’s accessibility for testing.
Official Nutanix Database Automation
Reference: Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database
Instances, Lesson 3.1: Provisioning Databases.
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Provision Database Instances (applicable to v6.10).
Nutanix NDB Administration Guide: "Supported Databases for Provisioning" section, noting PostgreSQL availability.
A
Explanation:
After a new NDB deployment, the administrator can test the provisioning capabilities using a database instance that is fully supported and readily configurable out of the box. PostgreSQL is the most suitable option because it is one of the core database engines supported by NDB from the initial deployment, with built-in provisioning templates and HA capabilities. NDB provides a streamlined process to provision PostgreSQL instances, making it an ideal choice for testing provisioning workflows, including VM creation, storage allocation, and network configuration.
Other options may require additional setup or licensing:
B. Oracle DB: Requires specific licensing and additional configuration, not typically available for initial testing.
C. MSSQL Server: Supported but may need Microsoft licensing and setup, less immediate than PostgreSQL.
D. MongoDB: Supported but less commonly used for initial testing due to its NoSQL nature and additional configuration needs.
Thus, the verified answer is A, reflecting PostgreSQL’s accessibility for testing.
Official Nutanix Database Automation
Reference: Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database
Instances, Lesson 3.1: Provisioning Databases.
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Provision Database Instances (applicable to v6.10).
Nutanix NDB Administration Guide: "Supported Databases for Provisioning" section, noting PostgreSQL availability.
Question #65
An administrator has configured NDB HA across multiple Nutanix clusters.
Which failure scenario will require manual interaction for the recovery?
- A . More than one API Server VM is down.
- B . One repository VM is down.
- C . More than one HA proxy VM is down.
- D . NDB Server process is down.
Correct Answer: A
A
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.
Reference:
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
A
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.
Reference:
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
Question #66
Which two security options are available when configuring an SMTP server for sending alert notifications via email? (Choose two.)
- A . SSL
- B . S/MIME
- C . DKIM
- D . TLS
Correct Answer: AD
AD
Explanation:
When configuring an SMTP server for sending alert notifications via email in NDB, the two security options available are SSL and TLS. These protocols encrypt the email communication between NDB and the SMTP server, ensuring the confidentiality and integrity of alert notifications. NDB supports both options to accommodate different SMTP server configurations, with TLS being the more modern standard and SSL as a legacy option.
Other options are not applicable:
B. S/MIME: This is used for email content encryption, not SMTP server configuration.
C. DKIM: This is a domain authentication method, not a security protocol for SMTP.
Thus, the verified answers are A and D, reflecting NDB’s SMTP security features.
Official Nutanix Database Automation
Reference: Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.1: Configuring Alert Notifications.
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.2: Manage Alerts (applicable to v6.10).
Nutanix NDB Administration Guide: "Configuring SMTP for Alerts" section, listing SSL and TLS options.
AD
Explanation:
When configuring an SMTP server for sending alert notifications via email in NDB, the two security options available are SSL and TLS. These protocols encrypt the email communication between NDB and the SMTP server, ensuring the confidentiality and integrity of alert notifications. NDB supports both options to accommodate different SMTP server configurations, with TLS being the more modern standard and SSL as a legacy option.
Other options are not applicable:
B. S/MIME: This is used for email content encryption, not SMTP server configuration.
C. DKIM: This is a domain authentication method, not a security protocol for SMTP.
Thus, the verified answers are A and D, reflecting NDB’s SMTP security features.
Official Nutanix Database Automation
Reference: Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.1: Configuring Alert Notifications.
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.2: Manage Alerts (applicable to v6.10).
Nutanix NDB Administration Guide: "Configuring SMTP for Alerts" section, listing SSL and TLS options.
Question #67
What is the terminology used for registering an existing database with Era?
- A . Greenfield Database
- B . Brownfield Database
- C . Cloned Database
- D . Source Database
Correct Answer: B
B
Explanation:
In the context of Nutanix Era, the term “Brownfield Database” is used to refer to an existing database that is registered with Era1. This process allows Era to bring Database as a Service (DBaaS) capabilities to your existing database2. It’s important to note that before you register a database with Era, certain prerequisites must be met3.
B
Explanation:
In the context of Nutanix Era, the term “Brownfield Database” is used to refer to an existing database that is registered with Era1. This process allows Era to bring Database as a Service (DBaaS) capabilities to your existing database2. It’s important to note that before you register a database with Era, certain prerequisites must be met3.
Question #68
What is the first step to add Time Machine (TM) data access to a Nutanix cluster?
- A . Enable multi-cluster in NDB.
- B . Disable multi-cluster in ND8.
- C . Register the required Nutanix clusters in ND8.
- D . Delete the TM data from the source database.
Correct Answer: C
C
Explanation:
To add Time Machine data access to a Nutanix cluster, the first step is to register the cluster in NDB. This will allow NDB to discover and manage the databases and snapshots on the cluster. You can register multiple Nutanix clusters in NDB using the Add Cluster option in the NDB settings page. You can also specify the cluster role, such as source, target, or both, depending on the data access and replication needs. Enabling or disabling multi-cluster in NDB is not the first step, as this is a global setting that affects the entire NDB instance. Deleting the TM data from the source database is not the first step, as this will remove the data protection and availability of the database.
Reference: Nutanix Database Management & Automation Training Course, Module 6: Managing NDB Multi-Cluster, Lesson 1: NDB Multi-Cluster Overview, Slide 5: Registering Nutanix Clusters
Nutanix Certified Professional – Database Automation (NCP-DB) 5 Exam, Section 6: Administer an NDB Environment, Objective 6.4: Apply procedural concepts to add Nutanix clusters to NDB
C
Explanation:
To add Time Machine data access to a Nutanix cluster, the first step is to register the cluster in NDB. This will allow NDB to discover and manage the databases and snapshots on the cluster. You can register multiple Nutanix clusters in NDB using the Add Cluster option in the NDB settings page. You can also specify the cluster role, such as source, target, or both, depending on the data access and replication needs. Enabling or disabling multi-cluster in NDB is not the first step, as this is a global setting that affects the entire NDB instance. Deleting the TM data from the source database is not the first step, as this will remove the data protection and availability of the database.
Reference: Nutanix Database Management & Automation Training Course, Module 6: Managing NDB Multi-Cluster, Lesson 1: NDB Multi-Cluster Overview, Slide 5: Registering Nutanix Clusters
Nutanix Certified Professional – Database Automation (NCP-DB) 5 Exam, Section 6: Administer an NDB Environment, Objective 6.4: Apply procedural concepts to add Nutanix clusters to NDB
Question #69
What is required to create an NDB Software Profile?
- A . Installer package for database software
- B . Database server VM registered with NDB
- C . Patch file for the installed databases
- D . OS image registered with Prism Element
Correct Answer: A
A
Explanation:
An NDB Software Profile is a template of the OS and database engine that you can use to provision or clone database server VMs using NDB. To create a software profile, you need to upload an installer package for the database software that you want to use, such as SQL Server or Oracle. The installer package must be compatible with the OS image that you have registered with Prism Element. You do not need a database server VM registered with NDB, a patch file for the installed databases, or an OS image registered with Prism Element to create a software profile. Those are required for other tasks, such as creating a software profile version, registering a database server VM, or provisioning a database server VM.
Reference: Nutanix Benefit 8: Integrated Self-service Database Management, Nutanix Support & Insights, section “NDB Software”
A
Explanation:
An NDB Software Profile is a template of the OS and database engine that you can use to provision or clone database server VMs using NDB. To create a software profile, you need to upload an installer package for the database software that you want to use, such as SQL Server or Oracle. The installer package must be compatible with the OS image that you have registered with Prism Element. You do not need a database server VM registered with NDB, a patch file for the installed databases, or an OS image registered with Prism Element to create a software profile. Those are required for other tasks, such as creating a software profile version, registering a database server VM, or provisioning a database server VM.
Reference: Nutanix Benefit 8: Integrated Self-service Database Management, Nutanix Support & Insights, section “NDB Software”
Question #70
An administrator needs to take multiple snapshots per day and retain them for one week.
How should the administrator define and schedule the SLA?
- A . • Daily snapshot retention: 7 days
• Daily snapshot at: 2 - B . • Weekly snapshot retention: 1 week
• Daily Snapshot at: 2 - C . • Weekly snapshot retention: 1 week
• Snapshots per Day: 2 - D . • Daily snapshot retention: 7 days
• Snapshots per Day: 2
Correct Answer: D
D
Explanation:
The correct answer is D because it matches the requirement of taking multiple snapshots per day and retaining them for one week.
Option A is incorrect because it only takes one snapshot per day, which is not enough for the administrator’s need.
Option B is incorrect because it only retains the snapshots for one week, which means the older snapshots will be deleted after seven days.
Option C is incorrect because it only takes two snapshots per week, which is not frequent enough for the administrator’s need.
Reference: The following sources provide more information about the SLA retention policies and how to create and modify them in NDB:
Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases
Using Time Machine, Lesson 4.1: Creating and Modifying SLA Retention Policies
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 5 – Protect NDB-managed Databases Using Time Machine
Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section 6.1: Creating and Modifying SLA Retention Policies
D
Explanation:
The correct answer is D because it matches the requirement of taking multiple snapshots per day and retaining them for one week.
Option A is incorrect because it only takes one snapshot per day, which is not enough for the administrator’s need.
Option B is incorrect because it only retains the snapshots for one week, which means the older snapshots will be deleted after seven days.
Option C is incorrect because it only takes two snapshots per week, which is not frequent enough for the administrator’s need.
Reference: The following sources provide more information about the SLA retention policies and how to create and modify them in NDB:
Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases
Using Time Machine, Lesson 4.1: Creating and Modifying SLA Retention Policies
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 5 – Protect NDB-managed Databases Using Time Machine
Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section 6.1: Creating and Modifying SLA Retention Policies