Which two statements are true when row archival management is enabled?

Question

Options

• AThe ORA_ARCHIVE_STATE column visibility is controlled by the ROW ARCHIVAL
• BThe ORA_ARCHIVE_STATE column is updated manually or by a program that could
• CThe ROW ARCHIVAL VISIBILITY session parameter defaults to active rows only.
• DThe ORA_ARCHIVE_STATE column is visible if referenced in the select list of a query.
• EThe ORA_ARCHIVE_STATE column is updated automatically by the Oracle Server based on

• A
  7% (2)
• B
  82% (23)
• C
  4% (1)
• E
  7% (2)

Explanation

B is correct because ORA_ARCHIVE_STATE is an application-managed column - Oracle Server never automatically updates it. A value of '0' means active; any other value means archived. It is the responsibility of user code or a program to update this column to mark rows as archived.

D is correct because ORA_ARCHIVE_STATE is a hidden (invisible) column, meaning SELECT * will not return it. However, if you explicitly name it in the SELECT list (e.g., SELECT ORA_ARCHIVE_STATE FROM employees), it is returned normally.

Why the distractors are wrong:

• A is wrong because column visibility is governed by the ROW ARCHIVAL VISIBILITY session parameter, not by the ROW ARCHIVAL clause itself (which only creates the column structure).
• C is wrong because the ROW ARCHIVAL VISIBILITY session parameter defaults to ALL rows, not active rows only - you must explicitly set it to ACTIVE to filter out archived rows.
• E is the opposite of B: Oracle does not auto-update ORA_ARCHIVE_STATE; that is precisely why B is true.

Memory tip: Think of In-Database Archiving as a "sticky flag your app must set." Oracle gives you the hidden column and the filter knob (ROW ARCHIVAL VISIBILITY), but you flip the flag - Oracle never does it for you. That locks in B. And hidden columns behave like a shy guest: they won't show up uninvited (SELECT *), but they'll answer if you call them by name - locking in D.

No community discussion yet for this question.