Oracle 1Z0-067 Online Practice Questions and Exam Preparation

Oracle 1Z0-067 Online Questions & Answers

• Question 181:

  The CATDB12C database contains an Oracle Database 12c catalog schema owned by the rc12c user.

  The CATDB11 database contains an Oracle Database 11g catalog schema owned by the rc11 user.

  A database with dbid=1423241 is registered in the catdb11

  catalog. Both the recovery catalog databases are open.

  In the CATDB12c database, you execute the commands:

  $rman

  RKAN> CONNECT CATALOG rc12c/pass12c@catdb12c

  RKAN> IMPORT CATALOG rc11/pwdcat11@catdb11 DBID=1423241;

  What is the outcome of the import?

  A. It fails because the target database and recovery catalog database are of different versions.
  B. It succeeds and all global scripts in the RC11 catalog that have the same name as existing global scripts in the RCI2C catalog are automatically renamed.
  C. It succeeds but the database is not automatically registered in the RC12C catalog.
  D. It fails because RMAN is not connected to the target database with DBID=1423241
  B. It succeeds and all global scripts in the RC11 catalog that have the same name as existing global scripts in the RCI2C catalog are automatically renamed.

• Question 182:

  You perform an RMAN block media recovery on the tools 01.dbf data file in the SALES database. Which two statements are true? (Choose two.)

  A. You must ensure that the SALES database is mounted or open.
  B. You must restore a backup control file to perform a block media recovery.
  C. You must take the tools01.dbf data file offline before you start a block media recovery.
  D. You must put the database in NOARCHIVELOG mode to perform a block media recovery.
  E. You can perform only a complete media recovery of individual blocks, point-in-time recovery of individual data blocks is not supported.
  A. You must ensure that the SALES database is mounted or open.
  E. You can perform only a complete media recovery of individual blocks, point-in-time recovery of individual data blocks is not supported.

• Question 183:

  Automatic Undo Management is enabled for your database. You want a user to retrieve metadata and historical data for a given transaction or for transactions in a given time interval.

  Which three are prerequisites to fulfill this requirement?

  A. Minimal supplemental logging must be enabled.
  B. The database must be running in archivelog mode.
  C. Flashback Data Archive must be created and the flashback archive administer system privilege must be granted to the user.
  D. The flashback any table privilege must be granted to the user.
  E. The select any transaction privilege must be granted to the user.
  F. The recycle bin parameter must be set to on.
  A. Minimal supplemental logging must be enabled.
  B. The database must be running in archivelog mode.
  E. The select any transaction privilege must be granted to the user.

  ---

  To configure your database for the Flashback Transaction feature, you or your database administrator must: With the database mounted but not open, enable ARCHIVELOG: ALTER DATABASE ARCHIVELOG; Open at least one archive log:

  ALTER SYSTEM ARCHIVE LOG CURRENT; If not done, enable minimal and primary key supplemental logging: ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY

  KEY) COLUMNS; Granting Necessary Privileges For Oracle Flashback Transaction Query Grant the SELECT ANY TRANSACTION privilege. For Oracle Flashback Query and Oracle Flashback Version Query To allow access to specific

  objects during queries, grant FLASHBACK and SELECT privileges on those objects. To allow queries on all tables, grant the FLASHBACK ANY TABLE privilege.

  Reference:

  http://docs.oracle.com/cd/E11882_01/appdev.112/e41502/adfns_flashback.htm#ADFNS612

• Question 184:

  Which two statements are true regarding the Oracle Data Pump export and import operations?

  A. You cannot export data from a remote database.
  B. You can rename tables during import.
  C. You can overwrite existing dump files during export.
  D. You can compress data but not metadata during export.
  B. You can rename tables during import.
  C. You can overwrite existing dump files during export.

  ---

  However, in Oracle 11g there is a new parameter, reuse_dumpfiles, which overwrites any created dump file in a specified folder. This parameter accepts two values: Y and N. Default is N. If the parameter was set to Y, then Data Pump overwrites the files that already exist. Reference: http://www.dba-oracle.com/T_rman_167_expdp_reuse_dumpfiles_parameter.htm

