1z0-931-25 Oracle Autonomous Database Cloud 2025 Professional Questions and Answers

Migrating a PDB to Autonomous Database has limitations:

Correct Answer (B): “PDBs cannot be migrated to an Autonomous Database using plug, unplug, or clone” is true. Autonomous Database does not support direct plugging/unplugging of PDBs due to its managed architecture and differing storage/backup mechanisms.

Incorrect Options:

A: Unplugging into an XML file is valid for traditional PDBs, but Autonomous Database doesn’t accept this for migration.

C: Cloning via database link isn’t a standard method; it’s more aligned with replication tools like GoldenGate.

Full Detailed In-Depth Explanation:

Autonomous Transaction Processing (ATP) offers predefined service levels with varying concurrency and parallelism capabilities:

MEDIUM:Supports up to 50 concurrent statements per OCPU, with no parallelism by default. Unsuitable for the requirement.

TPURGENT:Supports up to 200 concurrent statements per OCPU and enables manual parallelism. This meets both requirements (concurrency ≥ 200 and parallelism), making it the correct choice.

LOW:Supports only 25 concurrent statements per OCPU, with no parallelism. Insufficient for the requirement.

TP:Supports 125 concurrent statements per OCPU, with no parallelism by default. Falls short of the 200 concurrency threshold.

TPURGENT is designed for high-concurrency, time-sensitive workloads, providing the necessary resources and flexibility for parallel query execution, aligning perfectly with the specified needs.

Fleet administrators managing dedicated Exadata infrastructure in Oracle Autonomous Database require broad permissions across all Autonomous Database resources, including those on dedicated infrastructure.

Correct Answer (B): The policy Allow group adb-admins to manage autonomous-database-family in tenancy grants comprehensive management rights over the entire Autonomous Database family, including dedicated Exadata infrastructure. The autonomous-database-family resource type encompasses all Autonomous Database resources (shared and dedicated) within the tenancy, making it suitable for fleet admins.

Incorrect Options:

A: Limits permissions to databases with the OLTP workload type (Autonomous Transaction Processing), excluding Data Warehouse (DW) or other types on dedicated infrastructure.

C: Restricts access to DW workload types only, omitting OLTP and other configurations.

Full Detailed In-Depth Explanation:

Autonomous Database on Dedicated Infrastructure comprises:

Autonomous Exadata Infrastructure:The hardware and software foundation.

Autonomous Container Database:Hosts multiple ADB instances.

Autonomous Database:The managed database instance.

Autonomous Backup:Automatic backups to OCI Object Storage.

Other options include roles (B, C) or general OCI resources (D), not core components of the service. A is the correct composition.

ADW and ATP are tailored for different workloads:

Correct Answer (C): “Only ADW uses columnar compression by default” is true. ADW employs Hybrid Columnar Compression (HCC) for analytics, optimizing storage and query performance, while ATP uses row-based storage for transactional workloads (though HCC can be enabled manually).

Incorrect Options:

A: Both ADW and ATP manage optimizer statistics automatically.

B: Autoscaling is supported by both ADW and ATP.

Securing an Autonomous Database after a user departs involves:

Correct Answer (C): “Rotate the instance wallet and share the new wallet with the remaining users” invalidates the old wallet’s credentials (e.g., certificates in ewallet.p12). Since the wallet secures client connections, rotating it ensures the departed user’s access is revoked, even if they retained a copy.

Incorrect Options:

A: Trusting the user is a security risk, not a solution.

B: Deleting the database user ID doesn’t address wallet-based access if credentials were shared externally.

Provisioning dedicated Exadata Infrastructure resources for Autonomous Database follows a strict hierarchical order, reflecting roles and dependencies. The correct sequence is:

The Fleet Administrator provisions the Autonomous Exadata Infrastructure and then the Autonomous Container DB and then, the Database Administrator provisions the Autonomous DB (A):

Fleet Administrator provisions Autonomous Exadata Infrastructure (AEI):The Fleet Admin, responsible for infrastructure management, starts by provisioning the AEI via the OCI console (e.g., “Create Autonomous Exadata Infrastructure”). This sets up the physical Exadata hardware, networking (e.g., VCN, subnets), and initial configuration (e.g., 2 racks, 4 nodes). For example, they might specify a compartment and region (e.g., us-ashburn-1), taking 1-2 hours for provisioning.

