Which three RMAN persistent settings can be set explicitly?

Question

Options

• ASPFILE backup duplexing
• Bcontrol file auto backup formats
• Carchive log deletion policy
• Dimage copy duplexing
• Eredo log backup duplexing
• Farchive log backup duplexing

• A
  11% (6)
• B
  79% (42)
• D
  6% (3)
• E
  4% (2)

Explanation

RMAN's CONFIGURE command supports persistent settings for control file autobackup formats (B), archivelog deletion policy (C), and archivelog backup copies/duplexing (F) - these each have dedicated CONFIGURE syntax (CONFIGURE CONTROLFILE AUTOBACKUP FORMAT, CONFIGURE ARCHIVELOG DELETION POLICY, and CONFIGURE ARCHIVELOG BACKUP COPIES) that survive across RMAN sessions. Options A and E are incorrect because RMAN has no separate persistent setting to duplex SPFILE backups or online redo log backups as distinct categories - SPFILE is bundled into general backup set behavior, and online redo logs are not directly backed up by RMAN (archived logs are). Option D is incorrect because image copies cannot be duplexed at all; duplexing applies only to backup sets (backup pieces), not image copies, which are by nature single-file replicas.

Memory tip: Think "CAF" - Control file format, Archivelog deletion policy, File copies (archivelog backup duplexing) - the three things RMAN lets you explicitly CONFIGURE as persistent settings in this group.

No community discussion yet for this question.