Oracle Database Administration from Zero to Hero - Managing Roles (Part 2 of 2)

This lecture covers the management of roles in Oracle databases, focusing on password-protected roles, enabling roles in applications, and the public role. It explains how to drop roles and the security implications, explores dictionary views for role information, and provides best practices for role management. The lecture concludes with a summary and a preview of the next topic on user profiles.

What is the purpose of using password-protected roles in databases?

• To automatically enable roles for all users

• To ensure roles are only enabled for specific applications

• To make role management easier for administrators

• To allow users to change their roles at will

Which statement is used to remove a password-protected role from a user's default roles list?

• ALTER USER DEFAULT ROLE ALL EXCEPT

• SET ROLE ROLE NAME

• CREATE ROLE WITH IDENTIFIED BY

• GRANT ROLE TO USER

What is a key characteristic of the public role in Oracle databases?

• It can be dropped by any user with admin privileges

• It is automatically granted to every database user

• It appears in the DBA roles data dictionary

• It must be manually assigned to each user

Why should you be cautious when granting privileges to the public role?

• It is difficult to revoke privileges once granted

• It is not supported in all Oracle database versions

• It can lead to unauthorized access if not managed properly

• It requires additional configuration steps

What happens to the security domains of users when a role is dropped?

• They remain unchanged

• They need to be manually updated

• They are automatically updated to reflect the change

• They are deleted along with the role

Which view retrieves all roles in the database?

• ROLE SYSBREVS

• SESSION ROLES

• DBA ROLES

• DBA ROLE BRIEFS

What is the scope of views that do not start with the DBA or user prefix?

• They are deprecated in newer versions

• They are specific to the current session

• They are global across all sessions

• They are only available to administrators

What is a recommended practice when granting privileges?

• Grant all available privileges to simplify management

• Use roles instead of granting privileges directly to users

• Avoid documenting privilege grants to reduce paperwork

• Grant privileges based on verbal requests

Why is it important to review current grants regularly?

• To increase the number of privileges available

• To reduce the number of roles in the system

• To comply with database software updates

• To ensure they are still valid and necessary

What is a benefit of splitting the DBA role from the developer's role?

• It ensures developers have access to all system privileges

• It allows developers to have full control in production

• It simplifies the deployment process into production

• It reduces the need for auditing