Fleet Administrator provisions Autonomous Container DB (ACD):Within the AEI, the Fleet Admin creates the ACD (e.g., “Create Autonomous Container Database”), a lightweight container hosting multiple ADBs. They set parameters like version (e.g., 19c) and maintenance windows (e.g., Sundays 02:00 UTC), ensuring the container is ready. This step might take 15-30 minutes.

Database Administrator provisions Autonomous DB (ADB):Finally, the DBA provisions individual ADBs within the ACD (e.g., “Create Autonomous Database”), choosing workload type (ATP/ADW), OCPUs (e.g., 4), and storage (e.g., 1 TB). For instance, they might create an ATP instance named PRODDB for a transactional app, completing setup in 5-10 minutes.

The incorrect options are:

B:The DBA can’t provision the ACD or ADB before the AEI exists, as the infrastructure is foundational. The Fleet Admin must act first.

C:The DBA doesn’t provision AEI—that’s an infrastructure task beyond their scope. The Fleet Admin handles hardware setup.

D:The DBA can’t provision the ACD; that’s a Fleet Admin task within the AEI. Roles are distinct: Fleet Admin for infra, DBA for databases.

This order ensures proper infrastructure setup before database creation, aligning with OCI’s role-based workflow.

Disabling Autonomous Data Guard affects the standby database:

Correct Answer (A): “The standby database is terminated” is true. When Data Guard is disabled via the OCI Console or API, the standby database is deleted, ending its role as a replica. This is a permanent action requiring re-enablement to recreate a standby.

Incorrect Options:

B: The standby doesn’t become read-write; it’s removed entirely.

C: It doesn’t remain read-only; termination stops all operations.

Keeping Autonomous Database tables synchronized with an on-premises data source involves loading and updating data from external locations. TheCloud Locations cardon the Data Loadpage is the correct method:

Correct Answer (B): The Cloud Locations card allows users to connect to Oracle Cloud Infrastructure (OCI) Object Storage buckets and load data into Autonomous Database tables. By regularly updating the data in Object Storage from the on-premises source (e.g., via scripts or tools), you can maintain synchronization using this feature. It supports automated data loading workflows when paired with appropriate processes.

Incorrect Options:

A: Oracle REST Data Services (ORDS) is used for building RESTful web services, not for direct data synchronization from on-premises sources to Autonomous Database tables.

C: The Link Data option enables linking to external database tables (e.g., via database links), but it doesn’t inherently synchronize data; it provides access rather than replication.

Restoring an Autonomous Database involves specific recovery options:

Correct Answer (A): “Selecting the backup from which restore needs to be done” allows you to choose a specific automatic backup (listed by timestamp) in the OCI Console to restore the database to that state.

Correct Answer (D): “Specifying the point in time (timestamp) to restore” enables Point-in-Time Recovery (PITR), restoring to any moment within the backup retention period (default 60 days), even between backups.

Incorrect Options:

B: There’s no “snapshot of the backup” option; backups are managed as full/incremental sets, not user-selectable snapshots.

ACLs control network access to Autonomous Database on Shared Infrastructure:

Correct Answer (B): “When you restore a database, the existing ACLs are not overwritten by the restore” is true. ACLs are part of the database’s network configuration, preserved during restore operations to maintain security settings.

Incorrect Options:

A: ACLs can include both IP addresses and VCN CIDR blocks simultaneously; they’re not mutually exclusive.

C: ACLs apply to public endpoints, not just private ones, to restrict access.

Migrating to Autonomous Database requires robust tools:

Correct Answer (B):Oracle Zero Downtime Migration (ZDM)minimizes downtime by synchronizing data and schema changes while the source remains online, ideal for critical systems.

Correct Answer (C):GoldenGateprovides real-time replication, enabling near-zero downtime migration by continuously syncing data to Autonomous Database.

Correct Answer (D):Data Pumpexports data and schema to dump files, which are then imported into Autonomous Database, suitable for offline migrations.

