Oracle 1Z0-060 Online Practice Questions and Exam Preparation

Oracle 1Z0-060 Online Questions & Answers

• Question 201:

  You execute this piece of code with appropriate privileges:

  

  User SCOTT has been granted the CREATE SESSION privilege and the MGR role.

  Which two statements are true when a session logged in as SCOTT queries the SAL columns in the view and the table?

  A. Data is redacted for the EMP.SAL column only if the SCOTT session does not have the MGR role set.
  B. Data is never redacted on the EMP.SAL column.
  C. Data is redacted for the EMP.SAL column only if the SCOTT session has the MGR role set.
  D. Data is redacted for the EMP_V.SAL column only if the SCOTT session has the MGR role set.
  E. Data is never redacted on the EMP_V.SAL column.
  A. Data is redacted for the EMP.SAL column only if the SCOTT session does not have the MGR role set.
  E. Data is never redacted on the EMP_V.SAL column.

• Question 202:

  Which action takes place when an incremental checkpoint occurs?

  A. The checkpoint position is advanced by the checkpoint process.
  B. Redo entries are written by the checkpoint process to the online redo log files.
  C. All dirty buffers are written to data files by the checkpoint process.
  D. The checkpoint position is written to all the data file headers and the control file by the checkpoint process.
  E. The checkpoint position is written to the control file by the checkpoint process.
  C. All dirty buffers are written to data files by the checkpoint process.

  ---

  Reference: http://www.dba-oracle.com/t_incremental_checkpoint.htm

