To whom, and in which order, are dedicated Exadata Infrastructure resources provisioned?

Provisioning dedicated Exadata Infrastructure resources for Autonomous Database follows a specific hierarchical order:

Fleet Administrator, Autonomous Exadata Infrastructure -> Autonomous Container DB -> Database Administrator -> Autonomous DB (A):

Fleet Administrator provisions Autonomous Exadata Infrastructure:The Fleet Administrator, responsible for infrastructure management, first sets up the Autonomous Exadata Infrastructure (AEI), which includes the physical Exadata hardware and networking configuration.

Fleet Administrator provisions Autonomous Container DB (ACD):Within the AEI, the Fleet Administrator creates the ACD, a container that hosts multiple Autonomous Databases.

Database Administrator provisions Autonomous DB:Finally, the Database Administrator (DBA) provisions individual Autonomous Databases within the ACD, configuring them for specific workloads (e.g., ATP or ADW).

The incorrect options are:

B:The Database Administrator cannot provision the ACD before the AEI is set up by the Fleet Administrator.

C and D:The Database Administrator does not provision the AEI or ACD; these are infrastructure-level tasks handled by the Fleet Administrator.

This order ensures proper separation of infrastructure and database management responsibilities.