Oracle 1z0-082 Oracle Database Administration I Exam Practice Test

the first column in the first select of the compound query

the first varchab2 column in the first select of the compound query

the first number column in the first select of the compound query

the first number or varchar2 column in the last select of the compound query

the first column in the last select of the compound query

analysis of all privileges used by all users including administrative users in the database

analysis of all privileges used by all users but excluding administrative users in the database

analysis of privileges that a user has on their own schema objects that they did not use

analysis of privileges that a user has on their own schema objects that they did use

analysis of privileges granted directly to a role that are then used by a user who has been granted that role

analysis of privileges granted indirectly to a role that are then used by a user who has been granted that role

A synonym has an object number.

A synonym can be created on an object in a package.

A synonym can have a synonym.

All private synonym names must be unique in the database.

Any user can create a PUBLIC synonym.

dump files

control files

password files

bad files

input files

They can be written by server processes

Trace files are written to the Fast Recovery Area (FRA)

They can be written by background processes

All trace files contain error information that require contacting Oracle Support

Trace file names are based on the database name concatenated with a sequential number

in the SPFILE, SPFILE, and memory

in the SPFILE and in memory

only In the SPFILE

in the SPFILE and SPFILEc

only in memory

The command succeeds and HR will be connected to the orcl and abc.sql databases

The command succeeds and HR will be connected to the orcl database instance, and the abc.sql script will be executed

The command fails because the script must refer to the full path name

The command fails and reports an error because @ is used twice

Aggregate functions can be nested to any number of levels

The AVG function implicitly converts NULLS to zero

Aggregate functions can be used in any clause of a SELECT statement

The MAX and MIN functions can be used on columns with character data types

The value is changed only in the PFILE and takes effect at the next instance startup

The value is changed for the current instance and in the PFILE

It fails because the SCOPE clause is missing

Change is applied to the current instance, but does not persist after instance restart

Private Temporary Tables (PTTS) store metadata in memory only

An index created with the UNUSABLE attribute has no segment

If they exist for a session, Private Temporary Tables (PTTs) are always dropped at the next COMMIT OR ROLLBACK statement

An index that is altered to be UNUSABLE will retain its segment

A table that is truncated will always have its segment removed

undo

index

stored procedures

sequences

tables

clusters

The CURRENT_TIMESTAMP function returns data without time zone information

A TIMESTAMP WITH LOCAL TIMEZONE data type column is stored in the database using the time zone of the session that inserted the row

A TIMESTAMP data type column contains information about year, month, and day

The DBTIMEZONE function can return an offset from Universal Coordinated Time (UTC)

The SESSIONTIMEZONE function can return an offset from Universal Coordinated Time (UTC)

Multiple INTERSECT operators are not possible in the same SQL statement

It processes NULLs in the selected columns

INTERSECT is of lower precedence than UNION or UNION ALL

It ignores NULLs

Oracle Managed Files (OMF)

Online table segment shrink

Online index segment shrink

Automatic data file extension (AUTOEXTEND)

Capacity planning growth reports based on historical data in the Automatic Workload Repository (AWR)

Data block headers contain their own Data Block Address (DBA)

A table row piece can be chained across several database blocks

Multiple row pieces from the same row may be stored in different database blocks

Multiple row pieces from the same row may be stored in the same block

Data block free space is always contiguous in the middle of the block

Index block free space is always contiguous in the middle of the block

Data dictionary views are created by joins of dictionary base tables and DBA-defined tables

The data dictionary is created and maintained by the database administrator

Views with the same name but different prefixes, such as CDB, DBA, ALL and USER, reference the same base tables from the data dictionary

Base tables can be queried directly

It is owned by the SYSTEM user

Usernames of all users including database administrators are stored in the data dictionary

INTERSECT

UNION ALL

UNION

SUBTRACT

MINUS

They can be used only in the WHERE clause of a SELECT statement

The argument can be a column name, variable, literal or an expression

The data type returned can be different from the data type of the argument

They can be nested to any level

They can accept only one argument

They return a single result row per table

SELECT NVL(cust_credit_limit * .15, ‘Not Available’) FROM customers;

SELECT NVL2(cust_credit_limit * .15, ‘Not Available’) FROM customers;

SELECT NVL(TO_CHAR(cust_credit_limit * .15), ‘Not Available’) FROM customers;

SELECT TO_CHAR(NVL(cust_credit_limit * .15, ‘Not Available’)) FROM customers;

SELECT NVL2(cust_credit_limit, TO_CHAR(cust_credit_limit * .15), ‘Not Available’) FROM customers;

Dynamic service registration cannot be used for this database instance

The LREG process registers services dynamically with the LISTENER_1 listener

LISTENER_1 must also be defined in the LISTENER.ORA file to enable dynamic service registration

There are two listeners named LISTENER and LISTENER_1 running simultaneously using port 1521 on the same host as the database instances

The definition for LISTENER_1 requires a CONNECT_DATA section to enable dynamic service registration

SELECT &&col1, &&col2FROM &tableWHERE &&condition = &&cond;

SELECT &col1, &col2FROM &&tableWHERE &condition;

SELECT &col1, &col2FROM “&table”WHERE &condition;

SELECT ‘&&col1’, ‘&&col2’FROM &tableWHERE ‘&&condition’ = ‘&cond’;

SELECT &&col1, &&col2FROM &tableWHERE &&condition;