Incorrect Options:

A: SFTP with CSV files is not a comprehensive migration method; it lacks schema migration and automation for complex databases.

Loading data into Autonomous Database from object storage (e.g., OCI Object Storage) relies on a specific PL/SQL package. The correct answer is:

DBMS_CLOUD (D):The DBMS_CLOUD package is Oracle’s cloud-native tool for interacting with external data sources, including object storage, in Autonomous Database. It provides procedures like DBMS_CLOUD.COPY_DATA to load data from files (e.g., CSV, JSON, Parquet) stored in OCI Object Storage buckets into ADB tables. For example, to load a CSV file sales.csv from a bucket, you’d:

BEGIN

DBMS_CLOUD.CREATE_CREDENTIAL(credential_name => 'OBJ_STORE_CRED', username => 'oci_user', password => 'auth_token');

DBMS_CLOUD.COPY_DATA(table_name => 'SALES', credential_name => 'OBJ_STORE_CRED', file_uri_list => 'https://objectstorage.region.oraclecloud.com/n/namespace/b/bucket/o/sales.csv', format = > json_object('type' value 'csv'));

END;

This package handles authentication (via OCI credentials), file parsing, and data insertion, supporting formats like text, Avro, and ORC. It’s integral to ADB’s cloud integration, abstracting low-level operations and ensuring security (e.g., via IAM auth).

The incorrect options are:

DBMS_RPC (A):This package doesn’t exist in Oracle Database. It might be a typo or confusion with remote procedure calls, unrelated to data loading.

DBMS_LOAD (B):No such package exists. It might confuse with SQL*Loader, but that’s a separate utility, not a PL/SQL package, and isn’t used directly in ADB for object storage.

DBMS_MIGRATE (C):This doesn’t exist either. It might be a misnomer for DBMS_DATAPUMP (for Data Pump), but that’s for database migration, not object storage loading.

DBMS_CLOUD is purpose-built for ADB’s cloud-first architecture, making data ingestion seamless and efficient.

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

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

Correct Answer (D):Shared Exadata Infrastructureallows 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.

Manual backups in Autonomous Database are stored in OCI Object Storage, and the bucket name follows a strict convention. The correct name is:

BACKUP_DBSRV1 (D):For manual backups, ADB uses a bucket named BACKUP_ (all uppercase). Here, DBSRV1 is the database’s unique name (not the display name PRODDB), so the bucket must be BACKUP_DBSRV1. This bucket is automatically created by Oracle when you initiate a manual backup via the OCI console (e.g., “Create Manual Backup” button) or API (e.g., oci db autonomous-database backup create). For example, backing up DBSRV1 on March 18, 2025, stores files like backup_DBSRV1_20250318.dmp in this bucket. The unique name ensures uniqueness across the tenancy, as display names (e.g., PRODDB) might not be unique but the DB_UNIQUE_NAME is system-assigned and distinct.

The incorrect options are:

backup_proddb (A):This uses the display name proddb and lowercase, violating the BACKUP_ uppercase convention.

BACKUP_PRODDB (B):While uppercase, it uses the display name PRODDB, not the unique name DBSRV1, so it’s incorrect. Display names are for human readability, not system identification.

backup_dbsrv1 (C):This uses lowercase and lacks the exact BACKUP_ prefix format, failing Oracle’s naming rule.

The rigid naming ensures consistency and automation in ADB’s backup system.

When provisioning an Autonomous Database (ADB) instance, Oracle creates a default administrative user with extensive privileges. The correct user is:

ADMIN (B):The ADMIN user is automatically created during ADB provisioning and serves as the primary administrative account. It has full privileges to manage the database, including creating users, granting roles, and performing administrative tasks (e.g., scaling, backups). For example, after provisioning an ADB via the OCI console, you’d connect as ADMIN using the password you set, then run commands like: CREATE USER analyst1 IDENTIFIED BY "password"; GRANT CONNECT, RESOURCE TO analyst1;. This user is the entry point for initial configuration and ongoing management, authenticated via the client wallet for secure access (e.g., sqlplus admin/password@adb_high). The ADMIN user is distinct from traditional Oracle users like SYS because ADB’s managed nature limits direct system-level access, funneling administration through ADMIN.

