The persistent configuration settings for RMAN have default for all parameters. Identify four RMAN commands that produce a multi-section backup.

The SYSTEM tablespace contains regular datafiles, so specifying SECTION SIZE 100M causes RMAN to divide each datafile into 100MB sections backed up in parallel across channels, producing a genuine multi-section backup set.

Image copy backups (AS COPY) in Oracle 12c fully support the SECTION SIZE parameter, allowing RMAN to produce multi-section image copies of the SYSTEM tablespace datafiles backed up in parallel.

Archive log files are discrete, immutable log files that RMAN backs up as complete units; the SECTION SIZE clause does not apply to archive log backups and the command does not produce a multi-section backup.

Temporary tablespace datafiles hold only transient sort and hash data that is never recovered, so RMAN explicitly disallows backing up temporary tablespaces and the command returns an error rather than producing any backup.

The UNDO tablespace consists of standard datafiles that support multi-section backup; the INCLUDE CURRENT CONTROLFILE clause appends the controlfile as a separate backup piece but does not disable multi-section behavior for the undo datafiles, so sections are still produced.

The SPFILE is a small single binary file that RMAN backs up as one indivisible piece; the SECTION SIZE parameter is not honored for SPFILE backups and the result is a single-section backup regardless of the size specified.

An incremental level 0 backup is a full datafile image that supports SECTION SIZE just like a non-incremental backup, so BACKUP INCREMENTAL LEVEL 0 TABLESPACE SYSAUX SECTION SIZE 100M correctly generates multiple sections per datafile.