Which three are true about configuring CONTROLFILE AUTOBACKUP by using RMAN?

Question

Options

• AThe control file is backed up whenever a new tablespace is created.
• BThe server parameter file (SPFILE) is automatically backed up each time the control file is
• CThe control file is backed up whenever a new table is created.
• DThe control file is backed up whenever an RMAN backup is successfully recorded in the
• EIt requires the use of fast recovery area (FRA).
• FThe control file is backed up automatically each time the SPFILE is backed up manually.

• A
  85% (29)
• C
  3% (1)
• D
  9% (3)
• E
  3% (1)

Explanation

When CONTROLFILE AUTOBACKUP ON is configured, Oracle automatically backs up the control file after structural database changes - creating a tablespace (A) qualifies because it alters the physical structure tracked in the control file, while creating a table (C) is merely a data dictionary operation and does not. The control file autobackup always packages the SPFILE alongside the control file in the same backup piece (B), and this works in both directions - manually backing up the SPFILE via RMAN also fires the autobackup of the control file (F). Option D is wrong because the trigger is completion of an RMAN backup command, not the passive act of recording a backup entry in the repository; option E is wrong because FRA is entirely optional - you can specify a custom FORMAT clause for the autobackup destination instead.

Memory tip: Think "Structure + SPFILE travel together." Autobackup fires on structural changes (tablespaces, datafiles - not tables) and always brings the SPFILE along for the ride. If you remember that tables live in segments managed by the data dictionary rather than control file structure, option C is easy to eliminate.

No community discussion yet for this question.