Which statement is true when the Autonomous Database has auto scaling enabled?
D
Explanation:
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.
Reference: Oracle Cloud Infrastructure Documentation - Auto Scaling in Autonomous Database
While creating an Autonomous Container Database on dedicated infrastructure through the Oracle
Cloud Infrastructure (OCI) console, which patch type is offered to be applied during maintenance?
D
Explanation:
When creating an Autonomous Container Database (ACD) on dedicated infrastructure, Oracle offers
specific patch types for maintenance. The correct answer is:
Release Update (RU) (D): During the creation of an ACD via the OCI console, users can choose to
apply a Release Update (RU), which includes the latest security patches, bug fixes, and
enhancements for the database version. RUs are the standard patching mechanism for Autonomous
Databases on dedicated infrastructure, ensuring the system stays current.
The incorrect options are:
Quarterly Bundle Patch (QBP) (A): QBPs are not a recognized patch type for Autonomous Databases;
they are more associated with on-premises Oracle deployments, not the cloud-native Autonomous
infrastructure.
Prior Release Update Revision (PRUR) (B): PRURs are minor updates to prior releases, but they are
not offered as a distinct option during ACD creation; Oracle focuses on RUs for consistency.
Prior Release Update (PRU) (C): PRUs refer to updates from previous major releases, but
Autonomous Databases typically apply the latest RU, not prior ones, during provisioning or
maintenance.
RUs align with Oracle’s strategy for maintaining Autonomous Databases.
Reference: Oracle Cloud Infrastructure Documentation - Patching Autonomous Container Databases
Which two statements are true about Recovery Time Objective (RTO) and Recovery Point Objective
(RPO) for Autonomous Data Guard? (Choose two.)
C, E
Explanation:
Autonomous Data Guard enhances high availability for Autonomous Database. The two true
statements are:
RPO is 0 minutes for an automatic failover (C): Recovery Point Objective (RPO) measures potential
data loss. With Autonomous Data Guard, the standby database is synchronously replicated with the
primary, ensuring zero data loss (RPO = 0) during an automatic failover, as all transactions are
mirrored in real-time.
RTO is 2 minutes for an automatic failover (E): Recovery Time Objective (RTO) measures downtime
during failover. For Autonomous Data Guard, Oracle specifies an RTO of approximately 2 minutes for
automatic failovers, reflecting the time to detect failure and promote the standby to primary.
The incorrect options are:
RTO and RPO are adjustable through the OCI console (A): RTO and RPO are fixed by the Autonomous
Data Guard architecture and cannot be manually adjusted via the OCI console.
RPO is adjustable, but RTO is always 5 minutes (B): RPO is not adjustable (it’s 0 due to synchronous
replication), and RTO is not fixed at 5 minutes; it’s typically 2 minutes for automatic failover.
RTO and RPO are 0 minutes for manual failovers (D): Manual failovers (switchovers) have an RTO
greater than 0 (typically a few minutes) due to manual initiation, though RPO remains 0 with
synchronous replication.
These values ensure minimal disruption and data loss.
Reference: Oracle Cloud Infrastructure Documentation - Autonomous Data Guard
What is the default time range in Performance Hub?
C
Explanation:
Performance Hub in Autonomous Database provides performance monitoring insights. The correct
answer is:
24 Hours (C): When you open Performance Hub in the OCI console or Database Actions, the default
time range displayed is the last 24 hours, shown in Coordinated Universal Time (UTC). This allows
users to review recent performance metrics like CPU usage, SQL activity, and wait times. Users can
adjust this range (e.g., to 1 hour or 1 week) as needed.
The incorrect options are:
15 Minutes (A): This is not a default option; it’s too short for a broad performance overview.
1 Hour (B): Available as an option, but not the default setting.
1 Week (D): Also available, but not the default; it’s a longer-term view users can select manually.
The 24-hour default balances recency and context for performance analysis.
Reference: Oracle Cloud Infrastructure Documentation - Performance Hub
Which of the following is not required for connecting to Autonomous Database (ADB) via SQL
Developer?
E
Explanation:
Connecting to Autonomous Database (ADB) via SQL Developer requires specific parameters. The
correct answer is:
Connection Name (E): The Connection Name is a user-defined label in SQL Developer to identify the
connection in the tool’s interface. It is not a technical requirement for establishing the database
connection itself, making it optional in terms of connectivity.
The required parameters are:
Password (A): Essential for user authentication alongside the username.
Service (B): Refers to the service name (e.g., high, medium, low) from the wallet’s tnsnames.ora,
specifying the performance level and connection type.
Username (C): Required to identify the database user.
Database name (D): Needed to specify the target database or PDB within the ADB instance, typically
provided via the wallet configuration.
Without A, B, C, and D, the connection cannot be established, but E is merely a convenience.
Reference: Oracle Cloud Infrastructure Documentation - Connecting with SQL Developer
Which workload type does the Autonomous Database on dedicated infrastructure service currently
support?
C
Explanation:
Autonomous Database on dedicated infrastructure supports multiple workload types. The correct
answer is:
ATP and ADW (C): Autonomous Database on dedicated infrastructure supports both Autonomous
Transaction Processing (ATP) for OLTP workloads (high concurrency, low latency) and Autonomous
Data Warehouse (ADW) for analytical workloads (high throughput, complex queries). This dual
support allows flexibility within a single dedicated Exadata infrastructure.
The incorrect options are:
Autonomous Transaction Processing only (A): Incorrect, as ADW is also supported.
Hybrid Columnar Compression (B): HCC is a data compression feature, not a workload type; it’s used
within ADW but doesn’t define the workload.
Autonomous Data Warehouse only (D): Incorrect, as ATP is also supported.
This versatility is a key feature of dedicated deployments.
Reference: Oracle Cloud Infrastructure Documentation - Autonomous Database on Dedicated
Infrastructure
Which of the following two statements regarding Data Transforms are correct? (Choose two.)
B, D
Explanation:
Data Transforms is a feature in Autonomous Database for designing data transformations. The two
correct statements are:
Data Transforms allows you to design data transformations in the form of data loads, data flows, and
workflows (B): True. Data Transforms provides a graphical interface to create data loads (importing
data), data flows (transforming data), and workflows (sequencing operations), simplifying ETL
processes within ADB.
All capabilities to transform data in ODI Classic are available with ODI Web Edition (D): True. Oracle
Data Integrator (ODI) Web Edition, which integrates with Data Transforms, retains the full
transformation capabilities of ODI Classic, adapted for a web-based interface.
The incorrect statements are:
Data Transforms provides access to Oracle Data Integrator (ODI) Web Edition (A): False. Data
Transforms is a distinct tool within ADB; while it leverages ODI under the hood, it does not directly
provide access to ODI Web Edition as a standalone product.
Workflows for Data Transforms are only available on the ODI Web Edition (C): False. Workflows are
part of Data Transforms itself, not exclusive to ODI Web Edition.
These features enhance data integration in ADB.
Reference: Oracle Cloud Infrastructure Documentation - Data Transforms
When you are increasing the number of OCPUs in your Autonomous Database, what does its status
show?
D
Explanation:
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.
Reference: Oracle Cloud Infrastructure Documentation - Scaling Autonomous Database
Which subset of services is offered via OCI-CLI (Command Line Interface) for Autonomous Database
(ADB) via calls made to the OCI APIs?
B
Explanation:
The OCI Command Line Interface (CLI) provides a range of commands for managing Autonomous
Database via OCI APIs. The correct answer is:
Create, Get, List, Stop, Restore (B): These are key operations supported by the OCI CLI for
Autonomous Database:
Create: oci db autonomous-database create provisions a new ADB instance.
Get: oci db autonomous-database get retrieves details of a specific ADB.
List: oci db autonomous-database list lists all ADBs in a compartment.
Stop: oci db autonomous-database stop halts the database.
Restore: oci db autonomous-database restore restores from a backup.
The incorrect options are:
A (Start, Delete, Update, Query, Stop): “Query” is not a CLI command; “Delete” and “Update” are
valid but not part of this specific subset.
C (Create, Query, Update, List, Start): “Query” is invalid; “Update” is supported but not listed here.
D (Create, Query, List, Stop, Restore): “Query” is not a valid CLI operation.
This subset reflects common management tasks via CLI.
Reference: Oracle Cloud Infrastructure Documentation - OCI CLI for Autonomous Database
Which terminology is used to refer to a communication channel for sending messages to a
subscription, such as email or SMS, in Oracle Cloud Infrastructure?
C
Explanation:
In Oracle Cloud Infrastructure (OCI), the Notifications service is used to send messages (e.g., via
email, SMS, or HTTP endpoints) to subscribers. The correct terminology for the communication
channel is:
Topic (C): A "topic" in OCI Notifications is the named entity that acts as a communication channel.
Publishers send messages to a topic, and subscribers (e.g., email addresses, SMS numbers, or custom
endpoints) receive those messages based on their subscription to that topic. For example, you might
create a topic called "DatabaseAlerts" to send notifications about database events. When a message
is published to this topic, all subscribed endpoints (e.g., an email like [email protected]) receive it.
This design follows a publish-subscribe (pub/sub) model, making "topic" the central concept for
message distribution.
The incorrect options are:
Subject (A): The "subject" is a field within a message (e.g., the subject line of an email), not the
channel itself. It describes the content of an individual notification but doesn’t define the mechanism
for sending it. For instance, an email notification might have a subject like "Database Maintenance
Scheduled," but the topic is the channel delivering it.
Notification (B): A "notification" refers to the actual message being sent (the payload), not the
channel through which it travels. It’s the output of the process, not the infrastructure enabling it. For
example, a notification might be "Database is down," but it’s sent via a topic.
Event (D): An "event" is an occurrence or trigger (e.g., a database failover) that might generate a
notification, but it’s not the channel. Events are inputs that can be monitored by services like OCI
Events, which then publish to a topic in Notifications.
The use of "topic" aligns with OCI’s architecture for scalable, decoupled messaging. To illustrate,
you’d create a topic in the OCI console under "Notifications," configure subscriptions (e.g., email or
SMS), and then use APIs or triggers to publish messages to it. This abstraction ensures flexibility and
reliability in message delivery across various protocols.
Reference: Oracle Cloud Infrastructure Documentation - Notifications Overview