OCP 1Z0 053 133

133.You performed the RMAN database backup with the KEEP option. Which two statements are true 
regarding this backup? (Choose two.) 
A. The backup contains data files, the server parameter file, and the control file even if the control file 
autobackup is disabled. 
B. The KEEP option overrides the configured retention policy. 
C. The backup contains only data files and archived redo log files. 
D. The KEEP option is an attribute of an individual backup piece. 
Answer: AB

http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmbckba.htm#CHDHAFHJ

Making Database Backups for Long-Term Storage

This section explains the basic concepts and tasks involved in making backups for long-term storage.

Purpose of Archival Backups

You can use BACKUP ... KEEP to create a backup that is both all-inclusive and exempt from the backup retention policy. The backup is all-inclusive because every file needed to restore and recover the database is backed up to a single disk or tape location. The KEEP option also specifies that the backup should be exempt from the retention policy either forever or for a specified period of time. The general name for a backup created with BACKUP ... KEEP is an archival backup.

As explained in "Data Preservation", one purpose of a backup and recovery strategy is to preserve data. You can use BACKUP ... KEEP to retain a database backup for longer than the time dictated by the retention policy. For example, you can back up the database on the first day of every year to satisfy a regulatory requirement and store the media offsite. Years after you make the archival backup, you could restore and recover it to query the data as it appeared at the time of the backup.

Another purpose of an archival backup is to create a backup to restore for testing purposes and then delete. For example, you can back up the database, restore the database in a test environment, and then discard the archival backup after the test database is operational. A related purpose is to create a self-contained backup that you can delete after transferring it to another user or host. For example, another user might want a copy of the database for reporting or testing.