You accidentally drop the CUSTOMERS table, and then recover it by using the FLASHBACK TABLE command. Which two statements are true about the dependent objects of the CUSTOMERS table?

Question

Options

• AAll the triggers associated with the table are flashed back but are disabled.
• BMaterialized views that use the CUSTOMERS table are flashed back.
• CLOB segments associated with the CUSTOMERS table are flashed back.
• DAll the constraints defined on the table, except the referential integrity constraints, are flashed
• EOnly the primary key constraint created for the table is flashed back, whereas all other indexes

• A
  3% (2)
• B
  10% (6)
• C
  83% (49)
• E
  3% (2)

Explanation

When Oracle drops a table (moving it to the Recycle Bin), LOB segments are physically stored alongside the table in the Recycle Bin and are fully recovered with FLASHBACK TABLE - making C correct. All constraints except referential integrity (foreign key) constraints are also restored - making D correct - because foreign key constraints reference other tables that may have changed since the drop, so Oracle cannot safely restore those relationships automatically.

A is wrong because triggers are flashed back in their original enabled/disabled state - they are not automatically disabled post-flashback. B is wrong because materialized views are independent objects; they are not stored in the Recycle Bin with the table and must be recreated manually. E is wrong because it understates the recovery: all non-referential constraints (not just the primary key) are restored, and indexes are also generally recovered.

Memory tip: Think "LOB and LOCAL constraints come back; LINKS to other tables (foreign keys) and LOOKUPS (materialized views) don't." The rule is simple - anything self-contained within the table is restored; anything involving cross-table relationships is not.

No community discussion yet for this question.