Which two are regarding the case of storage indexes?
To increase the chance of using the a storage index, you can make table indexes invisible.
To maximize the benefit of storage Indexes, load your data stored on the filtered columns.
The cell physical 10 bytes saved by storage index statistic returns multiple rows, one for each
Storage indexes are retained after a cell is rebooted.
Avoid the use of bind variables because Storage Indexes do not work with bind variables.
B:* To use storage indexes, Oracle Exadata queries must use smart scans, so not
all types of applications can benefit from storage indexes.
*With Exadata storage, database operations are handled much more efficiently. Queries that
perform table scans can be processed within Exadata storage with only the required subset of
data returned to the database server. Row filtering, column filtering and some join processing
(among other functions) are performed within the Exadata storage cells. When this takes place
only the relevant and required data is returned to the database server.
Not D:Storage indexes reside in the memory of the storage servers.
If a storage cell is shutdown or rebooted the storage index will be lost from memory and will be
recreated on subsequent accesses to the data after the cell has been brought back online.