Which two are true about instance recovery? (Choose two.)

The correct answer is C. Setting FAST_START_MTTR_TARGET to a lower value reduces instance recovery time by F. It is performed automatically while the database remains in MOUNT state. Then the database is. C is correct because setting FAST_START_MTTR_TARGET to a lower value tells Oracle to recover faster, which it achieves by increasing checkpoint frequency - dirty buffers are written to disk more often, so less redo needs to be reapplied after a crash. F is correct because…

Backup and Recovery

Question

Options

AIt is not possible if an archived log is missing.
BIt is performed automatically after the database is opened; however, blocks requiring recovery are
CSetting FAST_START_MTTR_TARGET to a lower value reduces instance recovery time by
DIt is performed by the Recovery Writer (RVWR) background process.
ESetting FAST_START_MTTR_TARGET to a higher value reduces instance recovery time by
FIt is performed automatically while the database remains in MOUNT state. Then the database is

How the community answered

(41 responses)

A
2% (1)
B
7% (3)
C
78% (32)
E
12% (5)

Explanation

C is correct because setting FAST_START_MTTR_TARGET to a lower value tells Oracle to recover faster, which it achieves by increasing checkpoint frequency - dirty buffers are written to disk more often, so less redo needs to be reapplied after a crash. F is correct because instance recovery is performed automatically by SMON while the database is still in MOUNT state; the database is not opened to users until recovery completes, ensuring a consistent state before access is granted.

Why the distractors are wrong:

A is wrong - instance recovery uses only online redo logs, not archived logs; missing archived logs would block media recovery, not instance recovery.
B is wrong - recovery happens before the database opens (in MOUNT state), not after; B describes deferred/lazy block recovery, which is a separate concept.
D is wrong - RVWR (Recovery Writer) writes flashback logs; instance recovery is performed by SMON (System Monitor).
E is the inverse trap - a higher FAST_START_MTTR_TARGET means Oracle is less aggressive with checkpointing, increasing potential recovery time, not reducing it.

Memory tip: Think "MTTR target = speed promise to yourself." A lower promise (shorter time) forces Oracle to checkpoint more aggressively, keeping recovery fast. And remember the acronym order: MOUNT → Recover → OPEN - the database never opens until instance recovery is done.

Topics

#Instance Recovery#FAST_START_MTTR_TARGET#Database Startup#Crash Recovery

Community Discussion

No community discussion yet for this question.

Full 1Z0-083 Practice