Which two statements are true regarding cloning a block volume?

When cloning a block volume, it is indeed possible to change the block volume performance during the cloning process. This allows users to optimize the performance settings of the new cloned volume according to their specific needs or workload requirements. Adjusting performance parameters facilitates enhanced flexibility when managing resources in the cloud environment, thereby contributing to better tailoring of storage solutions for different applications.

The remaining options do not accurately reflect the capabilities around block volume cloning. For instance, while cloning provides various functionalities, it does not support cloning across regions, meaning a cloned volume must reside within the same region as the original. Changing the block volume size during the cloning process is also not permissible; the size must be the same as the original block volume when a clone is created. Additionally, block volume encryption cannot be skipped during the cloning process—the encryption settings of the original volume are maintained in the clone, ensuring that security measures remain intact.

This understanding is crucial for effectively managing block volumes in Oracle Cloud Infrastructure, ensuring that users are aware of the capabilities and limitations when working with volume cloning.