Explanation
References:
Terraform configuration filescan use either of two formats: Terraform domain-specific language (HashiCorp Configuration Language format [HCL]), which is the recommended approach, or JSON format if the files need to be machine-readable.

Explanation
When Autonomous Databas instance is stopped,
CPU billing is halted based on full-hour cycles of usage
Billing for storage continues as long as the service instance exists.
and When AutonomousDatabase instance is started, the CPU billing is initiated

Explanation
References:https://docs.cloud.oracle.com/iaas/Content/Database/Tasks/managingDBsystem.htm

Explanation
If a bare metal DB system requires more compute node processing power, you can scale up (increase) the number of enabled CPU cores in the system without impacting the availability of that system but you can't increase the storage If the original DB system VM shapeuses a single node, running databases on the DB system nodes are sequentially stopped and then restarted on the new shape so not dynamic