Which two configurations can be used to protect sensitive data In a database?

Question

Options

• Asetting the SQL92_SECURITy initialization parameter to false
• Benabling salt tor an encrypted column
• Ccreating a procedure that defines the VPD restrictions in a VPD policy
• Dcollecting sensitive data Information with Database Security Assessment Tool (DBSAT)
• Eenforcing row-level security at the table level
• Fenforcing row-level security at the database level

• A
  22% (8)
• B
  8% (3)
• C
  54% (20)
• D
  3% (1)
• E
  14% (5)

Explanation

C and F together describe Oracle's Virtual Private Database (VPD): Option C is correct because VPD requires creating a PL/SQL policy function (procedure) that dynamically generates a WHERE clause to restrict which rows a user can see. Option F is correct because VPD enforces this row-level security transparently at the database engine level, meaning no application can bypass it - unlike application-layer restrictions.

Why the distractors are wrong:

• A - Setting SQL92_SECURITY to false reduces security by removing the requirement for SELECT privileges on UPDATE/DELETE operations; true would be safer.
• B - Salt strengthens encryption by adding randomness to prevent dictionary attacks, but it's an encryption quality enhancement, not an access-control mechanism for protecting sensitive data access.
• D - DBSAT assesses and discovers sensitive data; it does not enforce any protection.
• E - Row-level security enforced "at the table level" implies application-side or trigger-based control, which can be bypassed; VPD enforces at the database level (F), making it policy-driven and tamper-resistant.

Memory tip: Think "VPD = C + F" - you need the Code (policy procedure) and the database-level Force (engine enforcement). If either is missing, VPD doesn't work - just like a lock needs both a mechanism and a door frame.

No community discussion yet for this question.