Which three statements are true about Flashback Data Archive?

Question

Options

• ATo use Flashback Data Archive, users must have unlimited quota on the Flashback Data
• BTo enable Flashback Data Archive for a table, it is mandatory to have a default Flashback
• CWhile enabling Flashback Data Archive for a table, if no name is provided for Flashback Data
• DA table enabled for Flashback Data Archive cannot be dropped unless Flashback Data Archive
• EFlashback Data Archive prevents flashback queries from getting a snapshot-too-old error.

• A
  9% (3)
• B
  16% (5)
• C
  75% (24)

Explanation

C is correct because when you run ALTER TABLE ... FLASHBACK ARCHIVE without naming a specific archive, Oracle automatically routes the table to the designated default Flashback Data Archive - one must exist, but you don't have to name it explicitly.

D is correct because FDA places a protection on the table: attempting to DROP TABLE while FDA is active will raise an error. You must first run ALTER TABLE ... NO FLASHBACK ARCHIVE to remove the protection before the table can be dropped.

E is correct because FDA stores row history in a dedicated tablespace independent of the undo segment, so flashback queries can reach back to the FDA's retention limit without ever hitting the dreaded ORA-01555 "snapshot too old" error.

A is wrong because users querying FDA-tracked data need no quota on the FDA tablespace - quota management there is handled entirely by the DBA who creates and maintains the archive.

B is wrong because a default FDA is convenient but not required; you can always specify a named FDA explicitly (ALTER TABLE t FLASHBACK ARCHIVE fda_name), so having a default configured is optional.

Memory tip: Think of FDA with three rules - Default fills in, Dropping is blocked, Errors are gone (C, D, E). The two wrong options both describe unnecessary restrictions on users/DBAs that Oracle intentionally does not impose.

No community discussion yet for this question.