Oracle 1z0-062 Oracle Database 12c: Installation and Administration Exam Practice Test

Local naming supports multiple protocols, but for any one connection, the client and server must use the same protocol.

In the Easy Connect method, clients can connect to a database server by using the host name of the database with an optional port and service name.

In the Easy Connect method, the listener port and IP address must be provided for the connection to be successful.

The local naming method does not support connect-time failover and load-balancing options.

The directory naming method supports connect-time failover and load-balancing options.

It terminates if the SYSTEM tablespace in the source database is not autoextensible.

It automatically makes necessary changes to Oracle environment variables.

It automatically enables unified auditing in the upgraded database.

It automatically adds new data files if there is not enough disk space to grow.

Resource limits specified in a profile assigned to a user are always enabled.

A user can exist without any profile.

A profile can be assigned only to one user.

Password management using profiles is always enabled.

All system triggers are disabled during the upgrade process.

Only queries on fixed views execute without errors until you run the catctl.pl script.

The COMPATIBLE parameter must be set to at least 12.1.0 before issuing the command.

All job queues remain active during the upgrade process.

Only connections AS SYSDBA are allowed during the upgrade process.

The backup can be used as an incremental level 0 backup.

The database instance must be shut down to take the backup.

The database must be in MOUNT state to take the backup.

The backup consists of blocks that have been formatted.

The system Change Number (SCN) is the same for all the data files in the backup.

Oracle Data Pump export and import operations can be performed to move data across different database releases.

DBMS_DATAPUMP PL/SQL packages can be used independent of Data Pump clients.

A directory object must exist and a user performing an EXPDP or IMPDP operation must have read and write permission on that directory object.

Oracle Data Pump export and import operations can be performed only by users with the SYSDBA privilege.

Oracle Data Pump export operations invoked from the clients that are connected remotely by using a connection string, create Data Pump files on the client file system.

It prompts the Checkpoint (CKPT) process to write data to the data files and redo information to the online redo log files.

It ensures that all dirty buffers are written to data files during consistent shutdown.

It reduces the time required for recovery in case of an instance failure.

Frequent thread checkpoints can degrade database performance.

It prompts the Database Writer (DBWn) process to write checkpoint information into data file headers and the control file.

An AWR snapshot shows the SQL statements that are producing the highest load on the system, based on criteria such as elapsed time and CPU time.

AWR data is stored in memory and in a database.

All AWR tables belong to the SYSTEM schema.

The manageability monitor (MMON) process gathers statistics and creates an AWR snapshot that is used by the self-tuning components in a database.

An AWR snapshot contains system-wide tracing and logging information.

creation of SQL plan baselines

creation of SQL profiles

creation of materialized views

creation of indexes

rewriting of SQL statements

Optimizer statistics are collected automatically.

Only timed operating system (OS) statistics and plan execution statistics are collected.

Automatic Workload Repository (AWR) snapshots are not generated automatically.

The Oracle server dynamically generates the necessary object-level statistics on tables as part of query optimization.

The values assigned to the resource limits and password parameters in the default profile can be altered.

A different DEFAULT profile can be created before each user in a database.

It can be dropped and recreated.

it must be explicitly assigned to the user.

A resource plan change can be automated by using the Oracle Scheduler.

It can be used to control the consumption of only physical I/Os where excessive physical I/Os can trigger an automatic session termination but excessive logical I/Os cannot.

It can be used to control the usage of the undo tablespace by consumer groups.

A resource plan can have multiple resource plan directives, each of which controls resource allocation for a different consumer group.

It can be used to enable resumable timeout for user sessions.

It can be used to control the usage of the temp tablespace by consumer groups.

RMAN backups contain only data files.

The database instance must be shut down to take a user-managed consistent backup.

Consistent RMAN backups can be taken while the database is open.

User-managed backups only contain formatted data blocks.

The database must be in MOUNT state to take consistent RMAN backups.

loss of all the copies of the control file

loss of all the inactive online redo log group members

loss of a data file that belongs to the active undo tablespace

loss of data files that belong to the SYSTEM tablespace

logical corruption of data that is caused by a wrong transaction

abnormal termination of the database instance

when there are multiple undo tablespaces available in a database

when the data file of the undo tablespace is autoextensible

