1z0-931-23 Oracle Autonomous Database Cloud 2023 Specialist Questions and Answers

Autonomous Exadata Infrastructure instances and Autonomous Container Databases have no dependent resources that move with them. Associated (non-dependent) resources remain in their current compartments.

Moving an Autonomous Database instance does not include its automatic backups.

You do not need to have sufficient access permissions on the compartment that the resource is being moved to.

Moving the compartment of the Autonomous Database will also move the Autonomous Container Database and Autonomous Exadata Infrastructure.

Users have OS access to the database machine.

Users can customize the maintenance schedule.

It offers greater control and isolation starting at the Exadata cloud infrastructure level.

Users have SYS privileges in the database.

Users can customize the OS stack and add additional packages

Network Security Group

Security List

VCN

Route Table

Subnet

Regular Oracle SQL statements using a connection string to the database

Oracle Cloud Infrastructure console using the JSON Developer tool

REST API calls to the database

O NoSQL statements using Simple Oracle Document Access (SODA) drivers

Parallelism settings

Amount of storage

Number of OCPUS displayed in the console

Level of concurrency

I/O resources

Active transactions in Autonomous Data Warehouse are paused

Active transactions continue running unaffected

Active transactions are paused

Active transactions are terminated and rolled back

Scaling can happen while there are active transactions in the database

The IP Protocol is set to TCP

A stateless ingress rule is created to allow connections from the source to the Autonomous Database instance

The source is set to the address range you want to allow to connect to your database

The destination port range is set to 1522

3-D modelling

Churn analysis

Pattern matching

Facial recognition

Clustering

Business Object Security Feature

Analytic View Transparency View

Autonomous Aggregate Cache

Display private tables

Analytic View Base Table Query Transformation

creating and scaling an Autonomous Database service

configuring virtual cloud networks (VCNS)

monitoring Autonomous Databases for usage and query performance

using a wizard to download connection wallet for connection from desktop tools

starting and stopping an instance

15 days

1 day

7 days

30 days

supports only ATP as a workload type

maximum of two Always Free Databases per OCI tenancy

Oracle Application Express (APEX) not included

maximum of one OCPU per Database

Private endpoints can be configured when you clone an Autonomous Database on Shared Infrastructure that was initially created with public endpoints

An Autonomous Database with private endpoints can be accessed from the public Internet by adding your IP address to an Access Control List (ACL)

A Network Security Group (NSG) is required within your virtual cloud network before you can provision a Shared Autonomous Database to use private endpoints

You can configure private endpoints for an Always Free Autonomous Database

optimized data archive using partitioned external tables

optimized data archive using hybrid partitioned tables

scan avoidance using block skipping when reading parquet and ore files

scan avoidance using columnar pruning for columnar stores like parquet and orc

scan avoidance using partitioned external tables

scan avoidance using columnar pruning for .csv files

It provides indexing, word and theme searches

It is suited to search document collections

It requires an Oracle Text license for Autonomous Database

t uses standard SQL queries

After an Autonomous database is created using a clone, the network access option can be changed.

A clone database source can be a running database instance.

A clone database source can be from a point-in-time backup that is less than 2 hours old.

When cloning an Autonomous Database, Oracle Machine Learning workspaces, projects, and notebooks of the source database are cloned to the new database.

Terminate End

Maintenance Begin

Change Compartment Begin

Change Autoscaling Configuration Compartment

Update IORM Begin

the Oracle Cloud Infrastructure A. service console

SQL Developer

the DBMS_CLOUD_ADMIN package

SQL *Plus

Create a separate VCN that contains only public subnets

Only 1 of each is allowed to be allocated per environment.

Only 1 Subnet and 1 Compartment are allowed, multiple Groups highly advised.

Create at least 2 of each resource

licence-model

db-workload

is-dedicaced

db-type

Process includes identify candidates, create invisible auto indexes , verify with implement if performance improved and delete unused.

You can use the dbms_auto_index package to report on the automatic task and to set your preferences.

It is enabled by default.

You can control behavior at the statement level using the use_aoto_indexes or NO_USE_AUTO_INDEXES hints.

The indexing feature is implemented as an automatic task that runs at a fixed interval.

On the Autonomous Database Console.

SSH keys are not required in Oracle Cloud Infrastructure.

SSH keys cannot be added from console. They have to be added using REST APIs only.

Navigate to Identity, select Users panel on the console and select "Add Public Key".

Oracle Cloud Infrastructure Object Storage

Google Cloud Storage

Amazon S3

Azure Blob Storage

Oracle Cloud Infrastructure Object Storage Classic

Run the DBMS_CLOUD.INCREASE_THROUGHPUT procedure.

