Explanation/Reference:
Explanation:
* Because temp files cannot be backed up and because no redo is ever generated for them, RMAN never restores or recovers temp files. RMAN does track the names of temp files, but only so that it can automatically re-create them when needed.
* If you use RMAN in a Data Guard environment, then RMAN transparently converts primary control files to standby control files and vice versa. RMAN automatically updates file names for data files, online redo logs, standby redo logs, and temp files when you issue RESTORE and RECOVER.

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
References: https://docs.oracle.com/cd/E11882_01/server.112/e40540/datadict.htm#CNCPT002