If a column is not specified in a Data Redaction Policy, to which column(s) is it applied?

Question

Options

• Anone of the columns
• Bforeign key columns only
• Cthe primary and foreign key columns
• Dcolumns with any type of constraint
• Ethe primary key column only

• B
  4% (1)
• C
  88% (22)
• D
  8% (2)

Explanation

In Oracle Data Redaction, when a column is not explicitly defined within a redaction policy, the policy automatically applies to the primary key and foreign key columns by default - this is a protective fallback to ensure that key relational columns remain covered even when not individually specified, preventing accidental data exposure through table relationships.

Why the distractors are wrong:

• A (none of the columns) is wrong because unspecified columns don't simply escape the policy - key columns get covered by default.
• B (foreign key columns only) is a partial answer; it misses primary keys, which are equally important identifiers.
• D (columns with any constraint) overgeneralizes - not every constraint (e.g., NOT NULL, UNIQUE, CHECK) triggers default redaction.
• E (primary key only) is the mirror of B - it captures half the truth but ignores foreign keys, which also serve as identifiable linkage columns.

Memory tip: Think "PK + FK = the keys to your data relationships." Since these columns are the glue between tables, Oracle's default behavior protects both sides of the key pair when you forget to specify a column - remember Primary + Foreign = Protected by Fallback.

No community discussion yet for this question.