Which three are benefits of using temp UNDO when performing DML on global temporary tables?

Temp UNDO, introduced in Oracle 12c and refined in 23ai, stores undo for global temporary tables

(GTTs) in temporary tablespaces:

A . It permits DML on GTTs even if the database is opened read-only.False. In read-only mode, DML

on GTTs is allowed regardless of temp UNDO, as GTT data is session-private, but temp UNDO doesn’t

specifically enable this.

B . It reduces the amount of UNDO stored in the UNDO tablespace.True. Temp UNDO stores undo in

the temporary tablespace, reducing usage of the permanent UNDO tablespace.

C . It reduces I/Os to the SYSTEM tablespace.True. By avoiding permanent undo, it reduces metadata

updates in the SYSTEM tablespace related to undo management.

D . It reduces the amount of redo generated.True. Temp UNDO changes are not redo-logged to the

same extent as permanent undo, minimizing redo generation.

E . It reduces I/Os to the SYSAUX tablespace.False. SYSAUX is unrelated to undo management; temp

UNDO affects temporary and SYSTEM tablespaces.

Reference:Oracle Database Concepts 23ai, "Temporary Undo."