when the undo tablespace is of a fixed size and retention guarantee is not enabled

when Flashback Database is enabled

A pre-existing Oracle Net Listener

Oracle Notification services

A pre-existing database

A pre-existing Oracle management agent

Oracle CSSD service

A listener may listen on behalf of only one database instance at a time.

A server process checks a user’s authentication credentials and creates a session if the credentials are valid.

The listener continuously monitors a connection after the user process connects to a service handler.

The listener always spawns a new server process to deal with each new connection.

A connection request from a client is always first received by a listener running on the port that is used for the connection request for the database server.

Use DBCA to create a template from the existing database to contain the database structure and then manually copy the data by using Oracle Data Pump.

Use Database Configuration Assistant (DBCA) to create a template from the existing database to contain the database structure.

Create the database by using the CREATE DATAEASE. . . command and manually import data by using Data Pump.

Use DBCA to create a template from the existing database to contain the database structure with data files and then use the same template to create the database in the new location.

Automatic Database Diagnostic Monitor

Optimizer statistics gathering

SQL Access Advisor

Segment Advisor

Automatic SQL Tuning Advisor

Flashback logs are written sequentially, and are archived.

Flashback Database uses a restored control file to recover a database.

The Oracle database automatically creates, deletes, and resides flashback logs in the Fast Recovery Area.

Flashback Database can recover a database to the state that it was in before a reset logs operation.

Flashback Database can recover a data file that was dropped during the span of time of the flashback.

Flashback logs are used to restore to the blocks' before images, and then the redo data may be used to roll forward to the desired flashback time.

The optimizer automatically changes a plan during subsequent execution of a SQL statement if there is a huge difference in optimizer estimates and execution statistics.

The optimizer can re optimize a query only once using cardinality feedback.

The optimizer enables monitoring for cardinality feedback after the first execution of a query.

The optimizer does not monitor cardinality feedback if dynamic sampling and multicolumn statistics are enabled.

After the optimizer identifies a query as a re-optimization candidate, statistics collected by the collectors are submitted to the optimizer.

It succeeds because the PDB_ADMIN user has the required privileges.

It fails because common users are unable to use the SET CONTAINER statement.

It fails because local users are unable to use the SET CONTAINER statement.

If fails because the SET CONTAINER statement cannot be used with PDB$SEED as the target pluggable database (PDB).

1, 3, 2, 6, 7, 4, 5

1, 3, 7, 2, 6, 4, 5

1, 3, 2, 4, 5

1, 2, 6, 4, 5

1, 6, 2, 4, 5

Apply fine-grained auditing.

Implement value-based auditing.

Impose standard database auditing to audit object privileges.

Impose standard database auditing to audit SQL statements.

Space utilization inside segments is mapped by bitmaps.

Segments are automatically shrunk and compressed when rows are deleted.

The PCTFREE storage parameter has no effect on segments created in this tablespace.

The PCTUSED storage parameter has no effect on segments created in this tablespace.

Database operations will be monitored only when they consume a significant amount of resource.

Database operations for all sessions will be monitored.

Database operations will be monitored only if the STATISTICS_LEVEL parameter is set to TYPICAL and CONTROL_MANAGEMENT_PACK_ACCESS is set DIAGNISTIC + TUNING.

Only DML and DDL statements will be monitored for the session.

All subsequent statements in the session will be treated as one database operation and will be monitored.

6, 5, 4, 7

10, 1, 2, 5, 8

10, 1, 2, 5, 4, 9, 8

10, 1, 5, 8, 10

online redo log files

control file

SPFILE

archived redo log files

data file(s)

PFILE

Alerts are issued only when the critical threshold for space available in a tablespace is breached.

The sum of active extents and allocated user quotas is considered to compute space usage for an undo tablespace.

Database alerts can provide warnings about low space availability at both tablespace and segment levels.

Alerts are not issued for locally managed tablespaces that are offline or in read-only mode.

A newly created locally managed tablespace is automatically assigned the default threshold values defined for a database.

By default, EM express is available for a database after database creation.

You can use EM express to manage multiple databases running on the same server.

You can perform basic administrative tasks for pluggable databases by using the EM express interface.

You cannot start up or shut down a database Instance by using EM express.

