Answers to Review Questions - OCP: Oracle Database 12c Administrator Certified Professional - page 685

7. D. Option A is incorrect because the user accounts are merged, not overwritten.
Option B is incorrect because the passwords are not overwritten. Answer C is incorrect
because the plugged-in user accounts become local user accounts, not common users.
8. E. None of the options A through D are correct because a local user is not permitted to
switch from one PDB to another.
9. A, B, D. Answer C is incorrect; local users may not create common users.
10. A, B, C. Answer D is incorrect because a local user does not have privileges on another
pluggable database.
11. E. Each answer is a valid capability of a privilege.
12. C, D. Answers A and B are not correct; this is a very bad idea. The SYSDBA privilege
allows a user to delete your database.
13. A, B. Option C is incorrect because you should never commonly grant privileges to the
PUBLIC role, because that would grant the privileges to all users.
14. A. Option B is incorrect because common and local users can grant local privileges.
Option C is incorrect because you can grant local privileges to local and common users.
15. A, B. Option C is incorrect because a role is a group of privileges or other roles, not a
group of users. You may of course grant a role to a group of users. Option D is incor-
rect because a group of containers is a CDB, not a role.
16. B, D. Option A is incorrect because the local user naming convention and the common
role naming convention are mutually exclusive. Option C is incorrect because you can-
not create common roles in PDBs; you must be in the CDB$ROOT to create a common role.
17. C. Option C is correct because, while creating too many roles can cause a nuisance,
it's the associated privileges that can cause damage. Also, you should safeguard the
DROP ANY ROLE privilege. Option B is not entirely correct because we added
the privileges modifier.
18. C. Options A, B, and D are acceptable options for granting roles, as long as the role
grantor has been granted the appropriate roles, locally or commonly. Option C is not
allowed because that would create a circular reference.
19. C. Options A and B are not true; common users with assigned privileges or roles may
create objects in PDBs.
20. A, D. Options B and C are valid create statements because, while it is not allowed to
have a role name and a user name that are the same, independently, "c##mydba" and
c##mydba are stored differently in the data dictionary.