Examine this list of capabilities: 1. You can automatically restrict common users from accessing pluggable database (PDB). 2. Enabling Database Vault Operations Control In cdbsroot does not…

Question

Options

• A3, 5, 6
• B2, 3. 6
• C2, 4, 6
• D1, 4, 6
• E1, 2, 3, 5

• A
  81% (25)
• B
  10% (3)
• C
  3% (1)
• E
  6% (2)

Explanation

Option A is correct because statements 3, 5, and 6 accurately describe Database Vault Operations Control: a common user holding the DV_ADMIN role has the authority to enable it (3); Oracle provides an exception list mechanism so that legitimate common users and invoker's-rights procedures requiring PDB local data access are not blocked outright (5); and DBMS_MACADM.DISABLE_APP_PROTECTION is the valid procedure to disable the feature (6).

The distractors fail for specific reasons: statement 1 is wrong because Operations Control is never automatic - a DBA must explicitly enable it; statement 2 is the reverse of the truth - enabling Operations Control in CDB$ROOT does automatically propagate to all PDBs, which is one of its key design points; and statement 4 is wrong because ENABLE_APP_PROTECTION is not the procedure used to enable Operations Control - the correct procedure is DBMS_MACADM.ENABLE_DV_OPERATIONS_CONTROL, making this a classic "right concept, wrong API name" trap.

Memory tip: Remember that Operations Control flows top-down automatically (CDB$ROOT → PDBs), so any statement saying it does not propagate automatically is a red flag. Also watch for asymmetric procedure names on Oracle exams - enable and disable operations don't always mirror each other, and swapping them is a reliable distractor technique.

No community discussion yet for this question.