Viewing the maintenance history of Autonomous Exadata Infrastructure (AEI) requires navigating the

OCI console correctly. The correct path is:

Under Solutions and Platforms then Platform Services then Autonomous Exadata (C): In the OCI

console, AEI is categorized under “Solutions and Platforms” (a section for integrated services), then

“Platform Services” (covering cloud platform offerings), and finally “Autonomous Exadata.” Here, you

select your AEI instance (e.g., by name or OCID), and the details page displays a “Maintenance

History” section listing past events (e.g., patching dates, durations, and statuses like “Completed on

2025-03-01”). For example, a quarterly RU applied on January 15 might show “Patch Applied: RU

23.1” with start/end times. This path reflects AEI’s role as a dedicated platform supporting

Autonomous Container Databases (ACDs) and Autonomous Databases (ADBs).

The incorrect options are:

Under Core Infrastructure then Compute then Autonomous Exadata (A): “Core Infrastructure” >

“Compute” is for virtual machines or bare metal hosts, not Exadata infrastructure. AEI isn’t a

compute instance; it’s a database platform.

Under Database then Autonomous Transaction Processing then Autonomous Exadata (B): “Database”

> “Autonomous Transaction Processing” focuses on ATP instances, not the underlying Exadata

infrastructure. AEI maintenance is separate from specific ADB types.

Under Core Infrastructure then Autonomous Exadata (D): “Core Infrastructure” doesn’t directly list

AEI; it’s too broad and lacks the “Platform Services” context needed for Exadata-specific

management.

This navigation ensures you access AEI-specific maintenance details efficiently.

Reference: Oracle Cloud Infrastructure Documentation - Managing Autonomous Exadata

Infrastructure

Oracle Data Integrator (ODI) Web Edition integrates with Autonomous Database:

Correct Answer (B): “ODI Web Edition can be installed from Oracle Cloud Infrastructure (OCI)

Marketplace” is true. It’s offered as a Marketplace image for easy deployment on OCI compute

instances.

Correct Answer (D): “All capabilities of ODI Classic are available with ODI Web Edition” is correct; the

web version retains full functionality for data integration tasks.

Incorrect Options:

A: ODI Web Edition is not limited to Oracle Linux; it runs on various platforms supported by OCI.

C: The Data Transforms Card in Database Actions uses a simplified UI, not full ODI Web Edition

access.

This enhances data integration flexibility in the cloud.

Reference: ODI on OCI Marketplace

SQL Developer Web in Autonomous Database relies on Oracle REST Data Services (ORDS) for access.

The correct package is:

ORDS_ADMIN.ENABLE_SCHEMA (B): To allow a non-admin user (e.g., ANALYST1) to use SQL

Developer Web, the ADMIN user executes ORDS_ADMIN.ENABLE_SCHEMA to enable the schema for

ORDS access. This procedure activates the schema for RESTful services, granting privileges like

CONNECT and SELECT implicitly for web-based SQL execution. Example:

BEGIN

ORDS_ADMIN.ENABLE_SCHEMA(p_schema => 'ANALYST1');

END;