The incorrect options are:

SYS (A):In traditional Oracle databases, SYS is the superuser with ultimate control (e.g., owning the data dictionary). In ADB, however, SYS exists but is locked and inaccessible to customers due to the fully managed environment—Oracle manages system-level operations, and users connect as ADMIN instead.

DWDEV (C):There’s no predefined DWDEV user in ADB. This might confuse with roles like DWROLE (for Data Warehouse developers), but no such user is created by default.

SCOTT (D):SCOTT is a sample user from older Oracle versions (with tables like EMP and DEPT), not created in ADB. It’s irrelevant in this modern, managed context.

The ADMIN user’s role ensures customers can manage ADB without needing Oracle’s intervention, aligning with its autonomous design.

Full Detailed In-Depth Explanation:

The Service Console in Autonomous Database is for database-level management:

A:False. Auto-scaling is managed via OCI console.

B:True. It allows monitoring and terminating runaway SQL statements.

C:False. Compartment moves are OCI console tasks.

D:False. Manual backups are initiated via OCI or SQL*Plus.

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.

Network Security Groups (NSGs) in OCI control network traffic to Autonomous Database instances:

Correct Answer (D): You can configure up to 5 NSGs for an Autonomous Database. This limit allows sufficient flexibility to define multiple security rules while maintaining manageability. NSGs can be assigned during provisioning or updated later via the OCI Console or API, restricting access to specific IP ranges or VCNs.

Incorrect Options:

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.

The Performance Hub in Autonomous Database provides real-time SQL monitoring with status indicators:

Correct Answer (A): Aclock iconin the Status column indicates “The SQL statement is queued.” This means the statement is waiting in a queue (e.g., due to resource limits or consumer group settings) and has not yet started executing.

Incorrect Options:

B: An executing statement typically shows a green progress bar or running icon, not a clock.

C: An error would display a red icon or error symbol, often with details in the UI.

Scaling OCPUs in an Autonomous Database triggers a specific status update. The correct answer is:

SCALING IN PROGRESS (D):When you increase (or decrease) the number of OCPUs,the database status in the OCI console changes to “SCALING IN PROGRESS.” This indicates that the system is actively adjusting the compute resources, a process that typically completes in a few minutes with no downtime for active transactions.

The incorrect options are:

UPSCALE IN PROGRESS (A):“Upscale” is not an official status term used by Oracle for this operation.

RESIZING IN PROGRESS (B):While “resizing” might intuitively fit, Oracle specifically uses “SCALING IN PROGRESS” for CPU adjustments.

UPLIFT IN PROGRESS (C):“Uplift” is not a recognized status in the context of Autonomous Database scaling.

This status reflects Oracle’s terminology for dynamic scaling.

Graph query languages, like Oracle’s Property Graph Query Language (PGQL), are designed for graph databases:

Correct Answer (D): “Ability to specify patterns” is a defining feature. Graph queries excel at defining and matching patterns (e.g., nodes and edges) to explore relationships, such as finding paths or subgraphs, critical for applications like social network analysis or fraud detection.

Incorrect Options:

A: Key-value queries are typical of NoSQL key-value stores, not graph databases.

B: While scripting may be possible in some contexts, it’s not a core feature of graph query languages.

Full Detailed In-Depth Explanation:

Oracle Autonomous Database offers two primary services: Autonomous Data Warehouse (ADW) and Autonomous Transaction Processing (ATP), each optimized for different workloads. SQL hints are directives embedded in SQL statements to influence the optimizer’s execution plan. However, their handling differs between the services:

Autonomous Data Warehouse (ADW):ADW is designed for analytical workloads and data warehousing, where query performance is critical. To ensure optimal execution, ADW’s optimizer relies heavily on its own statistics and algorithms, ignoring SQL hints by default. This behavior prevents user-provided hints from overriding the automated optimization strategies tailored for complex analytical queries.

Autonomous Transaction Processing (ATP):ATP targets transactional workloads (OLTP) and provides more flexibility. It does not ignore hints by default, allowing developers and DBAs to use hints to fine-tune query execution plans for specific transactional needs.

