A: FALSE, a user needs privilege CREATE PUBLIC SYNONYM to do it B: TRUE SQL> SELECT owner, object_type, object_name, object_id FROM dba_objects WHERE object_id=20770; OWNER OBJECT_TYPE OBJECT_NAME OBJECT_ID -------------------- ----------- ---------------- ---------- GSMADMIN_INTERNAL SYNONYM DDL_REQUESTS_PWD 20770 C: FALSE; D: FALSE SQL> SELECT object_name, object_type, object_id, owner FROM dba_objects WHERE object_type='SYNONYM' AND owner LIKE 'KOTELNIK%'; OBJECT_NAME OBJECT_TYPE OBJECT_ID OWNER --------------- ----------- ---------- ----------- EMPLOYEES_S SYNONYM 76119 KOTELNIK1 EMPLOYEES_S SYNONYM 76128 KOTELNIK2E: E: TRUE, https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/CREATE-SYNONYM.html#GUID-A806C82F-1171-478E-A910-F9C6C42739B2 Use the CREATE SYNONYM statement to create a synonym, which is an alternative name for ... another synonym

The same question as in 1z0-071 Question #: 270

AD is correct. A -TRUE: You can create both public and private synonyms. A public synonym is owned by the special user group named PUBLIC and is accessible to every user in a database. A private synonym is contained in the schema of a specific user and available only to the user and to grantees for the underlying object.

CE same question in 1z0-071

Provided answer are wrong, C and E are corrects in my opinion: A. Any user can create a public synonym. --> False, you need grants. B. A synonym has an object number. --> False, OBJECT ID C. A synonym can be created on an object in a package. --> True. you can grant to object type like function, store procedure, etc. D. All private synonym names must be unique in the database. --> False, must be unique in the SCHEMA. E. A synonym can have a synonym. --> True.

B D is correct