Nutanix NCP-DB Practice Questions

Explanation:
Before updating Oracle Database software, you need to download the Patch Set Update (PSU) from Oracle support. A PSU is a collection of critical and security patches for Oracle products. You need to have a valid Oracle account and access to the My Oracle Support portal to download the PSU. You also need to check the compatibility and prerequisites of the PSU before applying it to your Oracle Database software. NDB uses outof- place patching for Oracle, which means you need to create a new software profile version with the patched Oracle software and use it to update your existing databases.

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.

Explanation:
NDB sends notifications when alerts are generated via email. The email notifications can be configured to send to one or more recipients, and can be customized to include the alert severity, category, description, and resolution steps. The email notifications help to inform the database administrator and other stakeholders about the status and issues of the NDB-managed databases and operations.
NDB does not send notifications via SNMP, APIs, or Pulse. SNMP is a protocol for collecting and organizing information about managed devices on a network. APIs are interfaces for communicating and exchanging data between different applications or systems. Pulse is a feature of the Nutanix cluster that collects and sends diagnostic and usage data to Nutanix for analysis and support.

Explanation:
The correct answer is D because it allows the administrator to make the profile available to all users without requiring any additional permissions or roles. A profile is a collection of settings that define how NDB manages a database server or a database. By default, a profile is only available to the user who created it and the Database Admin role. To make a profile available to all users, the administrator can update the profile and set the available state to All. This will enable all users to view and use the profile for their database operations. The other options are not correct because they either require additional steps or do not achieve the desired outcome. Option A is not correct because creating an Access Control role with the Create Profile right and assigning it to all users will only allow them to create their own profiles, not use the existing one. Option B is not correct because creating an Access Control group with the desired users and granting it the Database Admin role will only make the profile available to those users, not all users. Option C is not correct because updating the profile and setting the status to Published will not change the availability of the profile, only the state of the profile. A published profile is a profile that has been tested and verified by the administrator and is ready for use. A draft profile is a profile that is still under development or testing and is not ready for use.

Explanation:
To roll back an Oracle patch on a database server VM using NDB, the patch must have been applied using NDB in the first place. This is because NDB maintains a patch inventory and history for each database server VM and database that it manages. NDB uses this information to determine which patches can be rolled back and how to revert the changes made by the patch. If the patch was applied outside of NDB, NDB would not have the patch information and would not be able to roll back the patch. Therefore, the patch must have been applied using NDB for the rollback action to be successful. The other options are not required for the rollback action. The database does not need to be shut down or in read-only mode, as NDB can perform the rollback operation online. The patch does not need to be applied on Grid home only, as NDB can roll back patches applied on both Grid home and Database home.

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.