Final answer:
Stopping a Heatwave cluster will cease billing for processing resources, and data in memory will be removed. Stored data, however, will remain. Stopping the cluster does not automatically stop the connected MySQL DB system, which will continue to incur charges. Therefore, the correct answer options are B)
Step-by-step explanation:
If you have stopped the Heatwave cluster, it is important to understand the billing and operational effects of that action. The correct statements are that billing will stop for the HeatWave cluster, and data loaded in HeatWave cluster memory is typically removed, meaning that you no longer incur charges for compute resources used by the cluster. However, the underlying MySQL DB system and storage resources may still incur costs.
In regard to the preservation of data, the Heatwave cluster data on storage will remain intact despite the cessation of billing for the cluster's processing resources. This is because stopping the HeatWave cluster does not affect the stored data, which continues to reside on the connected MySQL DB system's storage.
As for the last part of the question, the Heatwave cluster stop action will not automatically stop the DB system; they are managed separately. Therefore, while the Compute part of HeatWave will stop, the DB system will continue to run and incur charges unless it is specifically stopped as well.