You want to prevent a group of users in your database from performing long-running transactions that consume huge amounts of space in the undo tablespace. If the quota for these users is exceeded…

Specifying a quota usually restricts the overall space a user can allocate for segments (tables, indexes) within a tablespace, not the undo space consumed by transactions.

Decreasing Interested Transaction List (ITL) slots primarily affects concurrency on data blocks and can cause errors during high concurrent DML, but it does not directly limit total undo space consumption for a transaction.

Oracle profiles primarily set limits on session-level resources like CPU time, logical reads, or idle time, but they do not directly control or limit undo tablespace consumption for transactions.

Oracle Database Resource Manager (DBRM) allows you to define resource plans with directives like `UNDO_POOL` that limit the undo tablespace consumption for specific consumer groups. If the limit is exceeded during a DML operation, the transaction will abort and return an error, while queries are unaffected.