What could be the reason for it?

Examine the initialization parameter values for the instance given below:
NAME TYPE VALUE
———————————— ———– ——————optimizer_capture_sql_plan_baselines boolean FALSE
optimizer_dynamic_sampling integer 2
optimizer_features_enable string 11.1.0.6
optimizer_index_caching integer 0
optimizer_index_cost_adj integer 100
optimizer_mode string ALL_ROWS
db_file_multiblock_read_count integer 64
The index created on the column used in the WHERE clause of the query. You notice that the

query is not using the index. Instead of an index scan, a full table scan is used.
View the Exhibit and examine the autotrace output for a query.

What could be the reason for it? (Choose all that apply.)

A.
The OPTIMIZER_INDEX_COST_ADJ initialization parameter has a low value.

B.
The DB_FILE_MULTIBLOCK_READ_COUNT initialization parameter has a low value.

C.
The statistics for the table and all the indexes associated with the table are not current.

D.
The table has less than DB_FILE_MULTIBLOCK_READ_COUNT blocks under the high-water
mark.