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.

Restricting access to an Autonomous Database to specific IPs involves network security controls. The correct answer is:
Access Control List (C): In Autonomous Database, an Access Control List (ACL) defines which IP addresses or CIDR blocks (e.g., 192.168.1.0/24) can connect to the database. You configure this via the OCI console under the ADB’s “Access Control List” settings, adding rules like “Allow TCP from 10.0.0.0/16 on port 1522.” This applies to public endpoints (shared infrastructure) or private endpoints with additional network rules, ensuring only authorized IPs can initiate connections. For example, a company might restrict access to its office VPN range, blocking all other traffic. ACLs work at the database level, complementing VCN security.
The incorrect options are:
Security List (A): Security Lists operate at the VCN subnet level, controlling traffic to all resources in the subnet (e.g., ingress TCP 1522 to an ADB subnet). While useful, they’re broader than ADB-specific ACLs, which target the database instance directly, making ACLs the precise answer here.
IP Vault (B): There’s no “IP Vault” in OCI. This might confuse OCI Vault (for secrets), but it doesn’t manage IP access.
IPSec List (D): IPSec secures traffic via VPNs, not IP allowlisting for database access. It’s unrelated to ADB connectivity restrictions.
ACLs provide a database-specific, user-friendly way to enforce IP-based access control.

SSH keys in OCI are used for secure access, but their role in API calls needs clarification. The correct answer is:
Navigate to Identity, select Users panel on the console and select "Add Public Key" (D): This is the correct process, but with a caveat—it’s about API authentication, not SSH for API calls per se. In OCI, API calls are authenticated using API keys (RSA key pairs), not SSH keys directly. To enable API access for a user, you generate a public/private key pair (e.g., using openssl), then add the public key in the OCI console:
Go to “Identity & Security” > “Users.” Select the user (e.g., john.doe).
Under “API Keys,” click “Add API Key.”
Upload the public key (e.g., ~/.oci/oci_api_key_public.pem).
This associates the key with the user, allowing API calls (e.g., oci db autonomous-database list) authenticated via the private key and config file (e.g., ~/.oci/config). The question’s phrasing (“SSH key”) likely misuses terminology, intending “API key,” as SSH keys are for compute instance access, not APIs. For example, a user might add a key to call the ADB API, securing requests with a signature.
The incorrect options are:
On the Autonomous Database Console (A): The ADB console manages database-specific settings (e.g., wallets), not user API keys, which are handled at the tenancy level under Identity.
SSH keys are not required in Oracle Cloud Infrastructure (B): False in general—SSH keys are needed for compute instances—but misleading here, as API calls use API keys, not SSH keys. Authentication (e.g., via tokens or keys) is required for APIs.
SSH keys cannot be added from console. They have to be added using REST APIs only (C): False. The console supports adding API keys under the Users panel; REST APIs (e.g., CreateApiKey) are an alternative, not the only method.
The correct path reflects OCI’s user management for API access, despite the SSH terminology confusion.

Private endpoints enhance security for Autonomous Database:
Correct Answer (A): “A Network Security Group is required within your Virtual Cloud Network before you can provision a shared Autonomous Database to use private endpoints” is true. An NSG is mandatory to define ingress/egress rules for the private subnet hosting the endpoint.
Correct Answer (C): “Private endpoints can be configured when you clone a shared Autonomous Database that was initially created with public endpoints” is true. Cloning allows switching to a private endpoint configuration.
Incorrect Options:
B: Private endpoints are inaccessible from the public internet, even with ACLs; that’s their purpose.
D: Always Free tier doesn’t support private endpoints; it’s limited to public access.
This ensures isolated, secure connectivity.

Oracle Database provides several techniques to optimize data access from Object Storage, particularly in the context of Autonomous Database, leveraging external tables and advanced storage formats. The question asks for four correct methods, and based on Oracle documentation, the following are the most applicable:
Correct Answer (A): Scan avoidance using partitioned external tables
Partitioned external tables allow Oracle Database to skip irrelevant partitions when querying data stored in Object Storage. By organizing data into partitions (e.g., by date or region), the database engine can prune partitions that don’t match the query predicates, significantly reducing the amount of data scanned and improving performance. This is a well-documented optimization for external data access in Oracle Database and Autonomous Database environments.
Correct Answer (D): Scan avoidance using columnar pruning for columnar stores like parquet and orc Columnar pruning is a technique where only the required columns are read from columnar file formats such as Parquet or ORC stored in Object Storage. These formats store data column-wise, enabling the database to avoid scanning entire rows or irrelevant columns, which is particularly efficient for analytical queries common in Autonomous Data Warehouse (ADW). This is a standard optimization supported by Oracle’s external table framework when accessing Object Storage.
Correct Answer (E): Optimized data archive using hybrid partitioned tables Hybrid partitioned tables combine local database partitions with external partitions stored in Object Storage. This allows older, less frequently accessed data to be archived efficiently in the cloud while remaining queryable alongside active data in the database. The database optimizes access by seamlessly integrating these partitions, reducing costs and improving archival efficiency. This feature is explicitly supported in Oracle Database and enhanced in Autonomous Database for data lifecycle management.
Correct Answer (F): Optimized data archive using partitioned external tables Similar to hybrid partitioned tables, using partitioned external tables alone optimizes data archiving by storing historical data in Object Storage with partitioning (e.g., by year). This method enables efficient querying of archived data by pruning unneeded partitions, offering a cost-effective and scalable archival solution. It’s a distinct approach from hybrid tables, focusing solely on external storage, and is widely used in Oracle environments.
Incorrect Options:
B . Scan avoidance using columnar pruning for .csv files
CSV files are row-based, not columnar, and lack the internal structure of formats like Parquet or ORC. While Oracle can read CSVs from Object Storage via external tables, columnar pruning is not applicable because CSVs don’t support column-wise storage or metadata for pruning. This makes this option incorrect as a specific optimization technique, though basic predicate pushdown might still reduce scanning to some extent.
C . Scan avoidance using block skipping when reading parquet and orc files Block skipping (or row group skipping) is a feature in some database systems where metadata in Parquet or ORC files allows skipping entire blocks of data based on query filters. While Oracle supports Parquet and ORC through external tables and can leverage their columnar nature (via pruning), “block skipping” is not explicitly highlighted as a primary optimization in Oracle’s documentation for Autonomous Database. It’s more commonly associated with systems like Apache Spark or Hive. Oracle’s focus is on columnar pruning and partitioning, making this option less accurate in this context.
Why Four Answers?
The question specifies “four ways,” and while six options are provided, A, D, E, and F are the most directly supported and documented methods in Oracle Autonomous Database for optimizing Object Storage access. Options B and C, while conceptually related to data access optimizations, are either inapplicable (CSV lacks columnar structure) or not explicitly emphasized (block skipping) in Oracle’s feature set for this purpose.
This selection aligns with Oracle’s focus on partitioning and columnar formats for efficient cloud data access, ensuring both performance and archival optimization.
External Tables and Object Storage
Hybrid Partitioned Tables
Autonomous Database Data Loading