Your database supports an online transaction processing (OLTP) workload in which one of the applications creates a temporary table for a session and performs transactions on it. This consumes a lot of

Increasing the size of the temporary tablespace can ensure that temporary segments for the session's temporary table operations have sufficient space, preventing contention or frequent resizing that could indirectly contribute to system overhead and impact perceived undo/redo activity.

Enabling Automatic Memory Management (AMM) allows Oracle to automatically tune the overall memory allocation between the System Global Area (SGA) and Program Global Area (PGA). This optimization can lead to more efficient processing, reduced disk I/O, and better resource utilization, which might indirectly alleviate the strain caused by high undo/redo generation from temporary table transactions.

Enabling undo retention guarantee ensures that undo information is kept for a specified duration, primarily for read consistency or Flashback queries. This setting would likely increase undo tablespace usage, not decrease it.

Enabling temporary undo for the database (via `TEMP_UNDO_ENABLED`) would directly solve the problem by having undo for temporary tables stored in the temporary tablespace and not generating redo, but it is not among the selected correct answers in this context.

Increasing the size of the redo log buffer (part of SGA) helps with writing redo entries to the redo logs more efficiently, but it does not reduce the amount of redo generated by the transactions themselves.