1z0-060 Practice Exam Questions with Answers Upgrade to Oracle Database 12c Certification

Place CDB1 in the mount stage and then take the USERDATA tablespace offline in ACCOUNTS_PDB.

Place CDB1 in the mount stage and issue the ALTER PLUGGABLE DATABASE accounts_pdb CLOSE IMMEDIATE command.

Issue the ALTER PLUGGABLE DATABASE accounts_pdb OPEN RESTRICTED command.

Take the USERDATA tablespace offline in ACCOUNTS_PDB.

Use the MD_RESTORE command to restore metadata for an existing disk group by passing the existing disk group name as an input parameter and use RMAN to restore the data.

Use the MKDG command to restore the disk group with the same configuration as the backed-up disk group and data on the disk group.

Use the MD_RESTORE command to restore the disk group with the changed disk group specification, failure group specification, name, and other attributes and use RMAN to restore the data.

Use the MKDG command to restore the disk group with the same configuration as the backed-up disk group name and same set of disks and failure group configuration, and use RMAN to restore the data.

Use the MD_RESTORE command to restore both the metadata and data for the failed disk group.

Use the MKDG command to add a new disk group DG1 with the same or different specifications for failure group and other attributes and use RMAN to restore the data.

The ORACLE_BASE base parameter is not set.

The installation is being performed by the root user.

The operating system group that is specified should have the root user as its member.

The operating system group that is specified must have permission to write to the inventory directory.

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

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 to DIAGNOSTIC+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.

The procedures may be used for some components to relocate component data to the SYSAUX tablespace from its current tablespace.

The procedures may be used for some components to relocate component data from the SYSAUX tablespace to another tablespace.

All the components may be moved into the SYSAUX tablespace.

All the components may be moved from the SYSAUX tablespace.

All the triggers for the table are disabled without changing any of the column names or column types in the table.

The primary key constraint on the EMPLOYEES table is disabled during redefinition.

VPD policies are copied from the original table to the new table during online redefinition.

You must copy the VPD policies manually from the original table to the new table during online redefinition.

Create the CREATE_TEST procedure with definer’s rights.

Grant the EXECUTE privilege to users with GRANT OPTION on the CREATE_TEST procedure.

Create the CREATE_TEST procedure with invoker’s rights.

Create the CREATE_TEST procedure as part of a package and grant users the EXECUTE privilege the package.

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

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

It is used by Oracle to authenticate users for remote database administration.

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

It supports the SYSBACKUP, SYSDG, and SYSKM system privileges.

It executes successfully and creates an UNDO tablespace in HR_PDB.

It fails and reports an error because there can be only one UNDO tablespace in a CDB.

It fails and reports an error because the CONTAINER=ALL clause is not specified in the command.

It fails and reports an error because the CONTAINER=CURRENT clause is not specified in the command.

It executes successfully but neither tablespace nor the data file is created.

ASM disk groups with ASM disks consisting of Exadata Grid Disks.

ASM disk groups with ASM disks consisting of LUNs on any Storage Area Network array

ASM disk groups with ASM disks consisting of any zero-padded NFS-mounted files

Database files stored in ZFS and accessed using conventional NFS mounts.

Database files stored in ZFS and accessed using the Oracle Direct NFS feature

Database files stored in any file system and accessed using the Oracle Direct NFS feature

ASM disk groups with ASM disks consisting of LUNs on Pillar Axiom Storage arrays

The movement of all segments to a target tablespace with a higher degree of compression, on a different storage tier, when the source tablespace exceeds TBS PERCENT USED

The movement of some blocks to a target tablespace with a lower degree of compression, on a different storage tier, when the source tablespace exceeds TBS PERCENT USED

The movement of some segments to a target tablespace with a higher degree of compression, on a different storage tier, when the source tablespace exceeds TBS PERCENT USED

Setting the target tablespace to read-only after the segments are moved

Taking the target tablespace offline after the segments are moved

when a registered database is opened with the resetlogs option

when the backup retention policy configuration is changed for a registered database

when a redo log Is archived

when a manual redo log switch is performed

