Practice Free NCP-DB-6.5 Exam Online Questions
Question #1
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 BRONZE SLA
- C . DEFAULT_008 SILVER SLA
- D . DEFAULT_008 BRASS SLA
Correct Answer: C
C
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.
Reference:
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]
C
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.
Reference:
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]
Question #2
An administrator is adding a stretched VLAN in NDB.
Which VLAN type(s) will satisfy this task?
- A . Only VLANs that are not managed in NDB
- B . Only static VLANs that are managed in NDB
- C . Only dynamic VLANs
- D . Both static and dynamic VLANs
Correct Answer: D
D
Explanation:
The administrator can add a stretched VLAN in NDB using either static or dynamic VLANs. A stretched VLAN is a VLAN that spans across multiple Nutanix clusters, and allows the NDB-managed databases to communicate and migrate between different clusters. A static VLAN is a VLAN that is manually configured and assigned to the database server VMs and the databases by the administrator. A dynamic VLAN is a VLAN that is automatically configured and assigned to the database server VMs and the databases by the NDB instance, using the Nutanix Calm orchestration service. Both static and dynamic VLANs can be used to create a stretched VLAN in NDB, as long as they have the same VLAN ID and network configuration across the clusters.
The administrator cannot add a stretched VLAN in NDB using only VLANs that are not managed in NDB. A VLAN that is not managed in NDB is a VLAN that is configured and assigned to the database server VMs and the databases outside of the NDB instance, using the Nutanix Prism web console or other tools. A VLAN that is not managed in NDB cannot be used to create a stretched VLAN in NDB, as it is not recognized or controlled by the NDB instance.
Reference:
Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration,
Lesson 4.1: Nutanix Era Configuration, slide 8.
Nutanix Database Management & Automation Training Course, Module 6: Nutanix Era Disaster
Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 6-7.
D
Explanation:
The administrator can add a stretched VLAN in NDB using either static or dynamic VLANs. A stretched VLAN is a VLAN that spans across multiple Nutanix clusters, and allows the NDB-managed databases to communicate and migrate between different clusters. A static VLAN is a VLAN that is manually configured and assigned to the database server VMs and the databases by the administrator. A dynamic VLAN is a VLAN that is automatically configured and assigned to the database server VMs and the databases by the NDB instance, using the Nutanix Calm orchestration service. Both static and dynamic VLANs can be used to create a stretched VLAN in NDB, as long as they have the same VLAN ID and network configuration across the clusters.
The administrator cannot add a stretched VLAN in NDB using only VLANs that are not managed in NDB. A VLAN that is not managed in NDB is a VLAN that is configured and assigned to the database server VMs and the databases outside of the NDB instance, using the Nutanix Prism web console or other tools. A VLAN that is not managed in NDB cannot be used to create a stretched VLAN in NDB, as it is not recognized or controlled by the NDB instance.
Reference:
Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration,
Lesson 4.1: Nutanix Era Configuration, slide 8.
Nutanix Database Management & Automation Training Course, Module 6: Nutanix Era Disaster
Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 6-7.
Question #3
How long is the default continuous recovery for the Gold SLA in Era Time Machine?
- A . 30 days
- B . 15 days
- C . 60 days
- D . 90 days
Correct Answer: A
A
Explanation:
The default continuous recovery for the Gold SLA in Era Time Machine is 30 days1. This means that the system keeps a continuous recovery point for the last 30 days, allowing you to restore your database to any point within this period1.
A
Explanation:
The default continuous recovery for the Gold SLA in Era Time Machine is 30 days1. This means that the system keeps a continuous recovery point for the last 30 days, allowing you to restore your database to any point within this period1.
Question #4
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 Patch Now advanced options
- B . Exclude the appropriate repositories on the VM prior to patching.
- C . Exclude the appropriate repositories on the VM and reboot prior to patching.
- D . Define a pre-script to disable the repositories in the Maintenance Window advanced options.
Correct Answer: B
B
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.
Reference:
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
B
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.
Reference:
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
Question #5
An administrator begins an SQL database clone deletion, but notices it fails almost immediately.
What could be the cause of this failure?
- A . A refresh operation is in progress.
- B . The clone has been marked as Immutable.
- C . The database was not marked as Offline before the operation.
- D . The database data drives are shared with other applications.
Correct Answer: B
B
Explanation:
If an SQL database clone deletion fails immediately in NDB, the most likely cause is that the clone has been marked as Immutable. An immutable clone is protected from deletion to prevent accidental data loss, often set for critical development or testing environments. This protection must be explicitly removed by the administrator (e.g., via the NDB GUI or CLI) before the deletion can proceed.
Option A (A refresh operation is in progress) is incorrect because a refresh operation would delay but not immediately fail the deletion.
Option B (The clone has been marked as Immutable) is correct as immutability blocks deletion until changed.
Option C (The database was not marked as Offline before the operation) is incorrect because the offline state is not a prerequisite for clone deletion.
Option D (The database data drives are shared with other applications) is incorrect because shared drives might cause issues, but immutability is a more direct cause of immediate failure.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Clones and Deletion
Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Clone Deletion Failures in NDB"
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
B
Explanation:
If an SQL database clone deletion fails immediately in NDB, the most likely cause is that the clone has been marked as Immutable. An immutable clone is protected from deletion to prevent accidental data loss, often set for critical development or testing environments. This protection must be explicitly removed by the administrator (e.g., via the NDB GUI or CLI) before the deletion can proceed.
Option A (A refresh operation is in progress) is incorrect because a refresh operation would delay but not immediately fail the deletion.
Option B (The clone has been marked as Immutable) is correct as immutability blocks deletion until changed.
Option C (The database was not marked as Offline before the operation) is incorrect because the offline state is not a prerequisite for clone deletion.
Option D (The database data drives are shared with other applications) is incorrect because shared drives might cause issues, but immutability is a more direct cause of immediate failure.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Clones and Deletion
Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Clone Deletion Failures in NDB"
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
Question #5
An administrator begins an SQL database clone deletion, but notices it fails almost immediately.
What could be the cause of this failure?
- A . A refresh operation is in progress.
- B . The clone has been marked as Immutable.
- C . The database was not marked as Offline before the operation.
- D . The database data drives are shared with other applications.
Correct Answer: B
B
Explanation:
If an SQL database clone deletion fails immediately in NDB, the most likely cause is that the clone has been marked as Immutable. An immutable clone is protected from deletion to prevent accidental data loss, often set for critical development or testing environments. This protection must be explicitly removed by the administrator (e.g., via the NDB GUI or CLI) before the deletion can proceed.
Option A (A refresh operation is in progress) is incorrect because a refresh operation would delay but not immediately fail the deletion.
Option B (The clone has been marked as Immutable) is correct as immutability blocks deletion until changed.
Option C (The database was not marked as Offline before the operation) is incorrect because the offline state is not a prerequisite for clone deletion.
Option D (The database data drives are shared with other applications) is incorrect because shared drives might cause issues, but immutability is a more direct cause of immediate failure.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Clones and Deletion
Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Clone Deletion Failures in NDB"
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
B
Explanation:
If an SQL database clone deletion fails immediately in NDB, the most likely cause is that the clone has been marked as Immutable. An immutable clone is protected from deletion to prevent accidental data loss, often set for critical development or testing environments. This protection must be explicitly removed by the administrator (e.g., via the NDB GUI or CLI) before the deletion can proceed.
Option A (A refresh operation is in progress) is incorrect because a refresh operation would delay but not immediately fail the deletion.
Option B (The clone has been marked as Immutable) is correct as immutability blocks deletion until changed.
Option C (The database was not marked as Offline before the operation) is incorrect because the offline state is not a prerequisite for clone deletion.
Option D (The database data drives are shared with other applications) is incorrect because shared drives might cause issues, but immutability is a more direct cause of immediate failure.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Managing Clones and Deletion
Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting Clone Deletion Failures in NDB"
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
Question #7
An administrator has run into an error when provisioning a new Oracle database VM.
What is the best action that the administrator should perform in the NDB GUI to provide the most complete picture to send to Nutanix support on that specific operation?
- A . From the Administration section of NDB. go to the Diagnostics section and chose Generate Bundle.
- B . Copy the error message from the Operations menu.
- C . In the operations menu, select the job the failed and choose Generate Bundle from the lower right.
- D . Take a screen shot of the error in the Operations menu.
Correct Answer: C
C
Explanation:
When an administrator encounters an error provisioning a new Oracle database VM in NDB, the best action to provide Nutanix support with the most complete picture is to select the failed job in the Operations menu and choose Generate Bundle from the lower right. The "Generate Bundle" option creates a comprehensive diagnostic package, including logs, configuration details, and error traces specific to the failed operation. This bundle is ideal for troubleshooting and can be uploaded to Nutanix Support for analysis.
Other options are less comprehensive:
C
Explanation:
When an administrator encounters an error provisioning a new Oracle database VM in NDB, the best action to provide Nutanix support with the most complete picture is to select the failed job in the Operations menu and choose Generate Bundle from the lower right. The "Generate Bundle" option creates a comprehensive diagnostic package, including logs, configuration details, and error traces specific to the failed operation. This bundle is ideal for troubleshooting and can be uploaded to Nutanix Support for analysis.
Other options are less comprehensive:
Question #8
A clone needs to be created on an existing database server, but there are no Authorized database servers defined to support the cloned database.
In which two ways can Database Server VMs be authorized during a Clone Create operation? (Choose two.)
- A . Within Time Machine, use the Actions menu and Authorize Database Server VMs to identify which database server VMs to authorize for clones.
- B . Within the Database Server VM Summary window, update the database sever to be authorized for supporting cloned databases.
- C . During the Clone creation process, click the plus icon to authorize one or more database server VMs.
- D . During the database server provisioning process, flag the database server to be authorized for supporting cloned databases.
Correct Answer: AC
AC
Explanation:
When creating a clone on an existing database server but no Authorized database servers are defined to support the cloned database, the administrator must authorize the necessary Database Server VMs. Two valid methods exist within NDB: (1) Using the Time Machine interface, the administrator can navigate to the Actions menu and select "Authorize Database Server VMs" to designate specific VMs for clone support, providing a proactive authorization step. (2) During the Clone creation process, the wizard includes an option (e.g., a plus icon) to authorize one or more database server VMs on the fly, streamlining the process if authorization is needed mid-operation.
Option A (Within Time Machine, use the Actions menu and Authorize Database Server VMs to identify which database server VMs to authorize for clones) is correct as it is a dedicated authorization method in Time Machine.
Option B (Within the Database Server VM Summary window, update the database server to be authorized for supporting cloned databases) is incorrect because the Summary window is for viewing, not authorizing, clone support.
Option C (During the Clone creation process, click the plus icon to authorize one or more database server VMs) is correct as it allows real-time authorization during cloning.
Option D (During the database server provisioning process, flag the database server to be authorized for supporting cloned databases) is incorrect because authorization is not typically set during initial provisioning but rather during clone operations.
These methods ensure the clone can be created on authorized servers.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Authorizing Database Servers for Clones
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
AC
Explanation:
When creating a clone on an existing database server but no Authorized database servers are defined to support the cloned database, the administrator must authorize the necessary Database Server VMs. Two valid methods exist within NDB: (1) Using the Time Machine interface, the administrator can navigate to the Actions menu and select "Authorize Database Server VMs" to designate specific VMs for clone support, providing a proactive authorization step. (2) During the Clone creation process, the wizard includes an option (e.g., a plus icon) to authorize one or more database server VMs on the fly, streamlining the process if authorization is needed mid-operation.
Option A (Within Time Machine, use the Actions menu and Authorize Database Server VMs to identify which database server VMs to authorize for clones) is correct as it is a dedicated authorization method in Time Machine.
Option B (Within the Database Server VM Summary window, update the database server to be authorized for supporting cloned databases) is incorrect because the Summary window is for viewing, not authorizing, clone support.
Option C (During the Clone creation process, click the plus icon to authorize one or more database server VMs) is correct as it allows real-time authorization during cloning.
Option D (During the database server provisioning process, flag the database server to be authorized for supporting cloned databases) is incorrect because authorization is not typically set during initial provisioning but rather during clone operations.
These methods ensure the clone can be created on authorized servers.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section:
Authorizing Database Servers for Clones
Nutanix Certified Professional – Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine
Question #9
Which Time Machine feature allows developers to automate the data refresh for their clones?
- A . Manual Backup
- B . update
- C . Log Catchup
- D . Schedule
Correct Answer: D
D
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, the Schedule feature of the Time Machine allows developers to automate the data refresh for their clones1. This feature eliminates the time-consuming, complex process of database clone/refresh, allowing admins to create database clones/refresh to any point in time in just a few minutes1. Please refer to the official Nutanix documentation and training materials for more detailed information2.
D
Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, the Schedule feature of the Time Machine allows developers to automate the data refresh for their clones1. This feature eliminates the time-consuming, complex process of database clone/refresh, allowing admins to create database clones/refresh to any point in time in just a few minutes1. Please refer to the official Nutanix documentation and training materials for more detailed information2.
Question #10
Era allows custom metadata to be assigned to entities (clones, time machines, databases, and database servers) by using which component?
- A . Tags
- B . Notes
- C . Text
- D . Index
Correct Answer: A
A
Explanation:
Nutanix Era allows custom metadata to be assigned to entities (clones, time machines, databases, and database servers) by using Tags. Tags are a component of Nutanix Era that allows users to assign custom metadata to various entities, enhancing the ability to organize, search, and manage these entities within the Era platform1.
A
Explanation:
Nutanix Era allows custom metadata to be assigned to entities (clones, time machines, databases, and database servers) by using Tags. Tags are a component of Nutanix Era that allows users to assign custom metadata to various entities, enhancing the ability to organize, search, and manage these entities within the Era platform1.