Your database is running in ARCHIVELOG mode and flashback is enabled. In which scenario must you use RMAN backups for recovering tables and table partitions? Choose the best answer.

The correct answer is A. when recovering data that was lost after a DDL operation modified the structure of a table. See the full explanation below for the reasoning.

Question

Options

Awhen recovering data that was lost after a DDL operation modified the structure of a table
Bwhen recovering dropped tables that are present in the recyclebin
Cwhen recovering a table that has been logically corrupted
Dwhen recovering a table to a point in time
Ewhen recovering the data of a table to the desired point in time, which is more recent than the

How the community answered

(51 responses)

A
78% (40)
B
2% (1)
C
4% (2)
D
4% (2)
E
12% (6)

Community Discussion

Ola B.May 24, 2026

The correct answer is A. Flashback features like Flashback Table and Flashback Query can handle logical corruption, point-in-time recovery, and recyclebin restores on their own, but the moment a DDL like ALTER TABLE or TRUNCATE has structurally changed the table, you have crossed a line that flashback cannot undo because those changes are not logged the same way, so RMAN is your only path back.

Grace U.May 30, 2026

A is the one to lock in, and the reason actually makes the other options easier to dismiss. Flashback Table works by reading undo data, and DDL operations like ALTER TABLE don't generate the kind of undo that flashback can reverse, so once a structural change has been made, flashback simply has nothing to work with and RMAN becomes your only path. The other scenarios, dropping a table that is still in the recyclebin, logical corruption within your undo retention window, or a point-in-time recovery that falls inside that same window, can all be handled without touching RMAN at all. What trips people up here is that the question is not asking when RMAN is useful, it is asking when it is required, and that word "must" is doing a lot of work. Once you recognize that DDL blocks flashback from functioning, A becomes the clear standout and the rest of the options describe situations where you have a choice.

Viktor S.May 21, 2026

E, because flashback only goes so far back and RMAN covers the rest.

Ola B.May 22, 2026

Viktor, the answer is A because Flashback Database rewrites the datafiles to a prior SCN using flashback logs, which is exactly what the question is asking about, while RMAN would be needed for a full restore/recovery scenario, not a flashback operation.

Nina C.May 9, 2026

Logical corruption is exactly what flashback cannot fix, so RMAN is your only option there.

-1

Grace U.May 9, 2026

Nina, you actually have it flipped, and it is a really common mix-up. Flashback is precisely the Oracle tool designed for logical corruption, think accidentally dropped tables or bad DML transactions, while RMAN shines at recovering from physical, block-level damage.

Bao N.Apr 27, 2026

Been grinding through the 1Z0-067 practice sets all week and this one keeps coming up, so let me break down why I am locking in C on this. Logical corruption is the exact scenario where Flashback Database and Flashback Table both fall flat, because those features rely on undo data and flashback logs to reverse changes, but if the table structure and row data look perfectly valid to Oracle yet the business logic behind them is broken, the database engine has no way to distinguish good data from bad. You cannot flashback your way out of a situation where the corruption is at the application meaning layer, not the block or transaction layer. RMAN is the one path that lets you pull a clean, known-good backup from before the corruption crept in, restore to a point where the data was still trustworthy, and bring just those objects forward without touching the rest of the database. Options A, B, D, and E all describe scenarios where Flashback features or Recycle Bin recovery handle things natively, so C is the one case where you are forced to go to RMAN.

-2

Full 1Z0-067 Practice