Not A: Both indexes are created fine.
B: The invisible index ORD_CUSTOMERS_IX1 and the bitmap index are both updated by DML operations on the Orders table.
F: Since ORD_CUSTOMERS_IX1 is invisible only ORD_CUSTOMERS_IX2 is used by the query optimizer.
Not C,Not D,Not E:
* ord_customer_ix1 is an invisible index and is therefore not used by the optimizer.
* VISIBLE | INVISIBLE Use this clause to specify whether the index is visible or invisible to the optimizer. An invisible index is maintained by DML operations, but it is not be used by the optimizer during queries unless you explicitly set the parameter OPTIMIZER_USE_INVISIBLE_INDEXES to TRUE at the session or system level.
Note: Specify BITMAP to indicate that index is to be created with a bitmap for each distinct key, rather than indexing each row separately. Bitmap indexes store the rowids associated with a key value as a bitmap. Each bit in the bitmap corresponds to a possible rowid. If the bit is set, then it means that the row with the corresponding rowid contains the key value.
The internal representation of bitmaps is best suited for applications with low levels of concurrent transactions, such as data warehousing.

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 (not D): CONS_VPD_AUTO Used to indicate to copy VPD policies automatically
*DBMS_RLS.ADD_POLICY / The DBMS_RLS package contains the fine-grained access control administrative interface, which is used to implement Virtual Private Database (VPD).DBMS_RLS is available with the Enterprise Edition only.
Note:
*CONS_USE_PK and CONS_USE_ROWID are constants used as input to the "options_flag" parameter in both the START_REDEF_TABLE Procedure and CAN_REDEF_TABLE Procedure. CONS_USE_ROWID is used to indicate that the redefinition should be done using rowids while CONS_USE_PK implies that the redefinition should be done using primary keys or pseudo-primary keys (which are unique keys with all component columns having NOT NULL constraints).
*DBMS_REDEFINITION.START_REDEF_TABLE To achieve online redefinition, incrementally maintainable local materialized views are used. These logs keep track of the changes to the master tables and are used by the materialized views
during refresh synchronization.
*START_REDEF_TABLE Procedure Prior to calling this procedure, you must manually create an empty interim table (in the same schema as the table to be redefined) with the desired attributes of the post-redefinition table, and then call this procedure to initiate the redefinition.

Explanation/Reference:
Explanation:
Not A: Both indexes are created fine.
B: The invisible index ORD_CUSTOMERS_IX1 and the bitmap index are both updated by DML operations on the Orders table.
F: Since ORD_CUSTOMERS_IX1 is invisible only ORD_CUSTOMERS_IX2 is used by the query optimizer.
Incorrect Answers:
C, D, E:
* ord_customer_ix1 is an invisible index and is therefore not used by the optimizer.
* VISIBLE | INVISIBLE Use this clause to specify whether the index is visible or invisible to the optimizer.
An invisible index is maintained by DML operations, but it is not be used by the optimizer during queries unless you explicitly set the parameter OPTIMIZER_USE_INVISIBLE_INDEXES to TRUE at the session or system level.
Note: Specify BITMAP to indicate that index is to be created with a bitmap for each distinct key, rather than indexing each row separately. Bitmap indexes store the rowids associated with a key value as a bitmap.
Each bit in the bitmap corresponds to a possible rowid. If the bit is set, then it means that the row with the corresponding rowid contains the key value. The internal representation of bitmaps is best suited for applications with low levels of concurrent transactions, such as data warehousing.

Explanation/Reference:
Explanation:
DBMS_FGA.ADD_POLICY(object_schema => 'hr',object_name => 'emp',policy_name =>
'chk_hr_emp',audit_condition => 'dept = "SALES" ',audit_column => 'salary'statement_types =>
'insert,update,delete,select');
Default value for statement_types is SELECT
Setting audit_trail to DBMS_FGA.DB sends the audit trail to the SYS.FGA_LOG$ table in the database

and omits SQL Text and SQL Bind.
Setting audit_trail to DBMS_FGA.DB+EXTENDED sends the audit trail to the SYS.FGA_LOG$ table in

the database and includes SQL Text and SQL Bind.
Setting audit_trail to DBMS_FGA.XML writes the audit trail in XML files sent to the operating system

and omits SQL Text and SQL Bind.
Setting audit_trail to DBMS_FGA.XML+EXTENDED writes the audit trail in XML files sent to the

operating system and includes SQL Text and SQL Bind.
Default value fo audit_trail parameter in DBMS_FGA.ADD_POLICY is DB+EXTENDED