After actual execution of the query, you notice that the hash join was done in the execution plan: Identify the reason why the optimizer chose different execution plans.

Examine the parameter for your database instance:

You generated the execution plan for the following query in the plan table and noticed that the
nested loop join was done. After actual execution of the query, you notice that the hash join was
done in the execution plan:

Identify the reason why the optimizer chose different execution plans.

A.
The optimizer used a dynamic plan for the query.

B.
The optimizer chose different plans because automatic dynamic sampling was enabled.

C.
The optimizer used re-optimization cardinality feedback for the query.

D.
The optimizer chose different plan because extended statistics were created for the columns
used.

Explanation:
* optimizer_dynamic_sampling
OPTIMIZER_DYNAMIC_SAMPLING controls both when the database gathers dynamic statistics,
and the size of the sample that the optimizer uses to gather the statistics.
Range of values0 to 11