when backup metadata records are aged out of the control file based on the control_file_record_keep_time parameter value

The backup succeeds and all the data files belonging to both the root container and pdb2_i are backed up.

The backup falls because the root container cannot be backed up with pdb2_i.

The backup succeeds, but only the system and sysaux tablespaces in the root container are backed up along with all the data files in pdb2_i.

The backup fails because pdb2_1 should be placed in the mount stage.

Oracle Data Pump

An ALTER TABLE MOVE to move the table and ALTER INDEX REBUILD to move the indexes.

An ALTER TABLE MOVE to move the table and ALTER INDEX REBUILD ONLINE to move the indexes

Online Table Redefinition

Edition-Based Table Redefinition

Schema objects owned by the C# # A_ADMIN common user can be shared across all PDBs.

The C##A_ADMIN user will be able to use the TEMP_TS temporary tablespace only in root.

The command will create a common user whose description is contained in the root and each PDB.

The schema for the common user C # # A_ADMIN can be different in each container.

The command will create a user in the root container only because the CONTAINER clause is not used.

Use the MD_RESTORE command to restore metadata for an existing disk group by passing the existing disk group name as input parameter and use RMAN to restore the data.

Use the MKDG command to restore the disk group with the same configuration as the backed-up disk group and data on the disk group.

Use the MD_RESTORE command to restore the disk group with the changed disk group specification, failure group specification, name, and other attributes and use RMAN to restore the data.

Use the MD_RESTORE command to restore both the metadata and data for the failed disk group.

Use the MKDG command to add a new disk group DG1 with the same or different specifications for failure group and other attributes and use RMAN to restore the data.

setting the PGA_AGGREGATE_TARGET parameter to 200M and the SGA_MAX_SIZE parameter to 400M

setting the MEMORY_TARGET and SGA_MAX_SIZE parameters to 400M

setting the SGA_TARGET parameter to 300M

setting the SGA_MAX_SIZE parameter to 400M

FULL redaction is active on the SAL column

RANDOM redaction is active on the MGR column

RANDOM redaction is active on the HIREDATE column

PARTIAL redaction is active on the MGR column.

PARTIAL redaction is active of the HIREDATE column.

It returns an error because the table name in the object_name column is not specified.

It retrieves the least recently dropped version of the table from the recycle bin for which undo is still available.

It retrieves the most recently dropped version of the table.

It retrieves the most recently dropped version of the table from the recycle bin for which undo Is still available.

It retrieves the least recently dropped version of the table.

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

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

increasing resource allocation for the consumer group mapped to the job class in the resource manager plan associated with 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

The size of the shared pool is too small.

Cursors are not being shared.

A large number COMMITS are being performed.

There are frequent logons and logoffs.

The buffers are being read into the buffer cache, but some other session is changing the buffers.

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.

Disable Flashback Archiving, set the column unused, and re-enable Flashback Archiving.

Disable Flashback Archiving, drop the column unused, and re-enable Flashback Archiving.

Disassociate the Flashback Archive using the DBMS_FLASHBACK_ARCHIVE.DISASSOCIATE_FBA procedure, drop the column, and re-associate the Flashback Archive using the DBMS_FLASHBACK_ARCHIVE.RESASSOCIATE_FBA procedure.

Drop the column using the ALTER TABLE statement.

Disassociate the Flashback Archive using the DBMS_FLASHBACK_ARCHIVE.DISASSOCIATE_FBA procedure, set the column unused, and re-associate the Flashback Archive using the DBMS_FLASHBACK_ARCHIVE.RESASSOCIATE_FBA procedure.

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.

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 resource allocation for the consumer group mapped to the job class in the resource manager plan associated with 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 adds new, better plans automatically as fixed plans to the baseline.

The non-accepted plans are automatically accepted and become usable by the optimizer if they perform better than the existing accepted plans.

It automatically performs verification or evolves non-accepted plans, in COMPREHENSIVE mode when they perform better than existing accepted plans.

The non-accepted plans in a SQL plan baseline are automatically evolved, in COMPREHENSIVE mode, during the nightly maintenance window and a persistent verification report is generated.