Thus, only ADW ignores hints by default, making option C the correct answer. Options A and B are incorrect because ATP does not share ADW’s default behavior, and option D incorrectly identifies ATP as the service that ignores hints.

Full Detailed In-Depth Explanation:

Connecting a marketplace OCI image (e.g., a pre-configured VM) to an Autonomous Database on Shared Infrastructure involves network and compatibility considerations. Let’s analyze each option:

A. The Autonomous Database must belong to a Network Security Group (NSG):False. NSGs enhance security but are optional. Connectivity can be achieved without them using security lists or other rules.

B. The marketplace OCI image can be used with an Always Free Autonomous Database account:True. The Always Free tier supports connectivity from OCI marketplace images, provided network configurations (e.g., VCN, subnet) allow it. This makes B the correct answer.

C. A Private Endpoint is required to connect to the Autonomous Database on Shared Exadata infrastructure:False. While private endpoints enhance security, public endpoints are also supported for shared infrastructure, making this optional.

D. The marketplace OCI image does not support connecting to an AutonomousDatabase on Shared Infrastructure:False. Marketplace images are designed to integrate with OCI services, including Autonomous Databases on shared infrastructure.

Option B stands out as it aligns with Oracle’s support for Always Free tiers, offering flexibility for users to leverage marketplace tools without additional cost.

Full Detailed In-Depth Explanation:

Service connections in Autonomous Database:

A. DBNAME_LOW:Optimized for high concurrency with minimal resources per query, ideal for many simultaneous queries.

B. DBNAME_MEDIUM:Balanced concurrency and performance.

C. DBNAME_HIGH:Prioritizes individual query performance, not concurrency.

D. DBNAME_CONCURRENT:Not a valid service name.

Provisioning dedicated Exadata Infrastructure resources for Autonomous Database follows a specific hierarchical order:

Fleet Administrator, Autonomous Exadata Infrastructure -> Autonomous Container DB -> Database Administrator -> Autonomous DB (A):

Fleet Administrator provisions Autonomous Exadata Infrastructure:The Fleet Administrator, responsible for infrastructure management, first sets up the Autonomous Exadata Infrastructure (AEI), which includes the physical Exadata hardware and networking configuration.

Fleet Administrator provisions Autonomous Container DB (ACD):Within the AEI, the Fleet Administrator creates the ACD, a container that hosts multiple Autonomous Databases.

Database Administrator provisions Autonomous DB:Finally, the Database Administrator (DBA) provisions individual Autonomous Databases within the ACD, configuring them for specific workloads (e.g., ATP or ADW).

The incorrect options are:

B:The Database Administrator cannot provision the ACD before the AEI is set up by the Fleet Administrator.

C and D:The Database Administrator does not provision the AEI or ACD; these are infrastructure-level tasks handled by the Fleet Administrator.

This order ensures proper separation of infrastructure and database management responsibilities.

The client credentials wallet for connecting to an Oracle Autonomous Database contains specific files required for secure connectivity. These files are downloaded from the OCI Console when you generate a wallet:

Correct Answer (A): protocol.ora is not a standard component of the client credentials wallet. It is typically used in traditional Oracle Database setups to define protocol parameters (e.g., TCP vs. IPC), but in Autonomous Database, such details are managed by Oracle and embedded within other wallet files like ewallet.p12.

Included Files:

B. ewallet.p12: Contains the encrypted private key and certificates for authentication.

C. sqlnet.ora: Specifies network configuration details (e.g., wallet location, encryption settings).

D. keystore.jks: A Java KeyStore file for Java-based applications to authenticate with the database.

Autonomous Transaction Processing (ATP) provides predefined connection services to optimize different workload types. For a high-concurrency OLTP application with parallel reporting queries, the appropriate service is:

HIGH (C):The HIGH connection service in ATP is designed for workloads requiring high concurrency and throughput, making it ideal for a production OLTP application like "EXAM" that handles many simultaneous transactions (e.g., user requests). Additionally, HIGH supports parallel query execution, which is critical for running reporting queries efficiently during off-peak times. It allocates more resources (e.g., OCPUs and I/O) compared to other services, ensuring performance for both transactional and analytical tasks. For example, the OLTP app might use HIGH to process thousands of concurrent user requests, while a nightly report leverages parallel processing to aggregate data quickly. In the wallet’s tnsnames.ora, the HIGH service might look like exam_high = (DESCRIPTION=...), offering the best balance for this mixed workload.

The incorrect options are:

TPURGENT (A):The TPURGENT service prioritizes low-latency, time-critical transactions (e.g., sub-second response times for single-user actions). It’s optimized for latency-sensitive operations, not high concurrency or parallel reporting, and would underperform for the broader OLTP and reporting needs here. For instance, it’s better suited for a single critical transaction than a multi-user system.

TP (B):The TP (Transaction Processing) service is a general-purpose option for OLTP workloads, offering moderate concurrency and latency. However, it’s not optimized for high concurrency or parallel query execution, making it less suitable for a production app with reporting demands. It’s a middle ground, not a top-tier performer like HIGH.

MEDIUM (D):The MEDIUM service balances performance and resource usage for moderate workloads. It supports some concurrency but lacks the resource allocation and parallel execution capabilities of HIGH, making it inadequate for a high-concurrency OLTP system with reporting requirements.

The HIGH service’s ability to handle both high transactional volume and parallel reporting aligns perfectly with the scenario’s strict performance needs, all within ATP’s zero-maintenance framework.

Oracle Autonomous Database on Dedicated Infrastructure enforces automatic maintenance to ensure security, stability, and performance. The correct answer is:

You cannot permanently disable scheduled Automatic Maintenance (C):Oracle mandates periodic maintenance updates (e.g., patching) to keep the database secure and compliant with the latest fixes. Customers can influence the timing of these updates but cannot disable them permanently. This is a design principle of the Autonomous Database service to reduce administrative overhead while maintaining system integrity.

The incorrect options are:

Change the Automatic Maintenance Schedule to 'No Preference' (A):This setting allows Oracle to determine the maintenance window but does not disable maintenance. It still occurs as scheduled by Oracle.

Change the Automatic Maintenance Schedule to 'None' (B):There is no 'None' option in the maintenance scheduling settings for Autonomous Dedicated Infrastructure. This is not a valid configuration.

Change the Automatic Maintenance Schedule to 'Specify a Schedule' but do not select any month, week, or day (D):This is not a functional workaround. Specifying a schedule requires selecting a valid time window, and leaving it blank does not prevent maintenance; it simply reverts to Oracle’s default scheduling.

Oracle’s documentation confirms that while customers can reschedule or skip specific maintenance runs (up to two consecutive quarters), permanently disabling automatic maintenance is not permitted to ensure the system remains up-to-date and secure.

Compartment quotas in Oracle Cloud Infrastructure (OCI) manage resource allocation:

Correct Answer (D): “Compartment quotas cannot be set on the root compartment” isfalse. Quotas can be applied to any compartment, including the root compartment, to limit resource usage tenancy-wide. While direct quotas on the root are less common (child compartment quotas are typically used), it’s technically possible via OCI policies.

True Statements:

A: Quotas offer flexible resource limits (e.g., OCPUs, storage) via policy statements.

B: Parent compartment quotas take precedence over child quotas, enforcing hierarchical control.

Defining a maintenance schedule for Dedicated Exadata Infrastructure allows customization:

Correct Answer (B): “Month of the Quarter, Week of the Month, Day of the Week, Start Hour” is the correct set. For example, you can specify “Month 2 of Q1, Week 3, Wednesday, 02:00 AM,” aligning with quarterly planning while offering weekly and daily precision.

Incorrect Options:

A: “Quarter of the Year” and “Date of the Month” are less flexible than week-based options and not the standard format.

C: “Month of the Year” skips the quarterly structure used in dedicated maintenance.

Oracle provides specialized index types for different data indexing needs. The correct answer is:

CTXCAT (B):The CTXCAT index type is specifically designed for indexing catalog information, such as product catalogs or structured data with short text fields. It supports fast queries on structured data combined with text search, making it ideal for applications like e-commerce catalogs.