After this, the user accesses SQL Developer Web via a URL (e.g., https:///ords/analyst1/_sdw), logging in with their database credentials. This is necessary because SQL

Developer Web runs on ORDS, and only enabled schemas can interact with it. For instance, an

analyst might query SELECT * FROM sales in the web interface post-enablement, without needing

full admin rights.

The incorrect options are:

ORDS_ADMIN.GRANT_SCHEMA (A): No such procedure exists in ORDS_ADMIN. Granting is handled

via database roles/privileges (e.g., GRANT CONNECT), not a specific ORDS grant function.

ORDS_PRIV.ENABLE_SCHEMA (C): There’s no ORDS_PRIV package; this might confuse with

ORDS_ADMIN. The correct package is ORDS_ADMIN for schema enablement.

SQLDEV_ADMIN.GRANT_SCHEMA (D): No SQLDEV_ADMIN package exists. SQL Developer Web

access is managed through ORDS, not a separate SQL Developer-specific package.

ORDS_ADMIN.ENABLE_SCHEMA is the standard, secure way to enable non-admin access to this tool

in ADB.

Reference: Oracle Cloud Infrastructure Documentation - SQL Developer Web Setup

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.

Reference: Oracle Autonomous Database Dedicated Documentation - Provisioning

Provisioning an Autonomous Database without using the OCI Console is possible through

programmatic methods. The correct answer is:

Using the cloud infrastructure command line interface or REST API calls (D): The Oracle Cloud

Infrastructure Command Line Interface (OCI CLI) and REST APIs allow users to provision and manage

Autonomous Database resources programmatically. This method is ideal for automation or when GUI

access is not preferred. For example, the OCI CLI command oci db autonomous-database create can

be used to provision a database by specifying parameters like compartment ID, database name, and

workload type. Similarly, a REST API POST request to /autonomousDatabases achieves the same

result.

The incorrect options are:

Using the DBCA on the database server (A): The Database Configuration Assistant (DBCA) is a tool for

on-premises Oracle databases, not for cloud-based Autonomous Databases, which are fully managed

by Oracle.

Connecting to the cloud infrastructure console using the SSH wallet (B): SSH wallets are for secure

shell access to compute instances, not for provisioning databases or interacting with the OCI

Console.

It cannot be done (C): This is false, as programmatic provisioning via CLI or API is explicitly supported.

This capability enhances automation and integration into DevOps workflows.

Reference: Oracle Cloud Infrastructure Documentation - CLI for Autonomous Database and REST API

for Autonomous Database

Data Insights is a feature in Autonomous Database that helps users understand their data. The false

statement is:

Data Insights are automatically generated by various analytic functions built into the database (C):

This is incorrect. Data Insights are not solely the result of automatic execution of built-in analytic

functions (e.g., AVG, SUM, or RANK). Instead, they are generated through a combination of user-

initiated analysis and Oracle’s machine learning-driven capabilities within the Data Insights

dashboard (part of Database Actions or OCI console). Users select datasets or tables, and the system

applies algorithms to identify patterns (e.g., trends in sales) or anomalies (e.g., outlier transactions),

but this process isn’t just a passive outcome of pre-existing database functions—it’s an active,

curated feature requiring configuration. For example, a user might explore a SALES table, and Data

Insights highlights a spike in Q4 sales, but this requires user input to define scope, not just automatic

function output.

The true statements are:

Data Insights display information about patterns and anomalies in the data of entities in your Oracle

Autonomous Database (A): True. The feature visualizes trends (e.g., seasonal sales increases) and

outliers (e.g., unexpected data drops) in tables or views, helping users spot significant data

behaviors. For instance, it might show a bar chart of monthly revenue with an anomaly flagged for a

sudden dip.

Data Insights provides a wide range of graphical data presentation capabilities (B): True. It offers

visualizations like bar charts, line graphs, and scatter plots, customizable to represent data insights

effectively. E.g., a line graph might track customer sign-ups over time, with options to adjust axes or

filters.

The results of the Insight analysis appear as a series of bar charts in the Data Insights dashboard (D):

True, partially. While bar charts are a common default (e.g., comparing sales by region), the

dashboard supports multiple chart types, but the statement’s focus on bar charts aligns with typical

output for simple insights.

The misconception in C overlooks the interactive, ML-assisted nature of Data Insights, distinguishing

it from passive function-based analytics.

Reference: Oracle Cloud Infrastructure Documentation - Data Insights in Database Actions

Creating an Autonomous Database (ADB) via OCI’s REST API involves a specific endpoint. The correct

command is:

POST /20160918/autonomousDatabases (D): This is the official REST API endpoint to create an ADB

instance. The POST request to /20160918/autonomousDatabases (versioned at API 20160918)

submits a JSON payload defining the database (e.g., compartment, name, workload type). Example:

curl -X POST "https://database.us-ashburn-1.oraclecloud.com/20160918/autonomousDatabases" \

-H "Authorization: Bearer " \

-H "Content-Type: application/json" \

-d '{

"compartmentId": "ocid1.compartment.oc1..example",

"dbName": "MYADB",

"cpuCoreCount": 1,

"dataStorageSizeInTBs": 1,

"dbWorkload": "OLTP",

"adminPassword": "Secure#123"

}'

This creates an ATP instance named MYADB with 1 OCPU and 1 TB storage. The response includes an

OCID (e.g., ocid1.autonomousdatabase.oc1..example), and provisioning starts asynchronously,

visible in the OCI console as “PROVISIONING.” The endpoint’s plural form (autonomousDatabases)

reflects the resource collection, consistent with OCI API conventions.

The incorrect options are:

POST /20160918/createADB (A): No such endpoint exists. OCI APIs use resource-based paths (e.g.,

/autonomousDatabases), not action-specific ones like createADB.

POST /20160918/createautonomousDatabases (B): Incorrect syntax—APIs don’t prepend “create” to

resource paths, and “autonomousDatabases” is lowercase here, matching the real endpoint.