Remove any non-JSON data from the database.

Increase the number of OCPUs allocated to the database.

Ask Support to migrate their setup to a node without noisy neighbors.

Allow group ADB-Admins to manage autonomous-database in tenancy where target.workloadType = ‘DW’

Allow group ADB-Admins to manage autonomous-database in tenancy.

Allow group ADB-Admins to manage autonomous-database-family in tenancy.

Allow group ADB-Admins to manage autonomous-database in tenancy where target.workloadType = 'OLTP'

Add a "BEFORE SHUTDOWN ON DATABASE" trigger within the database

Create a rule for the Oracle Cloud Infrastructure Event for "Autonomous Database STOP END"

Create a notification alert using DBMS_SNMP package

Create an Oracle Cloud Infrastructure Alarm for Shutdown metric

VM on Oracle Cloud Infrastructure

Bare-metal on Oracle Cloud Infrastructure

Exadata on Oracle Cloud Infrastructure

Any Oracle Engineered system

1-25 X OCPU

OS

unlimited

20 X OCPU

Create a single alarm for each metric

Suppress alarms during investigations

Tune your alarms routinely

Select the correct alarm interval for your metric

Use a single interval for all alarms

Create multiple alarm metrics

The standby database is started readwrite

The standby database is transformed in a refreshable clone

The standby database is terminated

The standby database is started read only

The standby database is terminated.

The standby database is also stopped.

Switchover is automatically initiated.

Failover is automatically initiated.

Autonomous Data Guard automatically reverts to the primary database when it becomes available again

Autonomous Data Guard automatically creates a new standby database

A new wallet is required to connect to the standby database

The OCPU Count, Storage, Display Name, Database Name, Auto Scaling, Tags, and Licensing options have the same values as the primary

Oracle Machine Learning Notebooks created in the primary database are available in the standby database

Week of the Quarter, Day of the Week, Start Hour

Month of the Year, Week of the Month, Day of the Week, Start Hour

Quarter of the Year, Month of the Quarter, Date of the Month, Start Hour

Month of the Quarter, Week of the Month, Day of the Week, Start Hour

Exadata

Active Data Guard

RAC, but only when scaling beyond 16 OCPUs

Transparent Data Encryption

Multitenant

2 hours

30 minutes

1 hours

24 hours

TPPERFORMANT

MEDIUM

HIGH

LOW

TPURGENT

MODIFY_BACELINE_WINDOW_SIZE

UPDATE_OBJECT_INFO

CREATE_BASELINE_TEMPLATE

MODIFY_SNAPSHOT_SETTINGS

IOPS, Storage Space Used By Tablespace, Apply and Transport Lag

CPU Utilization, Storage Utilization

Query Latency, User Calls, Execute Count

Transaction Count, Sessions, Running Statements

Execute alter database for user MTHEO tableapace DATA quota = 10G;

Execute alter user MTHEO quota unlimited on tablespace DATA;

Execute DBMS_CLOUD_ADMIN.GRANT_TABLESPACE_QUOTA (username = MTHEO', V U tablespace_quota -> UNLIMITED');

Execute alter tablespace DATA det quota = 10G;

JDBC only

SQL*Net only

new ADB-specific protocols

any protocol supported by Oracle Net Services

MEDIUM

HIGH

TP

TPURGENT

Oracle Data Safe helps you assess the security of your cloud database configurations by analyzing database configurations

Oracle Data Safe evaluates user types, how users are authenticated, and the password policies assigned to each user

Oracle Data Safe only supports Autonomous Databases

Oracle Data Safe helps you find sensitive data in your database by inspecting the actual data in your database and its data dictionary

db-workload

is-dedicated

db-type

license-model

Click Scale Up/Down and select the Auto Scaling checkbox

Use a REST call to enable Auto Scaling

Use a REST call to shut down the instance, then a second REST call to enable Auto Scaling, and a REST all to restart the instance

Shut down the instance, click Scale Up/Down and select the Auto Scaling checkbox, then restart the instance

Create an IDCS user with the APEX role.

Access the APEX Administration Services and create the workspace for the developer.

Create a new developer account.

Create a database user with the APEX role.

Under Core Infrastructure then Compute then Autonomous Exadata

Under Solutions and Platform then Platform Services then Autonomous Exadata

Under Database then Autonomous Transaction Processing then Autonomous Exadata

Under Core Infrastructure then Autonomous Exadata

SDO_RELATE

SDO_GEOMETRY

SDO_LOCATION

GEO_JSON

Autonomous Transaction Processing

Autonomous Data Warehouse

Neither service ignores hints by default

Both services ignore hints by default