You can design your applications to automatically grant a role to the user who is trying to log in, provided the user meets criteria that you specify. To do so, you create a secure application role, which is a role that is associated with a PL/SQL procedure (or PL/SQL package that contains multiple procedures). The procedure validates the user: if the user fails the validation, then the user cannot log in. If the user passes the validation, then the procedure grants the user a role so that he or she can use the application. The user has this role only as long as he or she is logged in to the application. When the user logs out, the role is revoked.
Incorrect:
Not B: REMOTE_OS_AUTHENT specifies whether remote clients will be authenticated with the value of the OS_AUTHENT_PREFIX parameter.
Not C, not E: SEC_MAX_FAILED_LOGIN_ATTEMPTS specifies the number of authentication attempts that can be made by a client on a connection to the server process. After the specified number of failure attempts, the connection will be automatically dropped by the server process.
Not D: REMOTE_LOGIN_PASSWORDFILE specifies whether Oracle checks for a password file.
Values:
shared
One or more databases can use the password file. The password file can contain SYS as well as non-SYS users.
exclusive
The password file can be used by only one database. The password file can contain SYS as well as non-SYS users.
none
Oracle ignores any password file. Therefore, privileged users must be authenticated by the operating system.
Note:
The REMOTE_OS_AUTHENT parameter is deprecated. It is retained for backward compatibility only.

Explanation/Reference:
Explanation:
A: ASM_POWER_LIMIT specifies the maximum power on an Automatic Storage Management instance for
disk rebalancing. The higher the limit, the faster rebalancing will complete. Lower values will take longer,
but consume fewer processing and I/O resources.
D:
* Normally a separate process is fired up to do that rebalance. This will take a certain amount of time. If
you want it to happen faster, fire up more processes. You tell ASM it can add more processes by
increasing the rebalance power.
* ASMB
ASM Background Process
Communicates with the ASM instance, managing storage and providing statistics
Incorrect:
Not B: A higher, not a lower, value of DISK_REPAIR_TIME would be helpful here.
Not E: If you implement database writer I/O slaves by setting the DBWR_IO_SLAVES parameter, you
configure a single (master) DBWR process that has slave processes that are subservient to it. In addition,
I/O slaves can be used to "simulate" asynchronous I/O on platforms that do not support asynchronous I/O
or implement it inefficiently. Database I/O slaves provide non-blocking, asynchronous requests to simulate
asynchronous I/O.

Explanation/Reference:
Explanation:
Multipartition maintenance enables adding, dropping, truncate, merge, split operations on multiple partitions.
A: Merge Multiple Partitions:
The new “ALTER TABLE … MERGE PARTITIONS ” help merge multiple partitions or subpartitions with a single statement. When merging multiple partitions, local and global index operations and semantics for inheritance of unspecified physical attributes are the same for merging two partitions.
B: Drop Multiple Partitions:
The new “ALTER TABLE … DROP PARTITIONS ” help drop multiple partitions or subpartitions with a single statement.
Example:
view plaincopy to clipboardprint?
SQL> ALTER TABLE Tab_tst1 DROP PARTITIONS
Tab_tst1_PART5, Tab_tst1_PART6, Tab_tst1_PART7;
Table altered
SQL>
Restrictions :
- You can’t drop all partitions of the table.
- If the table has a single partition, you will get the error: ORA-14083: cannot drop the only partition of a partitioned.

C: To use Oracle ASM or Oracle Restart, you must first install Oracle Grid Infrastructure for a standalone server before you install and create the database. Otherwise, you must manually register the database with Oracle Restart.
Desupport of Block and Raw Devices
With the release of Oracle Database 11g release 2 (11.2) and Oracle RAC 11g release 2 (11.2), using Database Configuration Assistant or the installer to store Oracle Clusterware or Oracle Database files directly on block or raw devices is not supported.
If you intend to upgrade an existing Oracle RAC database, or an Oracle RAC database with Oracle ASM instances, then you can use an existing raw or block device partition, and perform a rolling upgrade of your existing installation. Performing a new installation using block or raw devices is not allowed.