• Question 185:

  You want to back up a database such that only formatted blocks are backed up. Which statement is true about this backup operation?

  A. The backup must be performed in mount state.
  B. The tablespace must be taken offline.
  C. All files must be backed up as backup sets.
  D. The database must be backed up as an image copy.
  A. The backup must be performed in mount state.

  ---

  If you run multiple AUDIT statements on the same unified audit policy but specify different EXCEPT users, then Oracle Database uses the last exception user list, not any of the users from the preceding lists. This means the effect of the earlier AUDIT POLICY ... EXCEPT statements are overridden by the latest AUDIT POLICY ... EXCEPT statement Reference: https://docs.oracle.com/database/121/DBSEG/audit_config.htm#DBSEG459

• Question 186:

  A database is running in archive log mode. The database contains locally managed tablespaces. Examine the RMAN command:

  RMAN> BACKUP AS COMPRESSED BACKUPSET SECTION SIZE 1024M DATABASE;

  Which statement is true about the execution of the command?

  A. The backup succeeds only if all the tablespaces are locally managed.
  B. The backup succeeds only if the RMAN default device for backup is set to disk.
  C. The backup fails because you cannot specify section size for a compressed backup.
  D. The backup succeeds and only the used blocks are backed up with a maximum backup piece size of 1024 MB.
  D. The backup succeeds and only the used blocks are backed up with a maximum backup piece size of 1024 MB.

  ---

  COMPRESSED enables binary compression.

  RMAN compresses the data written into the backup set to reduce the overall size of the backup set. All backups that create backup sets can create compressed backup sets. Restoring compressed backup sets is no different from restoring

  uncompressed backup sets.

  RMAN applies a binary compression algorithm as it writes data to backup sets. This compression is similar to the compression provided by many media manager vendors. When backing up to a locally attached tape device, compression

  provided by the media management vendor is usually preferable to the binary compression provided by BACKUP AS COMPRESSED BACKUPSET. Therefore, use uncompressed backup sets and turn on the compression provided by the

  media management vendor when backing up to locally attached tape devices. You should not use RMAN binary compression andmedia manager compression together.

  Some CPU overhead is associated with compressing backup sets. If the target database is running at or near its maximum load, then you may find the overhead unacceptable. In most other circumstances, compressing backup sets saves

  enough disk space to be worth the CPU overhead.

  SECTION SIZE sizeSpec Specifies the size of each backup section produced during a data file backup.

  By setting this parameter, RMAN can create a multisection backup. In a multisection backup, RMAN creates a backup piece that contains one file section, which is a contiguous range of blocks in a file. All sections of a multisection backup are

  the same size. You can create a multisection backup for a data file, but not a data file copy.

  File sections enable RMAN to create multiple steps for the backup of a single large data file.

  RMAN channels can process each step independently and in parallel, with each channel producing one section of a multisection backup set. If you specify a section size that is larger than the size of the file, then RMAN does not use

  multisection backup for the file. If you specify a small section size that would produce more than 256 sections, then RMAN increases the section size to a value that results in exactly 256 sections.

  Depending on where you specify this parameter in the RMAN syntax, you can specify different section sizes for different files in the same backup job.

  Note: You cannot use SECTION SIZE with MAXPIECESIZE or with INCREMENTAL LEVEL 1.

