utlrp.sql and utlprp.sql
The utlrp.sql and utlprp.sql scripts are provided by Oracle to recompile all invalid objects in the database. They are typically run after major database changes such as upgrades or patches. They are located in the
$ORACLE_HOME/rdbms/admin directory and provide a wrapper on the UTL_RECOMP package. The utlrp.sql script simply calls the utlprp.sql script with a command line parameter of "0". The utlprp.sql accepts a single integer parameter that indicates the level of parallelism as follows.
0 - The level of parallelism is derived based on the CPU_COUNT parameter.
1 - The recompilation is run serially, one object at a time.
N - The recompilation is run in parallel with "N" number of threads.
Both scripts must be run as the SYS user, or another user with SYSDBA, to work correctly.

E:By default, flashback archiving is disabled for any table. You can enable flashback archiving for a table if you have the FLASHBACK ARCHIVE object privilege on the Flashback Data Archive that you want to use for that table. D:Creating a Flashback Data Archive
/Create a Flashback Data Archive with the CREATE FLASHBACK ARCHIVE statement, specifying the following:
Name of the Flashback Data Archive
Name of the first tablespace of the Flashback Data Archive
(Optional) Maximum amount of space that the Flashback Data Archive can use in the first tablespace
/Create a Flashback Data Archive named fla2 that uses tablespace tbs2, whose data will be retained for two years:
CREATE FLASHBACK ARCHIVE fla2 TABLESPACE tbs2 RETENTION 2 YEAR;

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'.

C: Creating a password file via orapwd enables remote users to connect with
administrative privileges through SQL*Net.
D, not A, Not B: When SYSDBA or SYSOPER privileges are granted to a user, that user's name
and privilege information are added to the password file.
Incorrect:
Not E: The Oracle orapwd command line utility assists the DBA with granting SYSDBA and
SYSOPER privileges to other users.
Note:
*You can create a password file using the password file creation utility, ORAPWD. For some
operating systems, you can create this file as part of your standard installation.
*ORAPWD FILE=filename [ENTRIES=numusers] [FORCE={Y|N}] [IGNORECASE={Y|N}] [NOSYSDBA={Y|N}]
FILEName to assign to the password file. See your operating system documentation for name
requirements. You must supply a complete path. If you supply only a file name, the file is written to
the current directory.
ENTRIES(Optional) Maximum number of entries (user accounts) to permit in the file.
FORCE(Optional) If y, permits overwriting an existing password file.
IGNORECASE(Optional) If y, passwords are treated as case-insensitive.
NOSYSDBA(Optional) For Data Vault installations. See the Data Vault installation guide for your
platform for more information.