1z0-931-23 Sample Questions Answers

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

Only ATP manages optimizer statistics.

Only ATP supports automatic backups.

Only ADW uses columnar compression by default.

Only ADW supports autoscaling.

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

JSON data is stored natively in the database

You can promote Autonomous JSON Database to Autonomous Transaction /Processing

It supports NoSQL-style, document-centric application

There is a 20 GB limit on JSON collection

Files in Oracle Cloud Storage

Backup files in block storage

Local Files

Files in AWS S3 Storage

REST endpoints

Use SFTP to copy CSV files into Autonomous Database

Use Oracle Zero Downtime Migration (ZDM)

Use Recovery Manager (RMAN)

Use GoldenGate

Use Data Pump

Oracle Cloud Infrastructure console using the JSON Online Developer tool

Oracle JSON Developer tool downloaded from OTN

NOSQL statements using Oracle SODA drivers

REST API calls to the database (not enabled by default)

Regular Oracle SQL statements using a connection through the listener

Quotas set on a parent compartment override quotas set on child compartments.

Compartment quotas cannot be set on the root compartment.

Compartment quotas use policies that allow allocation of resources with a high level of flexibility.

You cannot manage quotas in a compartment, unless you belong to a group that has the correct permissions.

TPPERFORMANT

MEDIUM

HIGH

LOW

TPURGENT

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

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

An "INSERT" REST call

A "GET" REST call

A "POST" REST call

A "PUT" REST call

licence-model

db-workload

is-dedicaced

db-type

MEDIUM

HIGH

TP

TPURGENT

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.

Parquet

DOC

DDL

JSON

CSV

AVRO

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'

DOC

AVRO

JSON

DDL

Dcsv

Parquet

VM on Oracle Cloud Infrastructure

Bare-metal on Oracle Cloud Infrastructure

Exadata on Oracle Cloud Infrastructure

Any Oracle Engineered system

ODI Web Edition is available only on Oracle Linux.

ODI Web Edition can be installed from Oracle Cloud Infrastructure (OCI) Marketplace.

The Data Transforms Card provides access to Oracle Data Integrator (ODI) Web Edition.

All of the capabilities of ODI Classic are available with ODI Web Edition,

Business Models

APEX

SQL Developer Web

Data Load

3-D modelling

Churn analysis

Pattern matching

Facial recognition

Clustering

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

The Autonomous Database must belong to a Network Security Group (NSG).

A Private Endpoint is required to connect to the Autonomous Database on shared Exadata infrastructure.

The marketplace OCI image does not support connecting to an Autonomous Database on Shared Infrastructure.

The marketplace OCI image can be used with an Always Free Autonomous Database account.

The Autonomous Database can only be in the same virtual cloud network (VCN) and subnet as the marketplace OCI image.

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

SQLDEV_ADMIN.GRANT_SCHEMA

ORDS_ADMIN.ENABLE_SCHEMA

ORDS_ADMIN.GRANT_SCHEMA

ORDS_PRIV.ENABLE_SCHEMA

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.

Tablespaces

Reports

Schemas

Data

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

900

1800

2700

1500

Oracle Cloud Infrastructure Object Storage

Google Cloud Storage

Amazon S3

Azure Blob Storage

Oracle Cloud Infrastructure Object Storage Classic

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

24 hrs

2 hrs

5 min

1 day

Exadata

Active Data Guard

RAC, but only when scaling beyond 16 OCPUs

Transparent Data Encryption

Multitenant

Undo Management

Index Storage

Memory Usage

Data Organization

Backup Retention

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

RMAN backup & restore

Physical migration methods, such as database cloning

Orace Zero Downtime Migration (ZDM)

Original imp/exp tools

Oracle Data Pump

Oracle Golden Gate

Compute Image and Shared ADB must be in same VCN and Subnet

ADB must be configured with NSG

ADB must be configured with Private endpoints

Cannot connect OCI Market image to shared ADB

For databases on dedicated Exadata infrastructure, the maximum number of cores is limited by the number of free cores that aren't being used by other auto scaling databases to meet high-load demands.

The base number of OCPU cores allocated to a database is not guaranteed.

For databases on dedicated Exadata infrastructure, the maximum number of cores available to a database depends on the total number of cores available in the Exadata infrastructure instance.

Auto scaling is enabled by default and can be enabled or disabled at any time.

Data Insights

JSON

Catalog

Data Load

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.

Increasing OCPUs will automatically increase storage

OCPUs and storage must remain in sync

OCPUs and storage can be scaled independently

Use auto scaling to increase storage

through the Oracle Cloud Infrastructure service console

through SQL/Developer s

using DBMS_CLOUD_ADMIN package

through SQLPIus

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

There are three types of quota policy statements which are set, unset and zero.

Compartment quotas use policies that allow allocation of resources with a high level of flexibility.

Along with compartment budgets, compartment quotas create a powerful toolset to manage your spending.

Compartment quotas are set by Oracle.

You can perform a "rolling restart" on all the Autonomous Databases. During a rolling restart, each node of an Autonomous Database is restarted separately while the remaining nodes continue to be available

You can skip a scheduled maintenance run. For Autonomous Databases on Shared Infrastructure, you can skip maintenance runs for up to two consecutive quarters if needed

You cannot configure the scheduling for your Autonomous Databases on Shared Infrastructure

You can choose to use Release Update (RU) or Release Update Revision (RUR) updates for your Autonomous Databases on Shared Infrastructure

Oracle Database licenses

Autonomous Container Database

Network Security Group(s)

Virtual Cloud Network and Subnet

Identity and Access Management (IAM) policy rules that allow access to the database

Autonomous Exadata Infrastructure

Autonomous Database instance

You can call PL/SQL procedures and functions by using a database link

You can connect to an Autonomous Database from a remote database using a database link

You can create a database link from one Autonomous Database to another Autonomous Database instance

You can connect to a remote database from an Autonomous Database by using a database line

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

Autonomous Transaction Processing only

ATP and ADW

Autonomous Data Warehouse only

Hybrid Columnar compression

Access to Database Actions is available for all users of Autonomous Database.

Oracle Machine Learning is available only with Autonomous Data Warehouse (ADW) Database.

SQL Developer Web is available exclusively on the Autonomous Database.

Database Actions is accessible from a server running on the same virtual cloud network (VCN) when the Autonomous Database is configured with Private Endpoint networking.

Oracle APEX can be accessed only from the Developer menu in the Service Console.