Which interpretation is correct?

View the exhibit and examine the plans in the SQL baseline for a given statement.

Which interpretation is correct?

A.
A new plan cannot be evolved because SYS_SQL_bbedc41f554c408 is accepted.

B.
Plan SYS_SQL_PLAN_bbdc741f554c408 will always be used by the optimizer for the query.

C.
A new plan must be evolved using the DBMS_SPM.EVOLVE_SQL_PLAN_BASELINE function
before it can be used.

D.
Plan SYS_SQL_bbedc741a57b5fc2 can be used by the optimizer if the cost of the query is less
than plan SYS_SQL_PLAN_bbedc741f554c408.

E.
Plan SYS_SQL_PLAN_bbedc741f554c408 will not be used until it is fixed by using the
DBMS_SPM.EVOLVE_SQL_PLAN_BASELINE function.

Explanation:

Note:
* Evolving a SQL plan baseline is the process by which the optimizer determines if non-accepted
plans in the baseline should be accepted. As mentioned previously, manually loaded plans are
automatically marked as accepted, so manual loading forces the evolving process. When plans
are loaded automatically, the baselines are evolved using the EVOLVE_SQL_PLAN_BASELINE
function, which returns a CLOB reporting its results.
SET LONG 10000
SELECT DBMS_SPM.evolve_sql_plan_baseline(sql_handle => ‘SYS_SQL_7b76323ad90440b9’)
FROM dual;
* Manual plan loading can be used in conjunction with, or as an alternative to automatic plan
capture. The load operations are performed using the DBMS_SPM package, which allows SQL
plan baselines to be loaded from SQL tuning sets or from specific SQL statements in the cursor
cache. Manually loaded statements are flagged as accepted by default. If a SQL plan baseline is
present for a SQL statement, the plan is added to the baseline, otherwise a new baseline is
created.
* fixed (YES/NO) : If YES, the SQL plan baseline will not evolve over time. Fixed plans are used in
preference to non-fixed plans.