• Question 187:

  You want to export the pluggable database (PDB) hr pdb1 from the multitenant container database (CDB)CDB1 and import it into the cdb2 CDB as the emp_pdb1 PDB.

  Examine the list of possible steps required to perform the task:

  1.Create a PDB named emp_pdb1.

  2.Export the hr_pdb1 PDB by using the full clause.

  3.Open the emp_pdb1 PDB.

  4.Mount the emp_pdb1 PDB.

  5.Synchronize the emp_pdb1 PDB in restricted mode.

  6.Copy the dump file to the Data Pump directory.

  7.Create a Data Pump directory in the emp_pdb1 PDB.

  8.Import data into emp_pdb1 with the full and remap clauses.

  9.Create the same tablespaces in emp_pdb1 as in hr_pdb1 for new local user objects.

  Identify the required steps in the correct order.

  A. 2, 1, 3, 7, 6, and 8
  B. 2, 1, 4, 5, 3, 7, 6, 9, and 8
  C. 2, 1, 3, 7, 6, 9, and 8
  D. 2, 1, 3, 5, 7, 6, and 8
  C. 2, 1, 3, 7, 6, 9, and 8

  ---

  Because the step 2 says that you perfom an expdp with the full clause and you don't need to create the tablespaces when you perform the impdp. FULL=yes will export tablespace definitions. So no need step 9.

  Reference:

  https://docs.oracle.com/cd/B10501_01/server.920/a96652/ch01.htm

• Question 188:

  Which three statements are true about unplugging a pluggable database (PDB)?

  A. The PDB must be open in read only mode.
  B. The PDB must be dosed.
  C. The unplugged PDB becomes a non-CDB.
  D. The unplugged PDB can be plugged into the same multitenant container database (CDB)
  E. The unplugged PDB can be plugged into another CDB.
  F. The PDB data files are automatically removed from disk.
  B. The PDB must be dosed.
  D. The unplugged PDB can be plugged into the same multitenant container database (CDB)
  E. The unplugged PDB can be plugged into another CDB.

  ---

  B, not A: The PDB must be closed before unplugging it.

  D: An unplugged PDB contains data dictionary tables, and some of the columns in these encode information in an endianness-sensitive way. There is no supported way to handle the conversion of such columns automatically. This means, quite simply, that an unplugged PDB cannot be moved across an endianness difference.

  E (not F): To exploit the new unplug/plug paradigm for patching the Oracle version most effectively, the source and destination CDBs should share a filesystem so that the PDB's datafiles can remain in place.

• Question 189:

  You have installed two 64G flash devices to support the Database Smart Flash Cache feature on your database server that is running on Oracle Linux.

  You have set the db_smart_flash_file parameter:

  DB_FLASH_CACHE_FILE= ` /dev/f lash_device_1`,` /dev/f lash_device_2`

  How should the D3_flash_cache_size be configured to use both devices?

  A. Set DB_FLASH_CACHE_SIZE=64G.
  B. Set D3_FLASH_CACHE_SIZE=64G, 64G.
  C. Set D3_FLASK_CACKE_SI2E=i28G.
  D. db_flash_cache_SI2E is automatically configured by the instance at startup.
  B. Set D3_FLASH_CACHE_SIZE=64G, 64G.

  ---

  * Smart Flash Cache concept is not new in Oracle 12C - DB Smart Flash Cache in Oracle 11g.

  In this release Oracle has made changes related to both initialization parameters used by DB Smart Flash cache. Now you can define many files|devices and its sizes for "Database Smart Flash Cache" area. In previous releases only one file|

  device could be defined.

  DB_FLASH_CACHE_FILE = /dev/sda, /dev/sdb, /dev/sdc

  DB_FLASH_CACHE_SIZE = 32G, 32G, 64G

  So above settings defines 3 devices which will be in use by "DB Smart Flash Cache"

  /dev/sda -size 32G

  /dev/sdb -size 32G

  /dev/sdc -size 64G

  New view V$FLASHFILESTAT -it's used to determine the cumulative latency and read counts of each file|device and compute the average latency

  Reference: https://oracle-base.com/articles/12c/database-smart-flash-cache-12cr1

• Question 190:

  ENCRYPT_TS is an encrypted tablespace that contains tables with data.

  Which statement is true regarding the effect of queries and data manipulation language (DML) statements on the encrypted data in the tables?

  A. The data is decrypted during SORT and JOIN operations.
  B. The data remains encrypted when it is read into memory.
  C. The data remains encrypted when it is stored in the redo logs
  D. The data remains encrypted in the UNDO tablespace provided that the UNDO tablespace was created with the encryption option enabled.
  C. The data remains encrypted when it is stored in the redo logs