The Always Free tier of Autonomous Database has specific limits. The two correct restrictions are:

Maximum of two Always Free Databases per OCI tenancy (B): OCI’s Always Free tier allows up to two free ADB instances per tenancy (e.g., one ATP, one ADW). This limit ensures fair resource distribution across users. For example, you might create FREEATP1 (1 OCPU, 20 GB) and FREEADW1 (1 OCPU, 20 GB) in your tenancy, but a third free instance isn’t permitted—you’d need a paid upgrade. This is tracked by tenancy OCID, visible in the OCI console under “Limits.”

Maximum of one OCPU per Database (D): Each Always Free ADB is capped at 1 OCPU, non-scalable, with 20 GB of storage. This restricts compute power (e.g., no auto-scaling to 3x like paid tiers), suitable for small workloads like dev/test apps. For instance, a free ATP instance runs a lightweight app with SELECT * FROM users, but can’t handle heavy concurrency due to the single OCPU.

The incorrect options are:

Supports only ATP as a workload type (A): False. Always Free supports both ATP (transactional) and ADW (warehouse) workload types, giving flexibility for OLTP or analytics (e.g., ATP for a web app, ADW for reports).

Oracle Application Express (APEX) not included (C): False. APEX is included in both free ATP and ADW instances, pre-installed and accessible via the OCI console (e.g., “Development” > “APEX”). You can build apps like a task tracker without extra cost.

These restrictions balance free access with resource constraints, encouraging upgrades for heavier use.

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.

Full Detailed In-Depth Explanation:

Bring Your Own License (BYOL) allows using existing on-premises Oracle licenses in the cloud:

A: False. Exadata is included in Autonomous Database; no separate license is needed.

B: False. Active Data Guard is an optional feature, not required for BYOL.

C: True. RAC is needed for BYOL when scaling beyond 16 OCPUs, as Autonomous Database uses RAC for high availability in larger deployments.

D: True. Multitenant is mandatory, as Autonomous Database uses a multitenant architecture (CDB/PDB).

E: False. TDE is included by default, not a BYOL requirement.

The scenario requires a low-maintenance, high-performance database for an OLTP web application with occasional reporting. The correct answer is:

ATP using 'tpurgent' and 'high' TNS services to separate connection types (A): Autonomous Transaction Processing (ATP) is ideal here. It’s a fully managed database optimized for OLTP workloads (e.g., scheduling service requests) with zero maintenance overhead—Oracle handles patching, backups, and tuning. ATP supports multiple connection services:

'tpurgent': Prioritizes low-latency, time-critical transactions (e.g., customer scheduling requests), ensuring fast response times for the web app.

'high': Suited for high-concurrency or reporting queries, allowing operational reports to run during non-peak hours without impacting the OLTP workload. By using these predefined services, the architecture separates transactional and reporting workloads within the same database, meeting performance needs without additional administration. For example, the web app connects via tpurgent for real-time updates, while a reporting tool uses high for batch queries at night, leveraging ATP’s auto-scaling if needed.

The incorrect options are:

Since the application needs to be highly available, it should be deployed on a Kubernetes Cluster (B): This misinterprets the question—it’s about the database service, not the application deployment. Kubernetes is for container orchestration, not a database solution, and adds complexity counter to the low-maintenance goal.

It is best to build a separate data warehouse, and move the OLTP data on a nightly basis (C): While a separate Autonomous Data Warehouse (ADW) could handle reporting, it requires data movement (e.g., via ETL), increasing admin effort and complexity, which the DBA Manager wants to avoid. ATP can handle both workloads with proper service separation.

ADW since operational reporting is a higher priority in this scenario (D): ADW is optimized for analytics, not OLTP. The web app’s transactional needs are primary, with reporting secondary and occasional, making ATP more suitable.

ATP’s self-managing nature and service flexibility make it the best fit.

Full Detailed In-Depth Explanation:

REST APIs use HTTP verbs:

A: True. POST creates new resources, such as an Autonomous Database instance.

B: False. GET retrieves data, not creates.

C: False. PUT updates existing resources.

D: False. INSERT is not a REST verb; it’s SQL-specific.

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_ < DB_UNIQUE_NAME > (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_ < UNIQUE_NAME > 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.

Oracle Data Pump is a powerful tool for migrating databases to Autonomous Database (ADB). The two correct advantages are:

Data Pump can exclude migration of objects like indexes and materialized views that are not needed by Autonomous Database (C): True. Data Pump’s EXCLUDE parameter allows skipping objects like indexes and materialized views during export (e.g., expdp ... EXCLUDE=INDEX,MATERIALIZED_VIEW). In ADB, these objects are often redundant because the database automatically creates and manages them based on workload (e.g., auto-indexing). For example, exporting a schema with EXCLUDE=INDEX from an on-premises database reduces migration overhead, as ADB recreates necessary indexes post-import, optimizing for its managed environment. This flexibility minimizes unnecessary data transfer and speeds up the process.

Data Pump is platform-independent - it can migrate Oracle databases running on any platform (D): True. Data Pump uses a platform-agnostic dump file format (.dmp), enabling migration from any Oracle Database (e.g., on Linux, Windows, or Solaris) to ADB in the cloud. For instance, you could export from an Oracle 12c database on AIX, upload the dump to OCI Object Storage, and import it into ADB using DBMS_CLOUD.COPY_DATA, regardless of endianness or OS differences (handled by Data Pump’s conversion). This universality makes it ideal for heterogeneous migrations.

The incorrect options are:

Data Pump is faster to migrate database than using RMAN (A): False. Speed depends on context—RMAN (Recovery Manager) is faster for physical migrations (e.g., restoring backups) of entire databases, especially large ones, due to block-level copying. Data Pump, a logical migration tool, extracts and loads data row-by-row, which can be slower for massive datasets but offers more control (e.g., schema selection). No universal speed advantage exists; it’s workload-specific.

Data Pump creates the tablespaces used by your Autonomous Database (B): False. In ADB, tablespaces are fully managed by Oracle (e.g., DATA tablespace), and Data Pump doesn’t create them. It imports data into existing, pre-allocated storage, ignoring source tablespace definitions. E.g., a source tablespace USERS is mapped to ADB’s default storage, not recreated.

These advantages make Data Pump a versatile, tailored migration solution for ADB.

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.

Oracle recommends best practices for effective alarm management:

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

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

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

Incorrect Option :

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.