1Z0-1093-25 practice question 5 of 15

While operating a MySQL HeatWave cluster, you need to resize the HeatWave cluster to accommodate an increased workload. Which method is the most efficient and recommended way to scale the HeatWave cluster?

Full set: 99 questions
Answer options
A: Manually altering the innodb_buffer_pool_size and restarting the MySQL server.
B: Using the OCI CLI or Console to adjust the HeatWave cluster's shape and node count. Correct answer
C: Modifying the underlying VM shapes of the MySQL Database System.
D: Recreating the HeatWave cluster with the desired size.
E: Performing a manual data export and import into a new, larger MySQL Database System.
Correct Answer:
B. Using the OCI CLI or Console to adjust the HeatWave cluster's shape and node count.
Explanation

The most efficient and recommended method to resize a MySQL HeatWave cluster is by using the Oracle Cloud Infrastructure (OCI) management interfaces, such as the OCI Console or Command Line Interface (CLI). This allows an administrator to scale the cluster out by increasing the number of nodes or scale it in by decreasing the number of nodes. This operation is managed by the service, which automatically handles the rebalancing of data across the new set of nodes, ensuring minimal disruption and optimal performance for the increased workload. This is significantly more efficient than recreating the cluster or the entire database system.

Why Incorrect

A. Manually altering the innodbbufferpoolsize affects the primary MySQL DB System's performance, not the scale of the separate HeatWave analytics cluster.
C. Modifying the underlying VM shapes of the MySQL Database System scales the primary OLTP node, not the attached HeatWave cluster used for analytics.
D. Recreating the HeatWave cluster is a valid but highly inefficient method, as it requires a complete reload of all data from the MySQL DB System.
E. Performing a manual data export and import is a full database migration strategy, not a standard scaling operation for an existing HeatWave cluster.

References

1. Oracle Cloud Infrastructure Documentation - MySQL HeatWave - Scaling a HeatWave Cluster: "You can scale a HeatWave cluster out by increasing the number of HeatWave nodes, or scale it in by decreasing the number of nodes. You can scale a HeatWave cluster from the Console, CLI, or your own code using one of the SDKs. When you scale out a HeatWave cluster, the data is automatically rebalanced across the new set of nodes." (Section: MySQL HeatWave, Page: Scaling a HeatWave Cluster)

2. Oracle Cloud Infrastructure Documentation - MySQL HeatWave - Editing a DB System: This section details how to modify a DB System's configuration, including enabling, disabling, or changing the HeatWave cluster attached to it. It states, "On the DB system details page, under Resources, click HeatWave. Click Actions, and then click Scale Out/In." This confirms the action is performed through the OCI Console interface. (Section: MySQL HeatWave, Page: Editing a DB System)

Scroll to Top