You can create and configure pluggable databases by using EM express.

It generates a script to recompile invalid objects post-upgrade.

The preupgrade_fixups.sql script is created to list and describe issues in the source database.

A log file, preupgrade.log, is created that contains the output of the Pre-Upgrade Information tool.

It checks for required tablespaces and if they are not available, creates them automatically.

The preupgrade_fixups.sql script is executed automatically to fix issues in the source database.

The postupgrade_fixups.sql script is created to address issues that can be fixed after a database has been upgraded.

Transactions and queries accessing database objects contained in any tablespace stored in DGROUP1 will fall.

Mirroring of allocation units will be done to ASM disks in the CONTROLLER2 failure group until the CONTROLLER1 for failure group is brought back online.

The data in the CONTROLLER1 failure group is copied to the controller2 failure group and rebalancing is initiated.

ASM does not mirror any data until the controller failure group is brought back online, and newly allocated primary allocation units (AU) are stored in the controller2 failure group, without mirroring.

Transactions accessing database objects contained in any tablespace stored in DGROUP1 will fail but queries will succeed.

Only the data definition language (DDL) commands that resulted in errors are logged in the alert log file.

All DDL commands are logged in the alert log file.

All DDL commands are logged in a different log file that contains DDL statements and their execution dates.

Only DDL commands that resulted in the creation of new segments are logged.

All DDL commands are logged in XML format in the alert directory under the Automatic Diagnostic Repository (ADR) home.

The MRKT tablespace is created as a small file tablespace, because the file size is less than the minimum required for big file files.

The MRKT tablespace may be dropped if it has no contents.

Users who were using the old default tablespace will have their default tablespaces changed to the MRKT tablespace.

No more data files can be added to the tablespace.

The relative file number of the tablespace is not stored in rowids for the table rows that are stored in the MRKT tablespace.

It records usernames and passwords of users when granted the DBA role

It contains usernames and passwords of users for whom auditing is enabled

It is used by Oracle to authenticate users for remote database administrator

It records usernames and passwords of all users when they are added to OSDBA or OSOPER operating groups

It fails because the DELETE INPUT option can be used only with the BACKUP AS BACKUPSET command.

It executes successfully and creates a backup set of the database along with archived log files and then deletes the original archived log files.

It executes successfully and creates an image copy of the database along with archive log files and then deletes the original archived log files.

It fails because the DELETE INPUT option can be used only with the BACKUP AS COPY command.

BACKUP TABLESPACE SYSTEM SECTION SIZE 100M;

BACKUP AS COPY TABLESPACE SYSTEM SECTION SIZE 100M;

BACKUP ARCHIVELOG ALL SECTION SIZE 25M;

BACKUP TABLESPACE "TEMP" SECTION SIZE 10M;

BACKUP TABLESPACE "UNDO" INCLUDE CURRENT CONTROLFILE SECTION SIZE 100M;

BACKUP SPFILE SECTION SIZE 1M;

BACKUP INCREMENTAL LEVEL 0 TABLESPACE SYSAUX SECTION SIZE 100M;

Transactions write their undo in the SYSTEM undo segment.

Transactions fail.

Transactions wait until space becomes available in UNDOTBS1.

Transactions write their undo in a temporary tablespace.

If no PDB plan is enabled for a pluggable database, then all sessions for that PDB are treated to an equal degree of the resource share of that PDB.

In a PDB plan, subplans may be used with up to eight consumer groups.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups across all PDBs in the CDB.

If no PDB plan is enabled for a pluggable database, then the PDB share in the CDB plan is dynamically calculated.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups based on the shares provided to the PDB in the CDB plan and the shares provided to the consumer groups in the PDB plan.

SPFILEs and PFILEs may both be edited with an O/S editing utility

Some SPFILE parameters can be modified successfully with the SCOPE=MEMORY clause

A SPFILE can be created by an idle instance

A PFILE can be created by an idle instance

All SPFILE parameters can be modified successfully with the SCOPE=BOTH clause

All SPFILE parameters can be modified successfully with the SCOPE=MEMORY clause

It can contain a nested chain of jobs.

It can be used to implement dependency-based scheduling.

It cannot invoke the same program or nested chain in multiple steps in the chain.