• Question 203:

  You are connected to a pluggable database (PDB) as a common user with DBA privileges. The STATISTICS_LEVEL parameter is PDB_MODIFIABLE. You execute the following: SQL > ALTER SYSTEM SET STATISTICS_LEVEL = ALL SID = `*' SCOPE = SPFILE; Which is true about the result of this command?

  A. The STATISTICS_LEVEL parameter is set to all whenever this PDB is re-opened.
  B. The STATISTICS_LEVEL parameter is set to ALL whenever any PDB is reopened.
  C. The STATISTICS_LEVEL parameter is set to all whenever the multitenant container database (CDB) is restarted.
  D. Nothing happens; because there is no SPFILE for each PDB, the statement is ignored.
  A. The STATISTICS_LEVEL parameter is set to all whenever this PDB is re-opened.

  ---

  http://docs.oracle.com/database/121/ADMIN/cdb_pdb_admin.htm#ADMIN14017

• Question 204:

  Which Oracle Database component is audited by default if the unified Auditing option is enabled?

  A. Oracle Data Pump
  B. Oracle Recovery Manager (RMAN)
  C. Oracle Label Security
  D. Oracle Database Vault
  E. Oracle Real Application Security
  B. Oracle Recovery Manager (RMAN)

• Question 205:

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

  A. The PDB must be open in read only mode.
  B. The PDB must be closed.
  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 closed.
  D. The unplugged PDB can be plugged into the same multitenant container database (CDB)
  E. The unplugged PDB can be plugged into another CDB.

  ---

  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. The PDB must be closed before it can be unplugged. When you unplug a PDB from a CDB, the unplugged PDB is in mounted mode. The unplug operation makes some changes in the PDB's data files to record, for example, that the PDB was successfully unplugged. Because it is still part of the CDB, the unplugged PDB is included in an RMAN backup of the entire CDB. Such a backup provides a convenient way to archive the unplugged PDB in case it is needed in the future.

• Question 206:

  Examine the commands executed to monitor database operations:

  $> conn sys oracle/oracle@prod as sysdba SQL > VAR eid NUMBER SQL > EXEC: eid:= DBMS_SQL_MONITOR.BEGIN_OPERATION ('batch_job', FORCED_TRACKING => 'Y');

  Which two statements are true? (Choose two.)

  A. Database operations will be monitored only when they consume a significant amount of resources.
  B. Database operations for all sessions will be monitored.
  C. Database operations will be monitored only if the STATISTICS_LEVEL parameter is set to TYPICAL and CONTROL_MANAGEMENT_PACK_ACCESS is set to DIAGNISTIC + TUNING.
  D. Only DML and DDL statements will be monitored for the session.
  E. All subsequent statements in the session will be treated as one database operation and will be monitored.
  C. Database operations will be monitored only if the STATISTICS_LEVEL parameter is set to TYPICAL and CONTROL_MANAGEMENT_PACK_ACCESS is set to DIAGNISTIC + TUNING.
  E. All subsequent statements in the session will be treated as one database operation and will be monitored.

  ---

  C: Setting the CONTROL_MANAGEMENT_PACK_ACCESS initialization parameter to DIAGNOSTIC+TUNING (default) enables monitoring of database operations. Real-Time SQL Monitoring is a feature of the Oracle Database Tuning Pack. Note:

  * The DBMS_SQL_MONITOR package provides information about Real-time SQL Monitoring and Real-time Database Operation Monitoring. *(not B) BEGIN_OPERATION Function starts a composite database operation in the current session.

  / (E) FORCE_TRACKING - forces the composite database operation to be tracked when the operation starts. You can also use the string variable 'Y'.

  / (not A) NO_FORCE_TRACKING - the operation will be tracked only when it has consumed at least 5 seconds of CPU or I/O time. You can also use the string variable 'N'.

• Question 207:

  You wish to enable an audit policy for all database users, except SYS, SYSTEM, and SCOTT.

  You issue the following statements:

  SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SYS;

  SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SYSTEM;

  SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SCOTT;

  For which database users is the audit policy now active?

  A. All users except SYS
  B. All users except SCOTT
  C. All users except SYS and SCOTT
  D. All users except SYS, SYSTEM, and SCOTT
  B. All users except SCOTT

  ---

  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.

  Note:

  *

  The ORA_DATABASE_PARAMETER policy audits commonly used Oracle Database parameter settings. By default, this policy is not enabled.

  *

  You can use the keyword ALL to audit all actions. The following example shows how to audit all actions on the HR.EMPLOYEES table, except actions by user pmulligan.

  Example Auditing All Actions on a Table

  CREATE AUDIT POLICY all_actions_on_hr_emp_pol

  ACTIONS ALL ON HR.EMPLOYEES;

  AUDIT POLICY all_actions_on_hr_emp_pol EXCEPT pmulligan;

• Question 208:

  Identify the prerequisite for configuring and accessing Enterprise Manager (EM) express for an Oracle 12c database.

  A. Create a SYSMAN user with the SYSDBA role as an administrator for EM express.
  B. Configure the DISPATCHERS initialization parameter such that at least one dispatcher is configured for the XMLDB service with the TCP protocol.
  C. Install the Oracle HTTP Server.
  D. Use the DBMS_XDB_CONFIG.SETHTTPPORT procedure to configure port number 5500 for the HTTP server.
  D. Use the DBMS_XDB_CONFIG.SETHTTPPORT procedure to configure port number 5500 for the HTTP server.

  ---

  Execute the DBMS_XDB_CONFIG.SETHTTPSPORT procedure.

  Reference: https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/access-em-database-express-12c.html

• Question 209:

  In a recent Automatic Workload Repository (AWR) report for your database, you notice a high number of buffer busy waits. The database consists of locally managed tablespaces with free list managed segments.

  On further investigation, you find that buffer busy waits is caused by contention on data blocks.

  Which option would you consider first to decrease the wait event immediately?

  A. Decreasing PCTUSED
  B. Decreasing PCTFREE
  C. Increasing the number of DBWN process
  D. Using Automatic Segment Space Management (ASSM)
  E. Increasing db_buffer_cache based on the V$DB_CACHE_ADVICE recommendation
  D. Using Automatic Segment Space Management (ASSM)

  ---

  *

  Automatic segment space management (ASSM) is a simpler and more efficient way of managing space within a segment. It completely eliminates any need to specify and tune the pctused,freelists, and freelist groups storage parameters for schema objects created in the tablespace. If any of these attributes are specified, they are ignored.

  *

  Oracle introduced Automatic Segment Storage Management (ASSM) as a replacement for traditional freelists management which used one-way linked-lists to manage free blocks with tables and indexes. ASSM is commonly called "bitmap freelists" because that is how Oracle implement the internal data structures for free block management.

  Note:

  *

  Buffer busy waits are most commonly associated with segment header contention onside the data buffer pool (db_cache_size, etc.).

  *

  The most common remedies for high buffer busy waits include database writer (DBWR) contention tuning, adding freelists (or ASSM), and adding missing indexes.

• Question 210:

  Which three statements are true about tablespaces in a multitenant container database (CDB)?

  A. All PDBs and CDBs have their own UNDO tablespaces.
  B. All PDBs and CDBs have their own SYSTEM and SYSAUX tablespaces.
  C. Each pluggable database (PDB) can have a temporary tablespace or a tablespace group.
  D. CDBs and PDBs may share the same temporary tablespace that is present in the root container.
  E. There can be only one temporary tablespace group in a CDB.
  B. All PDBs and CDBs have their own SYSTEM and SYSAUX tablespaces.
  C. Each pluggable database (PDB) can have a temporary tablespace or a tablespace group.
  D. CDBs and PDBs may share the same temporary tablespace that is present in the root container.