1z0-931-23 Exam Dumps - Oracle Autonomous Database Cloud 2023 Specialist

Current settings for ACLs are cloned.

Clone can be in a different region.

All OML notebooks are cloned.

All underlying data for OML notebooks is cloned.

All resource management rules are cloned.

MEDIUM

HIGH

TP

TPURGENT

120

60

15

7

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

Select the backup from which restore needs to be done.

Specify the point in time (timestamp) to restore.

Select the snapshot of the backup.

Use Recovery Manager (RMAN) to connect to Autonomous Database and back it up.

Specify the archived custom image.

A graph license key

NoSQL configuration

Graph created by a special tool downloaded from oracle.com

Graph analytics algorithms

Tables in an Autonomous Database instance

Fleet Administrator defines and gains access to the ADMIN administrative user account for the database.

Fleet administrators create, monitor and manage Autonomous Exadata Infrastructure and Autonomous Container Database resources.

Fleet Administrators are responsible for patching and backups of all container databases.

Fleet Administrators create, monitor and manage Autonomous Databases.

Business Models

Data Load

SQL Developer Web

APEX

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.

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

alter database set application_continuity=true

alter session set application_continuity=true

exec dbms_cloucl_admin. enable_app_cont ( ' ' ) ;

alter system set application_continuity=true

Oracle Machine Learning notebook

Compartment quotas

Resource Manager settings

SQL Developer Web Console

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.

Start

Update Network Access

Change administrator password

Update License Type

If a scheduled container database maintenance run cannot take place, Oracle will automatically reschedule the container database maintenance for the following quarter.

Autonomous Exadata Infrastructure maintenance takes place at least once each quarter and is mandatory.

You can change your container database maintenance window or reschedule a single container database maintenance run to ensure that your container database maintenance runs follow infrastructure maintenance within the same quarter.

Autonomous Exadata Infrastructure maintenance runs are for infrastructure patching (including patching of the Exadata grid infrastructure code and operating systems updates), and include database patching.

Database concurrency is scaled up when needed by the workload.

Increases the number of sessions available to the database.

Scales the PGA and SGA size when needed for the workload.

Enables the database to use up to 3x CPU/IO resources immediately when needed by the workload.

They continue to work

They revert to pending

They are also rotated

They become invalid

Oracle Machine Learning Zeppelin Notebook, Autonomous Exadata Infrastructure, Fleet Administrator, Database Administrator,

Virtual Cloud Network, Compartments, Policies, Autonomous Exadata Infrastructure

Autonomous Exadata Infrastructure, Autonomous Backup, Autonomous Container Database, Autonomous Database

Fleet Administrator, Database Administrator, Database User, Autonomous Exadata Infrastructure

The source file can be in either Oracle Standard Storage or Oracle Archive Storage bucket in the Object Store.

The source files can reside in Oracle Object Storage, Amazon S3 Object storage, or Azure Blob storage.

A valid credential must be created prior to running the DBMS_CLOUD.COPY_DATA procedure.

The source file will be automatically removed after the DBMS_CLOUD.COPY_DATA procedure finishes successfully.

The target table will be created in Autonomous Database if it does not already exist.

It supports only Autonomous Databases.

It helps you assess the security of your cloud database configurations by analyzing database configurations.

It helps you find and mask sensitive data in your database by inspecting the actual data in your database and its data dictionary.

It evaluates user types, how users are authenticated, and the password policies assigned to each user.

It helps you evaluate risks to data, assess user security, monitor user activity, and address data security compliance requirements.

Autonomous Transaction Processing only

ATP and ADW

Autonomous Data Warehouse only

Hybrid Columnar compression

JDBC only

SQL*Net only

new ADB-specific protocols

any protocol supported by Oracle Net Services

Undo Management

Index Storage

Memory Usage

Data Organization

Backup Retention

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

Exadata

Active Data Guard

RAC, but only when scaling beyond 16 OCPUs

Transparent Data Encryption

Multitenant

The DBMS_CLOUD.PUT_OBJECT procedure copies a file from Cloud Object Storage to the Autonomous Data Warehouse.

