Oracle Database Vault is enabled In the database. You have these requirements: 1. Database administrator dbai must export and import data from and to a non-protected schema. 2. Database…

Question

Options

• AGrant become user to dbai.
• BGrant sysoper to both users.
• CRun d3ms_macadm.authorize_datapump_user procedure granting dbai privileges to impdp and
• DGrant imp_full_database and exp_full_database to dbai and dba2.
• ERun dbms_macadm.authobize_datapump_useb procedure granting dba2 privileges to impdp and
• FGrant become user to dba2.
• GGrant sysdba to both users.

• A
  47% (16)
• B
  6% (2)
• D
  26% (9)
• F
  6% (2)
• G
  15% (5)

Explanation

When Oracle Database Vault is enabled, standard DBA privileges are insufficient for Data Pump operations - both dba1 and dba2 require explicit Database Vault authorization. Option C (DBMS_MACADM.AUTHORIZE_DATAPUMP_USER for dba1) is required because Database Vault intercepts Data Pump jobs even on non-protected schemas; additionally, A (BECOME USER for dba1) is required so dba1 can impersonate the non-protected schema owner during export/import. For dba2 accessing a protected schema (a Database Vault realm), E (DBMS_MACADM.AUTHORIZE_DATAPUMP_USER for dba2) grants the realm-specific authorization needed - BECOME USER alone (option F) is not enough because realm protections block it.

Why the distractors fail:

• B/G (SYSOPER/SYSDBA): A core Database Vault design goal is to restrict privileged DBAs, including SYSDBA - these grants do not bypass realm protections.
• D (IMP/EXP_FULL_DATABASE): These are standard Data Pump roles, but with Database Vault active they are insufficient on their own without the DBMS_MACADM authorization.
• F (BECOME USER for dba2): Effective for non-protected schemas, but useless against a Database Vault realm - realms require explicit AUTHORIZE_DATAPUMP_USER.

Memory tip: Think "DV locks out even the boss" - Database Vault blocks SYSDBA and standard roles. For Data Pump under DV, the rule is: everyone needs AUTHORIZE_DATAPUMP_USER, and non-protected schema users additionally need BECOME USER to impersonate the schema owner.

No community discussion yet for this question.