The incorrect options are:

CONTEXT (A):The CONTEXT index is used for full-text search on large unstructured text data (e.g., documents), not specifically for catalog information.

CTXRULE (C):The CTXRULE index is designed for rule-based classification of text, not for catalog indexing.

CONSTRAINS (D):This appears to be a typo (likely meant "CONSTRAINTS"), but constraints are not index types; they enforce data integrity rules, not indexing.

CTXCAT enhances performance for catalog-style queries, distinguishing it from other text index types.

Oracle recommends best practices for effective alarm management:

Correct Answer (A):Suppress alarms during investigationsprevents notification overload while troubleshooting, focusing attention on the issue.

Correct Answer (C):Select the correct alarm interval for your metricensures timely alerts without excessive noise (e.g., 1-minute intervals for critical metrics).

Correct Answer (D):Routinely tune your alarmsadjusts thresholds and settings to match workload changes, maintaining relevance.

Incorrect Option:

Oracle Autonomous JSON Database is a specialized variant of Autonomous Database. The correct workload is:

Schema-less, document-centric (D):Autonomous JSON Database is designed for applications needing flexible, schema-less data storage and retrieval, particularly JSON documents. It’s a NoSQL-style database optimized for document-centric workloads, such as web or mobile apps storing user profiles, IoT data, or content management systems. For example, a social media app might store user posts as JSON documents { "user": "John", "post": "Hello world" }, allowing dynamic field additions without schema changes. It supports SQL/JSON queries (e.g., SELECT JSON_VALUE(doc, '$.user')), blending relational and NoSQL benefits, and auto-manages indexing for performance.

The incorrect options are:

Data Marts (A):Data marts are structured, analytical stores for aggregated data, better suited to Autonomous Data Warehouse (ADW), which excels at columnar storage and complex queries, not JSON’s flexible format.

Transactions (B):Traditional OLTP transactions (e.g., banking records) are the domain of Autonomous Transaction Processing (ATP), which uses rigid schemas for consistency, unlike JSON Database’s schema-less approach.

Data Lakes (C):Data lakes store raw, mixed-format data (e.g., JSON, CSV, Parquet) for later processing, typically in object storage, not a managed database like Autonomous JSON. While JSON Database handles JSON, it’s not a data lake replacement.

This workload leverages JSON Database’s agility for modern, unstructured data applications.

Python developers connect to Autonomous Database using a dedicated library:

Correct Answer (D): “By using Oracle Client and the cx_Oracle interface” (now renamed oracledb) is the recommended method. The Oracle Client provides the underlying connectivity, and cx_Oracle (or oracledb) is a Python module for database access, supporting wallet-based authentication to Autonomous Database.

Incorrect Options:

A: SQL Developer is a GUI tool, not a Python interface.

B: DBD-oracle is not a standard Python library for Oracle; it’s likely a typo or confusion with Perl’s DBI.

Full Detailed In-Depth Explanation:

When provisioning an Autonomous Container Database (ACD) on dedicated infrastructure, Oracle provides specific options for backup retention periods to balance data recovery needs with storage costs. According to the official Oracle documentation, the available backup retention periods for a dedicated ACD are:

7 days: This is the default retention period for a newly provisioned ACD.

15 days: An option for extended retention beyond the default.

60 days: The maximum supported retention period for ACDs, offering the longest recovery window.

The option of120 daysis not supported as a backup retention period for an Autonomous Container Database. This limitation is due to the design of the Autonomous Database service, which caps retention at 60 days to optimize storage and performance on dedicated Exadata infrastructure. Attempting to set a retention period beyond 60 days is not an available choice during provisioning. Users must select a retention period that meets their recovery point objectives (RPO) within these constraints, noting that longer retention increases storage usage and associated costs.

Database Actions (formerly SQL Developer Web) offers tools for database management:

Correct Answer (A): TheCatalogtool provides a detailed view of database entities (tables, views, schemas) and their metadata, including dependencies via the “Impact” tab. It helps assess how changes (e.g., dropping a table) affect related objects.

Incorrect Options:

B: Data Load is for importing data, not analyzing entities or dependencies.