The DBMS_CLOUD.CREATE_CREDENTIAL procedure stores Cloud Object Storage credentials in the Autonomous Data Warehouse database.

The DBMS_CLOUD.VALIDATE_EXTERNAL_TABLE procedure validates the source files for an external table, generates log information, and stores the rows that do not match the format options specified for the external table in a badfile table on Autonomous Data Warehouse.

The DBMS_CLOUD.DELETE_FILE procedure removes the credentials file from the Autonomous Data Warehouse database.

The DBMS_CLOUD.CREATE_EXTERNAL_TABLE procedure creates an external table on files in the cloud. You can run queries on external data from the Autonomous Data Warehouse.

through the Oracle Cloud Infrastructure service console

through SQL/Developer s

using DBMS_CLOUD_ADMIN package

through SQLPIus

Fleet Administrator, Autonomous Exadata Infrastructure -> Database Administrator -> Autonomous Container DB -> Autonomous DB

Database Administrator, Autonomous Container DB -> Autonomous DB -> Fleet Administrator -> Autonomous Exadata Infrastructure

Fleet Administrator, Autonomous Exadata Infrastructure -> Autonomous Container DB -> Database Administrator -> Autonomous DB

Database Administrator, Autonomous Exadata Infrastructure -> Fleet Administrator -> Autonomous Container DB -> Autonomous DB

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

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

RPO is adjustable, but RTO I always 5 minutes

RTO and RPO are adjustable through the OCI console

RTO and RPO are 0 minutes for manual failovers

RTO is 2 minutes for an automatic failover

RPO is 0 minutes for an automatic failover

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

Trust the user who left to not access the database.

Shutdown and restart the instance.

Rotate the instance wallet and share the new wallet with the remaining users.

Delete the user.

Users can customize the OS stack and add additional packages

Users have more control over the maintenance schedule

Users have OS access to the database machine

Users are offered greater reutral and isolation starting at the Exade Cloud infrastructure level

Users have SYS privileges in the database

alter system set application_continuity=true

alter session set application_continuity-true

exec dbms_cloud admin.enable_app_cont('');

alter database set application_continuity=true

The standby database is terminated.

The standby database is also stopped.

Switchover is automatically initiated.

Failover is automatically initiated.

Oracle Key Vault, Oracle Cloud Infrastructure Vault

Oracle Database Vault, Oracle Key Vault

Oracle Audit Vault, Oracle Key Vault

Oracle Cloud Infrastructure Vault, Oracle Database Vault

Parallelism is not enabled by default.

Compression is enabled by default. Autonomous Data Warehouse uses Hybrid Columnar Compression for all tables by default.

Oracle Database Result Cache is enabled by default for all SQL statements.

You have direct access to the database node.

Create a database user (with connect, resource, object privileges), enable the schema to use SQL Developer and provide the user with the user-specific modified URL.

Create a database user with the default privileges.

Create a database user with connect, resource, and object privileges.

Create an IDCS user. Create a database user with connect, resource, and object privileges.

DBNAME_MEDIUM

DBNAME_HIGH

DBNAME_CONCURRENT

DBNAME_LOW

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

VM on Oracle Cloud Infrastructure

Bare-metal on Oracle Cloud Infrastructure

Exadata on Oracle Cloud Infrastructure

Any Oracle Engineered system

Files in Oracle Cloud Storage

Backup files in block storage

Local Files

Files in AWS S3 Storage

REST endpoints

SDO_RELATE

SDO_GEOMETRY

SDO_LOCATION

GEO_JSON

User's OCID

Tenancy's OCID

Database ADMIN password

Fingerprint of the public key

Autonomous Exadata infrastructure maintenance takes place at least once each quarter

Autonomous Exadata infrastructure maintenance runs are for infrastructure patching (including patching of the Exadata grid infrastructure code and operating systems updates) and includes container database patching

You can change your container database maintenance window or reschedule a single container database maintenance run to ensure that your container database maintenance runs follow infrastructure maintenance within the same quarter

If a scheduled container database maintenance run cannot take place, Oracle will automatically reschedules the container database maintenance for the following quarter