POST /20160918/createDatabases (C): Too generic; it doesn’t specify “autonomous” databases, and

no such endpoint exists for ADB creation.

This REST command is a programmatic alternative to console-based provisioning, ideal for

automation.

Reference: Oracle Cloud Infrastructure API Documentation - CreateAutonomousDatabase

A refreshable clone in Autonomous Database is a read-only copy of a source database that syncs

periodically, but it has a refresh time limit (typically 7 days). Once this limit is exceeded, specific

actions are available. The two correct options are:

You can disconnect from the source to make the database a read/write database (B): After the

refresh time limit passes, the clone can no longer sync with the source. You can “disconnect” it (via

the OCI console or API, e.g., oci db autonomous-database update --is-refreshable-clone false),

converting it into an independent, read/write Autonomous Database. This requires a new license and

incurs full costs, but it allows modifications (e.g., INSERT or UPDATE) that were blocked in read-only

mode. For example, a test clone might be disconnected to become a production instance after

testing.

You can use the instance as a read-only database (C): Even after the refresh limit, the clone remains

functional as a read-only database, retaining its last refreshed state. You can query it (e.g., SELECT *

FROM sales) for analysis or reporting without further refreshes, though it won’t reflect source

updates. This is useful if ongoing read-only access suffices without needing write capabilities.

The incorrect options are:

You can manually refresh the clone (A): False. Once the refresh time limit (e.g., 7 days) is exceeded,

manual refreshes are not possible. The clone’s refresh capability expires, and it can’t sync again

unless recreated. This is a fixed constraint to manage resource usage in ADB.

You can extend the refresh time limit (D): False. The refresh period (set during clone creation, max 7

days) cannot be extended after provisioning. You’d need to create a new clone with a longer limit if

needed, but post-expiry, no extension is allowed.

These options provide flexibility post-expiry, balancing read-only continuity and full database

conversion.

Reference: Oracle Cloud Infrastructure Documentation - Refreshable Clones

Third-party software can connect to an Autonomous Database using standard Oracle connectivity

options. The correct answer is:

Any protocol supported by Oracle Net Services (B): Autonomous Database leverages Oracle Net

Services (also known as SQL*Net) for connectivity, supporting protocols like TCP/IP with TLS for

secure communication. This allows a wide range of third-party tools (e.g., SQL Developer, Tableau, or

custom applications) to connect using established Oracle networking standards.

The incorrect options are:

New ADB-specific protocols (A): There are no proprietary, ADB-specific protocols; it uses Oracle’s

existing Net Services framework.

SQL*NET only (C): While SQLNet is part of Oracle Net Services, the broader term “Oracle Net

Services” encompasses all supported protocols, not just SQLNet.

JDBC only (D): JDBC is a specific Java-based API for database connectivity, not a protocol, and it’s just

one of many ways to connect via Oracle Net Services.

This flexibility ensures compatibility with diverse client applications.

Reference: Oracle Cloud Infrastructure Documentation - Connecting to Autonomous Database

Compartment quotas in OCI control resource usage within compartments. The incorrect statement

is:

Compartment quotas are set by Oracle (A): This is false. Compartment quotas are not set by Oracle;

they are defined by OCI administrators using quota policies in the Identity and Access Management

(IAM) system. Admins write policies (e.g., set database quota to 2 autonomous-databases in

tenancy) to limit resources like Autonomous Databases per compartment, giving customers full

control over resource allocation. Oracle provides the framework, but the specific quotas are user-

defined, not Oracle-imposed.

The correct statements are:

Along with compartment budgets, compartment quotas create a powerful toolset to manage your

spending (B): True. Quotas limit resource creation (e.g., max 5 ADBs), while budgets track spending

(e.g., $1000/month), together offering comprehensive cost management. For example, a quota

might cap ADB instances, and a budget alerts when costs approach a threshold.

There are three types of quota policy statements which are set, unset, and zero (C): True. SET assigns

a quota (e.g., set compute quota to 10 instances), UNSET removes it, and ZERO sets it to none,

effectively blocking resource creation. These verbs provide flexible quota management.

Compartment quotas use policies that allow allocation of resources with a high level of flexibility (D):

True. Policies are written in OCI’s IAM syntax, allowing granular control (e.g., set database quota to 1

autonomous-database where target.compartment.id = 'ocid1.compartment...'), tailored to specific

compartments or resources.

This customer-driven approach distinguishes quotas from Oracle-managed limits.

Reference: Oracle Cloud Infrastructure Documentation - Managing Quotas