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

BACKUP TABLESPACE SYSTEM SECTION SIZE 100M divides the SYSTEM tablespace datafile(s) into 100MB sections, each backed up as a separate piece within the backup set. This is the standard syntax for producing a multi-section backup of a regular tablespace.

BACKUP AS COPY with SECTION SIZE creates multi-section image copies by splitting the copy operation into independently processed 100MB sections. Oracle supports the SECTION SIZE clause for both backup sets and image copies of datafiles.

RMAN does not support multi-section backup for archive log files - the SECTION SIZE clause is valid only for datafile backup operations, and archive logs are always backed up as complete, unsplit units.

RMAN cannot back up temporary tablespaces because they contain no persistent data - temporary segments are recreated at instance startup and are explicitly excluded from all RMAN backup and recovery operations.

BACKUP TABLESPACE UNDO INCLUDE CURRENT CONTROLFILE SECTION SIZE 100M creates a valid multi-section backup because the SECTION SIZE clause applies to the undo tablespace datafile sections. The INCLUDE CURRENT CONTROLFILE option appends the control file to the same backup job without affecting the section-based processing of the datafiles.

The SPFILE is a small server parameter file for which the SECTION SIZE clause is not supported - multi-section backup applies exclusively to datafiles and does not extend to SPFILE backups.

BACKUP INCREMENTAL LEVEL 0 with SECTION SIZE is a supported multi-section incremental backup - Oracle allows multi-section processing for both full and incremental level 0 datafile backups, enabling the same parallelism benefits for incremental backup strategies.