Which three statements are true about Flashback Database?

The correct answer is A. Flashback logs are written sequentially, and are archived. C. The Oracle database automatically creates, deletes, and resides flashback logs in the Fast F. Flashback logs are used to restore to the blocks' before images, and then the redo data may. Flashback Database works by capturing before-images of modified blocks in flashback logs, then replaying redo to roll forward to the exact target point. Why A, C, F are correct: A: Flashback logs are written sequentially (unlike redo, which has more complex I/O patterns)…

Backup and Recovery

Question

Options

AFlashback logs are written sequentially, and are archived.
BFlashback Database uses a restored control file to recover a database.
CThe Oracle database automatically creates, deletes, and resides flashback logs in the Fast
DFlashback Database can recover a database to the state that it was in before a reset logs
EFlashback Database can recover a data file that was dropped during the span of time of the
FFlashback logs are used to restore to the blocks' before images, and then the redo data may

How the community answered

(35 responses)

A
77% (27)
B
6% (2)
D
3% (1)
E
14% (5)

Explanation

Flashback Database works by capturing before-images of modified blocks in flashback logs, then replaying redo to roll forward to the exact target point.

Why A, C, F are correct:

A: Flashback logs are written sequentially (unlike redo, which has more complex I/O patterns), making writes efficient. They reside persistently on disk in the FRA.
C: Oracle fully automates flashback log lifecycle - creation, sizing, deletion - entirely within the Fast Recovery Area. No DBA management is needed.
F: This is the exact two-phase mechanism: flashback logs first restore data blocks to their before-images (rewinding), then redo logs roll the database forward to the precise target SCN or timestamp.

Why the distractors are wrong:

B: Flashback Database uses the current control file - no restored control file is needed. Needing a restored control file implies traditional incomplete recovery (RMAN restore/recover), not Flashback Database.
D: The flashback window cannot cross a RESETLOGS boundary by default. An OPEN RESETLOGS resets the redo stream, which walls off earlier flashback history.
E: A data file dropped within the flashback window is unrecoverable via Flashback Database alone - dropped data files require datafile-level point-in-time recovery, not a database-level flashback.

Memory tip: Think "FRA-managed, two-phase rewind" - Oracle owns the logs (C), writes them sequentially (A), rewinds blocks then fast-forwards with redo (F). Flashback Database cannot jump RESETLOGS walls or resurrect dropped files.

Topics

#Flashback Database#Flashback Logs#Fast Recovery Area#Block Recovery Mechanism

Community Discussion

No community discussion yet for this question.

Full 1Z0-083 Practice