Q: 8
Which two statements are true about Oracle synonyms?
Options
Discussion
Option D had something really close to this in a practice set. Picked D and A since I thought you could make a synonym for stuff inside a package if it's public, but maybe that's not allowed for inside items. Pretty sure about D though, at least from that mock.
C/D? Not sure since the package vs object in package thing keeps coming up, but I think it's A and C still.
A/C. Private synonym names only need to be unique per schema, so B is out. The catch is with D-synonyms can't point to objects inside a package, just the package itself. Pretty sure it's A and C but let me know if I'm missing a weird edge case.
Why is B tempting here? Private synonym name uniqueness is only within a schema, so multiple users can have the same private synonym name. This one catches folks out on practice exams.
Its A and C. Similar question popped up in official practice tests and Oracle docs-definitely recommend reviewing those for these synonym rules.
It’s A and C. You can chain synonyms (A) and anyone with the right privilege can create a public synonym (C). Not totally sure if I’m missing a catch here, but B isn’t right since private names only matter per schema.
Maybe A and C. You can have a synonym for another synonym, and with create public synonym privilege, any user can do it. Not totally certain, but D seems iffy because synonyms on objects in packages don't work that way. Correct me if I'm missing something.
C/D? Saw a similar question on a practice test, think it's one of those two.
A and C tbh, B trips people up since private synonym names only have to be unique per schema.
A and C tbh. Had a similar question before, you can create a synonym for another synonym and with the right perms any user can make a PUBLIC synonym. The others don’t line up with how private synonyms and packages work.
Be respectful. No spam.