1z0-931-22 Oracle Autonomous Database Cloud 2022 Professional Questions and Answers

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

In-flighttransactions queries are stopped

Tools are no longer able to connect to a stopped instance

User with DWROLE can still access the database

CPU billing is halted

Under Core Infrastructure then Compute then Autonomous Exadata

Under Solutionsand Platform then Platform Services then Autonomous Exadata

Under Database then Autonomous Transaction Processing then Autonomous Exadata

Under Core Infrastructure then Autonomous Exadata

The standby database is started readwrite

The standby database is transformed in a refreshable clone

The standby database is terminated

Thestandby database is started read only

Terminate End

Maintenance Begin

Change Compartment Begin

Change Autoscaling Configuration Compartment

Update IORM Begin

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.

through the Oracle Cloud Infrastructure service console

through SQL/Developer s

using DBMS_CLOUD_ADMIN package

through SQLPIus

The Autonomous Database must be in the same VCN and Subnet as the Compute instance.

The OCI compute instance does not support connecting to a Shared Autonomous Database.

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

The OCI compute instance can be used with an Always-Free Autonomous Database account.

A Private Endpoint is required to connect to the Shared-Autonomous Database.

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.

The SQL statement completed its execution.

The SQL statement is executing.

TheSQL statement is queued.

The SQL statement did not complete either due to an error.

Autonomous Transaction Processing only

ATP and ADW

Autonomous Data Warehouse only

Hybrid Columnar compression

Scan partition tables

scan hybrid partition tables

prun column in parquet files

prun columns in csv files