Which three operations are available for a quarterly maintenance update on Autonomous Container
Database? (Choose three.)
B, C, D
Explanation:
Oracle Autonomous Container Database (ACD) provides specific options for managing quarterly
maintenance updates to ensure minimal disruption and flexibility. The three correct operations
available are:
Reschedule and patch immediately (B): This option allows users to adjust the maintenance window
to a more convenient time and apply the patch right away within that rescheduled window. It’s
useful when the default schedule conflicts with business operations but immediate patching is still
desired.
Reschedule patching (C): This option enables users to defer the patching to a later maintenance
window that suits their operational needs, providing flexibility without applying the patch
immediately.
Skip patching (D): Users can choose to skip a quarterly maintenance update entirely, which is
beneficial if the current database version is stable and no immediate updates are required. Oracle
allows skipping up to two consecutive quarterly updates for Autonomous Container Databases on
dedicated infrastructure.
The incorrect options are:
Patch immediately (A): This is not a standalone option for quarterly updates on ACDs. Patching
occurs within scheduled maintenance windows, and immediate patching outside of rescheduling is
not supported as a distinct choice.
Apply a partial patch (E): Oracle does not support applying partial patches during quarterly
maintenance updates. Updates are delivered as complete bundles to ensure consistency and
security.
This aligns with Oracle’s maintenance policies for Autonomous Databases on dedicated
infrastructure, where control over scheduling and skipping is provided, but partial patching is not an
option.
Reference: Oracle Cloud Infrastructure Documentation - Managing Autonomous Container Databases
Your customer wants to permanently disable scheduled maintenance on Autonomous Dedicated
Infrastructure to keep their current database version. How can they achieve this?
C
Explanation:
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.
Reference: Oracle Cloud Infrastructure Documentation - Update ACD Maintenance Preferences
Which statement is false about Autonomous Database Oracle Client Credentials (Wallets)?
A
Explanation:
Oracle Client Credentials (wallets) are essential for secure connections to the Autonomous Database.
The false statement is:
The Wallet for the Autonomous Database is the same as the TDE wallet (A): This is incorrect. The
Oracle Client Credential wallet (used for client authentication and connection security) is distinct
from the Transparent Data Encryption (TDE) wallet (used to encrypt data at rest within the database).
The client wallet contains certificates and keys for mutual TLS (mTLS) authentication, while the TDE
wallet manages encryption keys for data security. They serve different purposes and are not the
same.
The correct statements are:
You must have an Oracle Client Credential wallet in order to connect to the Autonomous Database
(B): True. The wallet is required for mTLS, which is the default authentication method for
Autonomous Databases, ensuring secure connections.
In addition to the Oracle Client Credential Wallet, a user must have a username and password in
order to connect to the Autonomous Database (C): True. Alongside the wallet, a database username
and password are needed for full authentication (mTLS + user credentials).
The Oracle Client Credential file is downloaded as a ZIP file (D): True. When downloaded from the
Oracle Cloud Infrastructure (OCI) console, the wallet is provided as a ZIP file containing configuration
files like tnsnames.ora and certificates.
This distinction is critical for understanding security mechanisms in Autonomous Database.
Reference: Oracle Cloud Infrastructure Documentation - Connecting to Autonomous Database
How can an Autonomous Database resource be provisioned without logging into the Oracle Cloud
Infrastructure Console?
D
Explanation:
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
Which three functions are provided by Spatial Studio? (Choose three.)
A, C, E
Explanation:
Oracle Spatial Studio is a self-service tool for working with spatial data in Autonomous Database. The
three correct functions are:
Map visualization (A): Spatial Studio provides robust capabilities to visualize spatial data on
interactive maps, enabling users to explore geographic patterns and relationships visually.
Spatial analysis (C): It offers tools for performing spatial operations like proximity analysis, spatial
joins, and buffering, which are essential for deriving insights from geographic data.
Spatial data editing (E): Users can edit spatial data, such as modifying geometries or updating
attributes, directly within Spatial Studio, making it a powerful tool for data management.
The incorrect options are:
Custom SQL queries (B): While Spatial Studio supports spatial operations, it is primarily a graphical
tool and does not focus on executing custom SQL queries. Such functionality is more aligned with
tools like SQL Developer.
Geocoding (D): Geocoding (converting addresses to coordinates) is not a core feature of Spatial
Studio. It focuses on visualization, analysis, and editing rather than address-to-coordinate
conversion, which is typically handled by separate Oracle services or tools.
These functions align with Spatial Studio’s purpose of simplifying spatial data management and
analysis.
Reference: Oracle Cloud Infrastructure Documentation - Spatial Studio Overview
Which index type is designed to index catalog information?
B
Explanation:
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.
Reference: Oracle Database Documentation - Text Index Types
Which option describes the connection types that third-party software can use to connect to an
Autonomous Database (ADB)?
B
Explanation:
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
When integrating object storage with Autonomous Database, how effectively does Oracle use the
files in the object storage?
B
Explanation:
When Autonomous Database integrates with object storage (e.g., Oracle Cloud Infrastructure Object
Storage), it optimizes data access. The correct answer is:
Scan partition tables (B): Oracle leverages partition pruning when scanning tables stored in object
storage. This means it only scans the relevant partitions based on query predicates, significantly
reducing I/O and improving performance. This is particularly effective for partitioned tables stored in
formats like Parquet or ORC, which support partitioning.
The incorrect options are:
Prune columns in parquet files (A): While column pruning is possible with columnar formats like
Parquet, the primary optimization highlighted in Oracle’s documentation for object storage
integration is partition pruning, not column pruning alone.
Scan hybrid partition tables (C): “Hybrid partition tables” is not a standard term in this context.
Oracle supports external partitioned tables, but the focus is on scanning partitioned tables, not a
hybrid-specific optimization.
Prune columns in CSV files (D): CSV files are row-based and do not natively support column pruning,
making this less effective compared to partition scanning.
Partition pruning is a key optimization for external tables in object storage, enhancing query
efficiency.
Reference: Oracle Cloud Infrastructure Documentation - Query External Data
Which predefined role that exists in Autonomous Database includes common privileges that are used
by a Data Warehouse developer? (Choose the best answer.)
B
Explanation:
Autonomous Database provides predefined roles tailored to specific use cases. The correct answer is:
DWROLE (B): The DWROLE predefined role is designed for Data Warehouse developers. It includes
privileges commonly needed for data warehousing tasks, such as creating tables, views, and
materialized views, as well as executing analytical queries. This role is optimized for Autonomous
Data Warehouse (ADW) workloads.
The incorrect options are:
ADBDEV (A): There is no predefined ADBDEV role in Autonomous Database; this appears to be a
fictional or misinterpreted role.
ADMIN (C): The ADMIN role is a superuser role with full database privileges, far exceeding the needs
of a typical Data Warehouse developer and not tailored to that specific use case.
ADWC (D): This is not a predefined role; it might be a typo or confusion with ADW (Autonomous Data
Warehouse), but no such role exists.
DWROLE is the best fit for a Data Warehouse developer’s needs.
Reference: Oracle Cloud Infrastructure Documentation - Predefined Database Roles
To whom, and in which order, are dedicated Exadata Infrastructure resources provisioned?
A
Explanation:
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.
Reference: Oracle Cloud Infrastructure Documentation - Provisioning Autonomous Exadata
Infrastructure
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