Creating an Autonomous Database offers specific deployment options. The two correct ones are:

APEX Service on Dedicated Infrastructure (A): This option provisions an Autonomous Database on

dedicated Exadata infrastructure with Oracle Application Express (APEX) pre-installed and optimized.

It’s ideal for APEX-based apps (e.g., custom web forms) requiring isolated resources. In the OCI

console, you select “Dedicated Infrastructure” and “APEX Service” as the workload type, specifying

OCPUs and storage. For example, a company might deploy an APEX app for internal reporting on a

dedicated ACD, ensuring performance isolation from other tenants.

Autonomous JSON Database on Shared Infrastructure (C): This creates a schema-less, JSON-centric

ADB on shared infrastructure, optimized for document storage (e.g., { "order_id": 123, "items": [...]

}). It’s provisioned via the OCI console under “Shared Infrastructure,” selecting “JSON Database” as

the workload type. For instance, a mobile app might use it to store user data, leveraging SQL/JSON

queries like SELECT JSON_VALUE(doc, '$.order_id'). It’s cost-effective and fully managed, sharing

Exadata resources.

The incorrect options are:

APEX Service on Shared Infrastructure (B): There’s no distinct “APEX Service” workload type on

shared infrastructure. APEX is available within ATP or ADW on shared infra, but it’s not a standalone

option—you’d provision ATP and enable APEX manually, not as a dedicated “APEX Service.”

Autonomous JSON Database on Dedicated Infrastructure (D): JSON Database is only offered on

shared infrastructure, not dedicated. Dedicated options include ATP, ADW, and APEX Service, but

JSON Database leverages shared resources for simplicity and cost.

These options cater to specific app development (APEX) and NoSQL (JSON) needs.

Reference: Oracle Cloud Infrastructure Documentation - Creating Autonomous Database