Which option enables Scott to eliminate the need to qualify the view with the name MARY.EMP_DEPT_LOC_VU each time the view is referenced?

Mary has a view called EMP_DEPT_LOC_VU that was created based on the EMPLOYEES,
DEPARTMENTS, and LOCATIONS tables. She granted SELECT privilege to Scott on this view.
Which option enables Scott to eliminate the need to qualify the view with the name
MARY.EMP_DEPT_LOC_VU each time the view is referenced?

A.
Scott cannot create any synonym for Mary’s view. Mary should create a private synonym for the
view and grant SELECT privilege on that synonym to Scott.

B.
Scott can create a synonym for the EMP_DEPT_LOC_VU by using the command
CREATE PRIVATE SYNONYM EDL_VU
FOR mary.EMP_DEPT_LOC_VU;
then he can prefix the columns with this synonym.

C.
Scott can create a synonym for the EMP_DEPT_LOC_VU by using the command
CREATE LOCAL SYNONYM EDL_VU
FOR mary.EMP_DEPT_LOC_VU;
then he can prefix the columns with this synonym.

D.
Scott can create a synonym for the EMP_DEPT_LOC_VU by using the command
CREATE SYNONYM EDL_VU
ON mary(EMP_DEPT_LOC_VU);
then he can prefix the columns with this synonym.

E.
Scott cannot create a synonym because synonyms can be created only for tables.

F.
Scott can create a synonym for the EMP_DEPT_LOC_VU by using the command
CREATE SYNONYM EDL_VU
FOR mary.EMP_DEPT_LOC_VU;
then he can prefix the columns with this synonym.

Explanation:

Correct syntax to create a local synonym is CREATE SYNONYM synonym_name. With PUBLIC
keyword you can create public synonym.