Nutanix NCP-DB Practice Questions

Explanation:
The administrator should perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, to accomplish the task of patching a MongoDB server cluster within an NDB environment. A rolling upgrade is a method of applying patches or updates to a cluster without downtime or interruption of service.
The administrator can use the NDB patching feature to perform a rolling upgrade on a MongoDB server cluster, which consists of a primary member and one or more secondary members that form a replica set. The NDB patching feature allows the administrator to select the software profile version, the database parameters profile, and the network profile for the patching operation. The NDB patching feature also automates the steps of the rolling upgrade, such as:
Step 1: The administrator initiates the patching operation on the NDB instance, and selects the MongoDB server cluster to be patched.
Step 2: The NDB instance verifies the prerequisites and compatibility of the patching operation, and creates a pre-patch snapshot of the MongoDB server cluster.
Step 3: The NDB instance applies the patch to the first secondary member of the MongoDB server cluster, and waits for the patching to complete successfully.
Step 4: The NDB instance verifies the status and functionality of the patched secondary member, and repeats the patching process for the remaining secondary members of the MongoDB server cluster, one at a time.
Step 5: The NDB instance performs a failover of the primary member to one of the patched secondary members, and applies the patch to the original primary member.
Step 6: The NDB instance verifies the status and functionality of the patched primary member, and performs a failback of the primary member to the original primary member, if desired.
Step 7: The NDB instance creates a post-patch snapshot of the MongoDB server cluster, and completes the patching operation.
Performing a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, is the recommended and best practice method of patching a MongoDB server cluster within an NDB environment, as it ensures the high availability, consistency, and performance of the MongoDB server cluster and the databases.
Performing a rolling upgrade, applying the patch to the primary member first, followed by the secondary members, is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to the primary member first would disrupt the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to restore the MongoDB server cluster to a functional state.
Applying the patch to all nodes at once is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to all nodes at once would require shutting down the entire MongoDB server cluster, and would expose the MongoDB server cluster and the databases to potential errors, failures, and corruption during the patching process.
Disabling the replica set while patching is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Disabling the replica set while patching would break the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to re-enable the replica set and restore the MongoDB server cluster to a functional state.

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.

Explanation: Nutanix Era supports a variety of database engines, including Oracle, PostgreSQL, MySQL, and Microsoft SQL Server1. However, when it comes to rolling back a patch using the Command Line Interface (CLI), this feature is specifically supported for the Oracle database engine1. This allows for efficient validation of critical database updates and simplifies database rollback1. Please note that while Era does provide support for other database engines, the ability to rollback a patch using CLI is currently specific to Oracle1.

Explanation:
There are two ways to upgrade an NDB Server: one-click upgrade and offline upgrade. One-click upgrade is the recommended method, as it automatically downloads and installs the latest NDB software version from the Nutanix portal. Offline upgrade is an alternative method, which requires you to manually download the NDB software bundle and upload it to the NDB Server VM. Both methods require you to have a valid Nutanix account and an internet connection.

Explanation:
The log frequency in the Era IJI for log catchup operation can be configured to as low as 5 minutes. This allows the system to capture changes to the database at a high frequency, enabling more precise point-in-time recovery options. However, it’s important to note that a higher frequency of log catchup operations can lead to increased system load. Therefore, the optimal frequency may vary depending on the specific requirements and capabilities of your system12. Please refer to the Nutanix Database Automation (NCP-DB) Learning documents for more detailed information.

Explanation: In the context of Nutanix Database Automation (NCP-DB), when there are insufficient resources on a development cluster, the administrator can adjust the Compute and Database Parameters profiles to make the copy fit within the available resources1. The Compute profile includes settings related to CPU and memory resources, which can be adjusted to fit within the available resources. The Database Parameters profile includes settings that control the behavior and resource usage of the database, which can also be adjusted to optimize resource usage1.