Nutanix NCP-DB Practice Questions

D.   Schedule

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.

B.   Era UI

Explanation:
An administrator can configure a custom SSL certificate for Era through the Era User Interface (UI)1. This can be done by logging into the Nutanix Console and selecting SSL Certificates from the drop-down list inside the gear icon23. In the SSL Certificate dialog box, the administrator can click Replace Certificate, then select the Import Key and Certificate radio button23. This process ensures secure communication within the Nutanix Era environment4.

C.   1. Download the required patch from MyOracle Support.
2. Apply the patch to the Oracle Hom€Grid Home on a cloned VM of the gold image using O PatchAuto.
3. Ensure success of patch application.

D.   1. Create new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era Gul.
2. Mark the original patch profile as hidden.

Explanation:
To create a software profile version for a newly-released Oracle ISc patch, an administrator should follow these steps:

• Download the required patch from MyOracle Support1. This is because Oracle patches are typically available from MyOracle Support, not Microsoft Support.
• Apply the patch to the Oracle Home/Grid Home on a cloned VM of the gold image using OPatchAuto1. OPatchAuto is a utility provided by Oracle that automates the process of applying patches to a database.
• Ensure success of patch application1. It’s important to verify that the patch has been applied successfully to avoid any issues down the line.
• Create a new software profile version from the original software profile using the cloned VM where OPatchAuto was run successfully using Era GUI1. This step is necessary to ensure that the new patch is included in the software profile.
• Mark the original patch profile as hidden1. This step is optional but can be useful for keeping the software profile clean and organized.

Please note that these answers are based on the information available as of my last update in 2021 and may need to be verified with the most recent Nutanix Database Automation (NCP-DB) documentation or resources.

D.   It is patched first and then becomes a secondary member.

According to the NDB documentation, the NDB patching process for MongoDB Server Cluster follows these steps1:

• NDB identifies the primary member of the MongoDB Server Cluster and patches it first.
• NDB triggers a failover to elect a new primary member from the remaining secondary members.
• NDB patches the former primary member, which becomes a secondary member after the failover.
• NDB patches the remaining secondary members one by one.
• NDB verifies the patching status and the cluster health.

This process ensures that the MongoDB Server Cluster always has a primary member available to handle write operations, while minimizing the downtime and the impact on the cluster performance.

B.   Japanese

Explanation:
The NDB user interface supports multiple languages, including English, Chinese, and Japanese. You can change the language preference in the NDB settings page. The NDB user interface does not support Korean, French, or German languages at this time.

C.   Critical, Warning Info

Explanation:
The Alerts dashboard in Nutanix displays alert messages with three severity levels: Critical, Warning, and Info1. These severity levels help users understand the importance and urgency of each alert, allowing them to prioritize their responses accordingly1.