Which two choices are true for Autonomous Database Workloads (ADW)?

When an Autonomous Database workload (ADW) is stopped, there are specific billing implications regarding compute and storage that are important to understand. The correct choice indicates that billing for compute resources stops when the ADW is stopped. This means that while the database is not in use and is effectively paused, the costs associated with the compute capacity are halted, which is beneficial for users as it allows them to save on costs when the database is not actively running.

However, it's important to note that the storage component is distinct from the compute resources. In the architecture of Autonomous Database, while compute costs cease during the stopped state, the storage costs persist. This is because the data stored remains available for when the database is restarted. Thus, while users will save on compute charges, they will continue to incur charges for the storage of their data.

Understanding this billing model is crucial for effective cost management in the Oracle Cloud Infrastructure, as it allows architects to plan and forecast expenditure associated with their database workloads. This distinction also encourages users to consider their usage patterns to make informed decisions about when to start or stop their Autonomous Database workloads.