You want to create a role to meet these requirements: 1. The role is to be protected from unauthorized usage. 2. The password of the role is not to be embedded in the application source code or stored in a table. Which method would you use to restrict enabling of such roles?

Question

Accepted Answer

B. Create the role as a secure application role. A secure application role (created with IDENTIFIED USING package_name) ties role enablement to a trusted PL/SQL stored procedure that can verify session context, application state, or other conditions before granting the role - protecting against unauthorized use while ensuring no password is ever embedded in source code or stored in a table, satisfying both requirements.

Answer

A. Create the role with external authentication. An externally authenticated role relies on OS credentials for role assignment but does not provide the application-level policy enforcement needed to meet both requirements without relying on OS identity.

Answer

C. Create the role as a password-protected role. A password-protected role requires the application to supply the password at runtime, which must either be hardcoded in source code or stored in a database table - directly violating requirement 2.

Answer

D. Create a role and use Fine-Grained Access Control (FGAC) to secure the role. Fine-Grained Access Control (VPD/FGAC) restricts data access at the row or column level and is not a mechanism for controlling role enablement or protecting the role activation process.

You want to create a role to meet these requirements: 1. The role is to be protected from unauthorized usage. 2. The password of the role is not to be embedded in the application source code or…

Question

Options

How the community answered

Why each option

Topics

Community Discussion