1z0-497 Exam Dumps - Oracle Database 12c Essentials

When a role is granted to a user, the privileges in the role are limited to the context of the PDB.

Local roles can be granted only to local users.

Common roles can be granted to both local and common users.

A user can create common roles if the user has the CREATE ROLE privilege, and SET CONTAINER for all PDBs

Common roles can be created in the root and PDBs.

A common user cannot have the same name as any local user across all PDBs.

A common user can be created only in the root container.

A local user with the proper privileges can also create a common user.

If a PDB is closed, the common and local users of the PDB are not visible.

A common user with the proper privileges can create a common user by using the CONTAINER=CURRENT clause.

A common user is one that has the same username and authentication credentials across multiple PDBs.

It contains three global service managers in the client's local region (east).

Client-side load balancing has been enabled only for the global service managers within the client's buddy (west).

Connect-time failover between regions has not been enabled.

The REGION parameter is optional.

Asynchronous redo transport with Data Guard

Synchronous redo transport with Data Guard

Active Data Guard Far Sync

Data Guard SQL Apply

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement with the FINISH keyword

ALTER DATABASE PREPARE TO SWITCHOVER and ALTER DATABASE COMMIT TO SWITCHOVER statements

ALTER DATABASE RECOVER TO STANDBY DATABASE statement with the FINISH keyword

D) ALTER DATABASE PREPARE SWITCHOVER and ALTER DATABASE COMMIT TO SWITCHOVER Statements

shared UNDO and default database temporary tablespace

Oracle-supplied metadata

shared Oracle-supplied data

CDB views providing information across PDBs

application tablespaces

local temporary tablespaces

local users and local roles

You can unplug a PDB from a development CDB and plug it into a production CDB, which allows for easier and more rapid movement of data and code.

You can consolidate shared database memory by combining multiple PDBs in a single CDB.

Patching individual PDBs requires the same amount of time as patching individual databases.

Consolidating separate databases into a single CDB requires the same amount of storage allocation.

In multitenant architecture, a PDB behaves the same as a non-CDB as seen from a client connecting with Oracle Net. No client modification is required.

database backup and recovery using RMAN

performance tuning operations such as generation of AWR, ADDM, and ASH reports

storage configuration for archive logs and control files

storage configuration for data files and redo log groups

database status view and Data Pump export and import jobs

The database advances a checkpoint.

A client process commits a transaction.

The redo log buffer becomes full.

A server process cannot find non-dirty blocks after scanning a threshold number of buffers.

A tablespace is changed to read-only status.

The database is shut down in immediate mode.

The analyzed result is lost when the database instance is restarted.

It runs every 1 hour automatically.

It is shipped only with Oracle Enterprise Manager 12c.

It analyzes high CPU trend and identifies problems before they can threaten application performance.

USERS

TEMP

SYSAUX

SYSTEM

EXAMPLE

The session is terminated after receiving the error and JIM can continue with his transaction.

SCOTT should perform a COMMIT or ROLLBACK to allow JIM to continue with his transaction.

The session is rolled back after receiving the error and JIM can continue with his transaction.

SCOTT has to re-execute the last command in the transaction after he commits the transaction.

Option A

Option B

Option C

Option D

Option E

Real-Time ADDM uses AWR snapshots of the last 10 minutes.

Real-Time ADDM uses ASH recent activity from SGA data.

Real-Time ADDM analyzes performance in a completely different fashion than regular ADDM.

Regular ADDM uses AWR snapshots that are not yet purged.

Extend the logical volume by 10 MB where the data files are stored;

# lvextend -L+10M /diskl

Add a data file:

SQL>ALTER TABLESPACE MYTBS ADD DATAFILE ' /disk1/mytbs_2 .dbf SIZE 10M;

Move a partition to another tablespace:

SQL> CREATE TABLESPACE ADDITIONAL_TBS DATAFILE '/disk1/additional_tbs_1 .dbf' SIZE 10M;

SQL> ALTER TABLE MYTAB MOVE PARTITION P2 TABLESPACE ADDlTIONAL_TBS;

Resize the existing data file:

SQL> ALTER DATABASE DATAFILE '/diskl/mytbs_l .dbf' RESIZE 20M;

E) Remove a data file:

SQL> ALTER TABLESPACE MYTBS DROP DATAFILE '/diskl/mytbs_l - dbf';

only from the server, if the database instance is not up

from either a client or server, even if the database instance is not up

from either a client or server, only if the database instance is up, and the command connects the session to the instance

from either a client or server, only if the database instance is up, but the command does not connect the session to the instance

The database is open and registered with a global service manager.

The service has been disabled on that database.

The database role is different from the role attribute of the service.

The replication lag on the database does not exceed the maximum value specified for the service.

The service has reached its cardinality defined by the number of preferred databases.

No other database in the pool is a better candidate for starting the service.

recompile it

rewrite its SQL queries

relink

rework the applications schema

nothing; it is transparent

It transparently encrypts data at rest in Oracle databases.

It securely manages encryption keys.

It protects against theft or loss of disks and backups.

It prevents OS users from inspecting tablespace files.

It limits the exposure of sensitive data in applications.

It alters data in caches, buffers, and persistent storage.

It impacts operational activities such as backup & restore, upgrade & patch, and replication.