Full Detailed In-Depth Explanation:

When provisioning an Autonomous Database (ADB) on dedicated infrastructure, the placement within the infrastructure is critical:

A. Listener endpoint: Incorrect. This is for connectivity, not placement.

B. Client Credentials wallet: Incorrect. This is for secure connections, not determining location.

C. The container database in which the Autonomous instance should run: Correct. On dedicated infrastructure, an Autonomous Container Database (ACD) hosts multiple ADB instances. Selecting the ACD during provisioning determines where the ADB resides, affecting resource allocation and isolation.

D. The compartment: Incorrect. Compartments organize resources in OCI, but multiple ACDs can exist within a compartment, so this doesn’t pinpoint the exact location.

Choosing the ACD is a key provisioning step for dedicated deployments.

Autonomous Database on Dedicated Infrastructure offers more control than shared infrastructure. The two correct statements are:

You, as the customer, are responsible for all patching operations (A): In dedicated infrastructure, customers manage patching for Autonomous Container Databases (ACDs) and Autonomous Databases (ADBs), unlike shared infrastructure where Oracle handles it. You choose when to apply Release Updates (RUs) or skip them (up to two quarters), using the OCI console or API (e.g., oci db autonomous-container-database update). For example, you might schedule an RU for an ACD on a Saturday night, downloading the patch from Oracle and applying it manually to minimize downtime. This responsibility comes with the dedicated model’s flexibility.

You can set maintenance windows for each individual Autonomous Container Database (C): Dedicated infrastructure allows setting specific maintenance windows per ACD, not just at the Exadata Infrastructure level. In the OCI console, under each ACD’s details, you configure a preferred time (e.g., “Sundays, 02:00-04:00 UTC”), ensuring patches or upgrades align with your schedule. For instance, ACD1 might patch Sundays, while ACD2 patches Tuesdays, tailoring downtime to different workloads.

The incorrect options are:

You can set maintenance windows for an Autonomous Exadata Infrastructure (B): Maintenance windows are set at the ACD level, not the broader Autonomous Exadata Infrastructure (AEI) level. AEI maintenance (e.g., hardware updates) is Oracle-managed, with notification but no customer scheduling.

Patching occurs on the first Sunday of each quarter (D): There’s no fixed schedule like “first Sunday.” In dedicated mode, you control patching timing within a quarter, notified by Oracle of available RUs, unlike shared infrastructure’s Oracle-driven schedule.

These statements highlight dedicated infrastructure’s customer-driven management.

Full Detailed In-Depth Explanation:

In Autonomous Database on Shared Infrastructure, tablespace quotas are managed using standard SQL commands, as administrative packages like DBMS_CLOUD_ADMIN are restricted in this environment. The correct method is:

ALTER USER MTHEO QUOTA UNLIMITED ON TABLESPACE DATA: This command directly modifies the user’s quota on the DATA tablespace, which is the default tablespace in Autonomous Database. “UNLIMITED” removes any storage restrictions.

Analysis of options:

A: Incorrect. DBMS_CLOUD_ADMIN is used in dedicated infrastructure for advanced administrative tasks, not shared infrastructure for quota changes.

B: Correct. This is the standard SQL syntax supported in shared infrastructure.

C: Incorrect. ALTER TABLESPACE modifies tablespace properties, not user quotas, and isn’t applicable here.

D: Incorrect. ALTER DATABASE syntax is invalid for user quotas; it’s for database-wide settings.

Oracle Autonomous Database is designed to run on specific infrastructure optimized for its managed capabilities:

Correct Answer (B) : Dedicated Exadata Infrastructure provides a fully dedicated Exadata system for a single tenant, offering maximum isolation, performance, and customization (e.g., maintenance scheduling).

Correct Answer (D) : Shared Exadata Infrastructure allows multiple Autonomous Database instances to share Exadata resources, providing a cost-effective option for smaller workloads while retaining automation benefits.

Incorrect Options :

A : Virtual Machines (VMs) on OCI are not a supported deployment platform for Autonomous Database. It requires Exadata hardware for its self-managing features, unlike traditional OCI VMs used for manual database setups.