C: JSON is a data format, not a tool; it’s supported but irrelevant here.

Oracle Data Pump is a key tool for migrating databases to Autonomous Database. The two objects imported are:

Data (B):Data Pump imports the actual data from the source database into the target Autonomous Database. This includes rows from tables, LOBs, and other data types stored in the dump file (e.g., .dmp). For example, if you export a table CUSTOMERS with 1 million rows, Data Pump imports all that data into ADB using DBMS_CLOUD.COPY_DATA after uploading the dump to OCI Object Storage. This ensures the content of your database is transferred intact.

Schemas (C):Data Pump imports schema definitions, including tables, views, indexes, triggers, and other objects owned by the schema. For instance, exporting a schema HR with tables like EMPLOYEES and DEPARTMENTS will recreate those objects in ADB, preserving their structure. The impdp utility or DBMS_CLOUD handles schema metadata, though some objects (e.g., indexes) may be recreated automatically by ADB’s optimization.

The incorrect options are:

Tablespaces (A):Tablespaces are not imported directly. In Autonomous Database, storage is fully managed, and tablespaces are abstracted away. Data Pump imports data and schemas into ADB’s managed tablespaces (e.g., DATA), not user-defined ones from the source. For example, a source tablespace USERS isn’t replicated; its data is mapped to ADB’s default storage.

Report (D):“Report” is not a database object; it might refer to query outputs or logs, but Data Pump doesn’t import such entities. It focuses on database content, not external artifacts.

This process ensures a smooth migration of data and structure to ADB’s managed environment.

Scaling resources in Autonomous Database offers flexibility. The true statement is:

OCPUs and storage can be scaled independently (A):In Autonomous Database, you can adjust the number of OCPUs (compute resources) and storage capacity (in terabytes) separately via the OCI console or CLI. For example, you might provision an ADB with 2 OCPUs and 1 TB of storage. Later, you could scale to 4 OCPUs without changing storage, or increase storage to 2 TB without touching OCPUs. This decoupling allows tailored resource allocation—e.g., more compute for a CPU-intensive workload or more storage for growing data—without over-provisioning. Scaling is online, with no downtime, and status shows “SCALING IN PROGRESS” during the operation.

The incorrect options are:

Use auto scaling to increase storage (B):Auto scaling applies to OCPUs only, allowing up to 3x the base CPU allocation dynamically. Storage scaling is manual; you specify a new size (e.g., via oci db autonomous-database update), not via auto scaling.

Increasing OCPUs will automatically increase storage (C):There’s no automatic linkage between OCPU and storage scaling. They are independent parameters, and increasing one does not affect the other unless explicitly requested.

OCPUs and storage must remain in sync (D):No such synchronization is required. You can have 1 OCPU with 10 TB or 10 OCPUs with 1 TB, depending on workload needs.

This independence is a hallmark of Autonomous Database’s elasticity.

When auto scaling is enabled in Oracle Autonomous Database, it dynamically adjusts resources to handle workload demands. The correct answer is:

Enables the database to use up to 3x CPU/IO resources immediately when needed by the workload (D):Auto scaling allows the database to automatically scale its CPU and I/O resources up to three times the base number of OCPUs provisioned, without manual intervention. This ensures the database can handle sudden spikes in demand efficiently, reverting to the base level when the workload decreases. This feature applies to both Autonomous Transaction Processing (ATP) and Autonomous Data Warehouse (ADW).

The incorrect options are:

Increases the number of sessions available to the database (A):Auto scaling does not directly increase session limits; session capacity is tied to the service level (e.g., LOW, MEDIUM, HIGH) and not dynamically adjusted by auto scaling.

Scales the PGA and SGA size when needed for the workload (B):The Program Global Area (PGA) and System Global Area (SGA) are memory structures managed automatically by Oracle, but auto scaling specifically adjusts CPU and I/O resources, not memory allocation directly.

Database concurrency is scaled up when needed by the workload (C):While increased CPU/IO resources can improve concurrency indirectly, auto scaling does not explicitly manage concurrency levels; this is more related to connection service settings.

This capability enhances performance elasticity for unpredictable workloads.