Q: 9
Which three are true about system and object privileges
Options
Discussion
I don't think it's C. A is a trap for system vs object, so A D F.
A D, F
My vote is A, D, and F are the ones here. WITH GRANT OPTION applies to object privs for users/roles (A), and revoking with that option does cascade (D). For F, you definitely need REFERENCES if you're doing a cross-schema foreign key. Not 100% though, could be missing a trick somewhere.
Probably A, D, F. These match my notes on grant/revoke behavior and privilege requirements for constraints. Pretty sure about D and F especially.
My pick: C, D, E. I was thinking that revoking a system privilege with ADMIN OPTION should also remove it from whoever it was passed to, so C looked good. Plus, adding constraints in another schema typically needs extra privileges. I'm not 100% sure on E vs F since REFERENCES is object-specific, but went with E here. Open to corrections if I'm mixing up privilege types.
I remember a similar question, and went with A, D, E. Adding a primary key in another schema seems like it should need a system privilege, not just object privileges. Pretty sure about A and D, but not 100% about E over F. Let me know if you see it differently.
Maybe C here.
D , had something like this in a mock and A D F were the correct picks there as well.
C/D/F? The cascade effect for system privileges with WITH ADMIN OPTION (C) is sometimes confused with object privileges and WITH GRANT OPTION (D). For F, REFERENCES is definitely needed if the foreign key crosses schemas. I think D and F are solid, but not 100% on C vs A since A might be stretching the scope. Could use some extra eyes on this.
A D, F for me. WITH GRANT OPTION works for object privileges to users/roles (A), and revoking it does cause a cascade (D). F is true too since you need REFERENCES to point a foreign key at a table in another schema. Pretty sure this combo is what the question wants, but let me know if I missed something.
Be respectful. No spam.