Free 1z0-054 – Oracle Database 11g: Performance Tuning Practice Test Question

Select all that apply, then click Submit answer.

• ○

  flashback query

• ○

  distributed transactions

• ○

  logging in and logging out of sessions

• ○

  all DDL statements having bind variables

• ○

  direct path load of data from external files
  

Select all that apply, then click Submit answer.

• ○

  The latch was requested in no wait mode.

• ○

  The latch was requested in willing-to-wait mode.

• ○

  The shared pool operations to allocate and free memory in it caused the misses.

• ○

  Automatic Memory Management is not enabled because the IMMEDIATE_GETS and IMMEDIATE_MISSES columns have zero in them.
  

Select all that apply, then click Submit answer.

• ○

  Set the SGA_TARGET parameter to 300M.

• ○

  Set the SGA_MAX_SIZE parameter to 400M.

• ○

  Set the MEMORY_MAX_TARGET and MEMORY_TARGET parameters to 400M.

• ○

  Set the MEMORY_MAX_TARGET and MEMORY_TARGET parameters to 100M.

• ○

  Set the PGA_AGGREGATE_TARGET parameter to 200M and the SGA_MAX_SIZE parameter to 400M.
  

Select all that apply, then click Submit answer.

• ○

  reducing hard parses

• ○

  increasing the size of the shared pool

• ○

  using only dedicated server connections

• ○

  setting the CURSOR_SHARING parameter to EXACT

• ○

  encouraging the use of more literal SQL statements
  

Select all that apply, then click Submit answer.

• ○

  Increase the number of ASMB processes.

• ○

  Increase the number of DBWR_IO_SLAVES.

• ○

  Decrease the value for the ASM_POWER_LIMIT parameter.

• ○

  Increase the value for the ASM_POWER_LIMIT parameter.

• ○

  Set the DISK_REPAIR_TIME disk attribute to a lower value.

• ○

  Specify the POWER clause with a lower value in an ALTER DISKGROUP statement.
  

Select an option, then click Submit answer.

• ○

  restoring statistics from statistics history up to the desired time

• ○

  deleting all AWR snapshots collected after the time of desired statistics collection

• ○

  applying the flashback table technique until the time of desired statistics collection

• ○

  setting the OPTIMIZER_PENDING_STATISTICS parameter to TRUE to use the previous version of statistics
  

Select an option, then click Submit answer.

• ○

  Change the STALE_PERCENT preference to zero for the tables.

• ○

  Set the OPTIMIZER_USE_PENDING parameter statistics to TRUE.

• ○

  Set the OPTIMIZER_DYNAMIC_SAMPLING parameter to zero during day time.

• ○

  Gather statistics on the table when the tables have a representative number of rows, and then lock the statistics.
  

Select an option, then click Submit answer.

• ○

  Set the PUBLISH preference to FALSE for the table.

• ○

  Set the NO_VALIDATE preference to TRUE for the table.

• ○

  Set the OPTIMIZER_DYNAMIC_SAMPLING parameter to 0.

• ○

  Set the OPTIMIZER_USE_SQL_PLAN_BASELINES parameter to FALSE for the session.

• ○

  Set the OPTIMIZER_USE_PENDING_STATISTICS parameter to FALSE for the session.
  

Select an option, then click Submit answer.

• ○

  because the query used SCOTT.EMP instead of EMP

• ○

  because the query with * always uses the default pool

• ○

  because the query with * always forces physical I/Os that bypass the keep pool

• ○

  because the blocks of the EMP table are already available in one of the other buffer pools
  

Select an option, then click Submit answer.

• ○

  because the histogram statistics for the COUNTRY_ID column are not updated

• ○

  because the index statistics for the index on the COUNTRY_ID column are not current

• ○

  because the DB_FILE_MULTIBLOCK_READ_COUNT initialization parameter is set to a higher value

• ○

  because the optimizer predicts that most of the blocks in the table are accessed. Therefore, it uses a full table scan, even though indexes are available.