1Z0-083 無料問題集「Oracle Database Administration II」

（A）RMAN always uses an auxiliary instance.

（B）RMAN can recover tables owned by the SYS user.

（C）RMAN can recover tables in the SYSTEM tablespace.

（D）RMAN can recover tables in a standby database.

（E）RMAN can recover tables owned by the SYSTEM user.

（F）RMAN can recover tables in the SYSAUX tablespace.

（G）RMAN can recover a table after a DDL operation has altered the table structure.

（A）Thesamestatementmayfilteronbothtransactiontimeandvalidtemporaltimebyusingthe AS OF TIMESTAMP and PERIOD FOR clauses.

（B）The valid time columns employee_time_start and employee_time_end are automatically created.

（C）The valid time columns are visible by default when the table is described.

（D）Setting the session valid time using DBMS_FLASHBACK_ARCHIVE.ENABLE_AT_VALID_TIME sets the visibility for data manipulation language (DML), data definition language (DDL), and queries performed by the session.

（E）The valid time columns are not populated by the Oracle Server automatically.

（A）creating an SPFILE for the target database

（B）connecting to an auxiliary instance

（C）creating a password file for an auxiliary instance

（D）matching the database identifier (DBID) of the source database and the duplicate database

（E）connecting to the target database and a recovery catalog to execute the duplicate command

（A）It is always possible for RMAN to connect to a pluggable database as a target.

（B）It is only possible for RMAN to connect to a pluggable database as a target if an RMAN Virtual Private Catalog is used.

（C）A Virtual Private Catalog used to register a container database can be created in a non-container database.

（D）A Virtual Private Catalog used to register a container database can be created in a pluggable database.

（E）It is always possible for RMAN to connect to a pluggable database as a target if any RMAN Catalog is used.

（F）A Virtual Private Catalog used to register a container database must be created in a pluggable database.

（A）It can have local users with the same name in different PDBs.

（B）It contains predefined common roles in both the root and the seed.

（C）It can contain only one PDB$SEED, which is created when the CDB is created.

（D）It can be created by cloning an existing CDB.

（E）It can be created from a non-CDB.

（F）It can contain only one Application Container seed, which is created when the Application Container is created.

（G）It can have any number of pluggable databases (PDBs) limited only by space availability.

（A）The password file and SPFILE for the duplicate database dup1 are created in their respective default locations.

（B）he duplicate command.

（C）All archive redo log files are automatically copied to the duplicate database.

（D）The duplicate database has the same directory structure as the source database.

（E）The duplicate database is created without using RMAN backups and prod1 is allowed to remain open during duplication.

（F）The duplicate database is created by using the backups created during the execution of

（A）It recompiles all stored PL/SQL code by using utlrp.sql.

（B）It sets all user tablespaces to "read-only" before starting the upgrade.

（C）It increases tablespace size, if required, to meet upgrade requirements.

（D）It performs prerequisite checks to verify if the Oracle database is ready for upgrade.

（E）It empties the RECYCLE BIN.

（F）It removes the AUDSYS schema and the AUDIT_ADMIN and AUDIT_VIEWER roles

（A）FLASHBACK TRANSACTION

（B）FLASHBACK DATA ARCHIVE

（C）FLASHBACK TABLE

（D）FLASHBACK DATABASE

（E）FLASHBACK VERSION QUERY

（A）CDB$ROOT is in MOUNT state.

（B）PDB1 and PDB2 are in READ ONLY state.

（C）PDB1 and PDB2 are in MOUNT state.

（D）PDB$SEED is in READ ONLY state.

（E）Redo logs are opened.

（A）It can be used to apply interim patches to the Grid Infrastructure and Database Home combination.

（B）It is platform independent.

（C）It requires installation of Oracle Universal Installer.

（D）It is a Java-based utility for applying patchsets.

（E）It supports Rolling Patching.

（F）It must be invoked as the user that owns the software being patched.

（A）It can be backed up manually as a binary copy.

（B）It gets backed up automatically by RMAN when the BACKUP SPFILE command is used.

（C）It cannot be backed up manually as a binary copy.

（D）It can get backed up automatically as a binary copy.

（E）It can be backed up manually as a trace file containing SQL statements for control file recreation.

（F）It gets backed up automatically by RMAN as a trace file containing SQL statements for control file recreation when a database backup occurs.

（A）A CDB-level resource plan is mandatory when using PDB-level resource plans.

（B）A CDB-level resource plan can limit session CPU utilization.

（C）A CDB-level resource plan can limit PDB UNDO use.

（D）PDB-level resource plans can limit uncommitted UNDO per consumer group.

（E）A PDB-level resource plan can limit session PGA memory.

（F）A CDB-level resource plan can limit PDB CPU utilization.