Choose the best answer. Examine this configuration: 1. CDB1 is a container database. 2. There are several pluggable databases (PDBs) in CDB1. 5. Each PDB has several tables with referential…

Question

Options

• Arestore and recover database
• Bflashback transaction
• Cflashback database
• Dflashback table and transaction
• Eflashback table

• A
  2% (1)
• B
  14% (7)
• C
  76% (37)
• D
  2% (1)
• E
  6% (3)

Explanation

FLASHBACK DATABASE is correct because it operates at the CDB level, rewinding the entire container database - including all PDBs and their data - to a prior point in time with a single FLASHBACK DATABASE TO ... command. The configuration explicitly enables this feature (FLASHBACK DATABASE IS ON), making it directly applicable. Since the undesired changes span all PDBs, only a CDB-level operation can address everything atomically in one command.

Why the distractors fail:

• A (restore and recover database): Requires multiple RMAN commands (RESTORE, RECOVER, OPEN RESETLOGS) - not a single command, and more operationally heavy than necessary.
• B (flashback transaction): Targets individual transactions by XID; it cannot sweep across multiple tables in multiple PDBs in one shot.
• D (flashback table and transaction): Not a real Oracle feature as a combined single operation - this is a fabricated distractor.
• E (flashback table): Works on a single table within a single PDB; multiple commands would be needed for every affected table in every PDB.

Memory tip: Scope your flashback to the scope of the damage. Changes across all PDBs = CDB-level fix = FLASHBACK DATABASE. If the question said "one table in one PDB," the answer would shift down to FLASHBACK TABLE.

No community discussion yet for this question.