1Z1-060 無料問題集「Oracle Upgrade to Oracle Database 12c」

（A）Each pluggable database (PDB) has its own set of background processes.

（B）Different PDBs can have different default block sizes.

（C）A PDB can have a private temp tablespace.

（D）Log switches occur only at the multitenant container database (CDB) level.

（E）PDBs share a common system tablespace.

（F）PDBs can share the sysaux tablespace.

（G）Instance recovery is always performed at the CDB level.

（A）Only the ORD_CUSTOMER_IX2 index is created.

（B）Only the ORD_CUSTOMER_IX1 index is created.

（C）The optimizer evaluates index access from both the Indexes before deciding on which index to use for query execution plan.

（D）Both the indexes are updated when a new row is inserted, updated, or deleted In the orders table.

（E）Both the indexes are created; however, only the ORD_COSTOMER index is visible.

（A）It excludes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN in root and all PDBs.

（B）It fails and reports an error because the CONTAINER=ALL clause is not used.

（C）It executes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN in root only.

（D）It executes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN in all PDBs.

（E）It fails and reports an error because the CONTAINER=CURRENT clause is not used.

（A）the shutdown proceeds as soon as all transactions in the PDBs are either committed or rolled back.

（B）the shutdown proceeds immediately

（C）the shutdown proceeds as soon as all transactions in the CDB are either committed or rolled back.

（D）the statement results in an error because there are open PDBs

（A）Tablespace creation ignores the data file and temp file locations specified in the CREATE commands, and creates both the tablespaces in the DB_CREATE_FILE_DEST location.

（B）The AUGUST_SALES tablespace is created with its data file in the DB_CREATE_FILE_DEST location and the TEMP101 tablespace is created with its temp file in the '/u01/app/oracle/mydata' location.

（C）The two tablespaces are created with the data file and temp file in their respective locations as specified in the CREATE commands.

（D）The TEMP101 tablespace is created with its temp file in the DB_CREATE_FILE_DEST location and the tablespace is created with its data file in the '/u01/app/oracle/mydata/ AUGUST_SALES location.
mysales.dbf'

（A）Use the MD_RESTORE command to restore the disk group metadata and use RMAN to restore the data.

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

（C）Use the MKDG command to add a new disk group DG1 with the same or different specifications as those from the lost disk group and use RMAN to restore the data.

（D）Use RMAN to restore both the metadata and the data.

（A）They are used to gather only missing statistics.

（B）Improve plan accuracy by persisting both compilation and execution statistics in the SYSAUX tablespace.

（C）They are tied to a specific statement or SQL ID.

（D）They instruct the maintenance job to collect missing statistics or perform dynamic sampling to generate a more optimal plan.

（E）They are created for a query expression where statistics are missing or the cardinality estimates by the optimizer are incorrect.

（F）They instruct the optimizer to create only column group statistics.

（A）Increasing the value of the JOB_QUEUE_PROCESSES parameter

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

（C）Increasing the priority of the scheduler window to which the job belongs

（D）Increasing the priority of the job class to which the job belongs

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

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

（A）Decreasing PCTFREE

（B）Increasing the number of DBWNprocess

（C）Decreasing PCTUSED

（D）Increasing db_buffer_cache based on the V$DB_CACHE_ADVICE recommendation

（E）Using Automatic Segment Space Management (ASSM)

（A）STREAMS_POOL_SIZE

（B）JAVA_POOL_SIZE

（C）DB_16K_CACHE_SZIE

（D）DB_KEEP_CACHE_SIZE

（E）SORT_AREA_SIZE

（F）LOG_BUFFER

（A）The ORA_ARCHIVE_STATE column is updated manually or by a program that can reference activity tracking columns, to indicate that a row is no longer considered active.

（B）The ORA_ARCHIVE_STATE column is visible if it is referenced in the select list of a query.

（C）The ORA_ARCHIVE_STATE column is updated automatically by the database based on activity tracking columns, to indicate that a row is no longer considered active.

（D）Visibility of the ORA_ARCHIVE_STATE column is controlled by the ROW ARCHIVAL VISIBILITY session parameter.

（E）The ROW ARCHIVAL VISIBILITY session parameter defaults to all rows.

（A）Enable Flashback Data Archiving for the tables that require tracking.

（B）Enable supplemental logging for the database.

（C）Create a Flashback Data Archive in any suitable tablespace.

（D）Create a Flashback Data Archive in the tablespace where the tables are stored.

（E）Specify undo retention guarantee for the database.

（A）The root container can be flashed back without flashing back the pluggable databases (PDBs).

（B）The DB_FLASHBACK RETENTION_TARGET parameter must be set to enable flashback of the CDB.

（C）A CDB can be flashed back specifying the desired target point in time or an SCN, but not a restore point.

（D）Individual PDBs can be flashed back without flashing back the entire CDB.

（E）To enable flashback database, the CDB must be mounted.

（A）Statistics gathered on the CUSTOMERS table when schema stats are gathered are stored as pending statistics.

（B）Statistics gathered on the CUSTOMERS table when database stats are gathered are stored as pending statistics.

（C）Any existing statistics for the CUSTOMERS table are still available to the optimizer at parse time.

（D）Statistics collection is not done for the CUSTOMERS table when schema stats are gathered.

（E）Statistics collection is not done for the CUSTOMERS table when database stats are gathered.