You are connected to an Oracle database Instance as a user with privileges to query the hr.employees table. You are not exempt from any reduction policies. Examine this query and result: You implement

Question

Exhibit

Options

• ANo rows will be returned.
• BFIRST_NAME LAST_NAME SALARY

  ---

  Steven King 24000
• CORA-28094: SQL construct not supported by data redaction
• DFIRST_NAME LAST_NAME SALARY

  ---

  Steven King XXXXX
• EFIRST_NAME LAST_NAME SALARY

  ---

  Steven King 0

• A
  9% (4)
• B
  4% (2)
• C
  67% (30)
• D
  18% (8)
• E
  2% (1)

Explanation

Option C is correct because the query contains a SQL construct - likely an expression, aggregate function, or operator applied to the redacted SALARY column - that Oracle Data Redaction's engine cannot safely process, so it raises ORA-28094 instead of returning any result. Oracle deliberately throws this error to prevent circumventing redaction through clever SQL constructs that might expose underlying values.

Why the distractors fail:

• A - Data Redaction never silently suppresses rows; it masks column values, not row visibility, so "no rows" is not how the feature works.
• B - The user is explicitly stated to be not exempt from redaction policies, so seeing the real salary (24000) is ruled out.
• D / E - These would be valid results for a simple SELECT with a character (XXXXX) or numeric (0) full-redaction policy respectively, but the unsupported SQL construct in the query prevents any redacted output from being generated at all.

Memory tip: Think of ORA-28094 as Oracle "throwing up its hands" - whenever a SQL construct is too complex for the redaction engine to safely mask (e.g., functions or expressions on a protected column), Oracle errors out rather than risk leaking real data. If the query were a plain SELECT salary FROM ..., you'd get 0 or XXXXX; complexity triggers the error.

No community discussion yet for this question.