It cannot have more than one dependency.

It can be executed using event-based or time-based schedules.

1, 2, 3, 4, 6

2, 5, 1, 6

4, 2, 5, 1, 6

2, 3, 1, 6

The create user command fails if any role with the name Sidney exists in the database.

The user Sidney can connect to the database instance but cannot perform sort operations because no space quota is specified for the temp tablespace.

The user Sidney is created but cannot connect to the database instance because no profile is default.

The user Sidney can connect to the database instance but requires relevant privileges to create objects in the users tablespace.

The user Sidney is created and authenticated by the operating system.

CREATE DATABASE LINK HQ USING 'HQ';

CREATE DATABASE LINK HQ CONNECT TO CURRENT_USER USING ‘HQ’;

CREATE PUBLIC DATABASE LINK HQ CONNECT TO scott IDENTIFIED BY tiger USING 'HQ';

CREATE DATABASE LINK HQ CONNECT TO scott IDENTIFIED BY tiger USING 'HQ';

OMF cannot be used in a database that already has data files created with user-specified directions.

The file system directions that are specified by OMF parameters are created automatically.

OMF can be used with ASM disk groups, as well as with raw devices, for better file management.

OMF automatically creates unique file names for table spaces and control files.

OMF may affect the location of the redo log files and archived log files.

It fails because the DB_8K_CACHE_SIZE parameter cannot be changed dynamically.

It succeeds only if memory is available from the autotuned components if SGA.

It fails because an increase in DB_8K_CACHE_SIZE cannot be accommodated within SGA_TARGET.

It fails because an increase in DB_8K_CACHE_SIZE cannot be accommodated within SGA_MAX_SIZE.

It checks the database for intrablock corruptions.

It can detect corrupt pfiles.

It can detect corrupt spfiles.

It checks the database for interblock corruptions.

It can detect corrupt block change tracking files.

Increasing the priority of the job class to which the job belongs

Increasing the job's relative priority within the Job class to which it belongs

Increasing the resource allocation for the consumer group mapped to the scheduler job's job class within the plan mapped to the scheduler window

Moving the job to an existing higher priority scheduler window with the same schedule and duration

Increasing the value of the JOB_QUEUE_PROCESSES parameter

Increasing the priority of the scheduler window to which the job belongs

It will create a multitenant container database (CDB) with only the root opened.

It will create a CDB with root opened and seed read only.

It will create a CDB with root and seed opened and one PDB mounted.

It will create a CDB that must be plugged into an existing CDB.

It will create a CDB with root opened and seed mounted.

Row movement is enabled.

Referential integrity constraints for the table are disabled.

No queries are running on this table.

Extra disk space equivalent to the size of the segment is available in the tablespace.

No pending transaction exists on the table.

The PDB must be open in read only mode.

The PDB must be dosed.

The unplugged PDB becomes a non-CDB.

The unplugged PDB can be plugged into the same multitenant container database (CDB)

The unplugged PDB can be plugged into another CDB.

The PDB data files are automatically removed from disk.

An attempt to start a new session by a user belonging to DSS_QUERIES fails with an error.

An attempt to start a new session by a user belonging to OTHER_GROUPS fails with an error.

The CPU_WAIT_TIME column indicates the total time that sessions in the consumer group waited for the CPU due to resource management.

The CPU_WAIT_TIME column indicates the total time that sessions in the consumer group waited for the CPU due to I/O waits and latch or enqueue contention.

A user belonging to the DSS__QUERIES resource consumer group can create a new session but the session will be queued.

All users except SYS

All users except SCOTT

All users except sys and SCOTT

All users except sys, system, and SCOTT

Transportable database

Transportable tablespace

Data Pump full export/import

The DBMS_PDB package

RMAN

Parallel compilation of only the stored PL/SQL code

Sequential recompilation of only the stored PL/SQL code

Parallel recompilation of any stored PL/SQL code

Sequential recompilation of any stored PL/SQL code

Parallel recompilation of Java code

Sequential recompilation of Java code

You can conned as a common user by using the connect statement.

You can connect as a local user by using the connect statement.

You can connect by using easy connect.

You can connect by using OS authentication.

You can connect by using a Net Service name.

You can connect as a local user by using the SET CONTAINER statement.