Which two statements apply to the Autonomous Database service on Dedicated Infrastructure?

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 perACD, 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.