For which three requirements would you use the Database Resource Manager?

Database Resource Manager allows specifying an `IDLE_TIME` limit for consumer groups, which can be configured to detect and terminate sessions that are idle and actively blocking other sessions, thereby preventing resource contention.

DBRM enables administrators to limit the degree of parallelism for operations performed by user sessions belonging to a specific consumer group, ensuring that parallel execution does not excessively consume system resources.

Resource Manager plans can include directives that specify the maximum number of concurrent sessions allowed for a particular user or consumer group, helping to prevent resource exhaustion from an excessive number of active connections.

While Database Resource Manager can limit CPU usage, it typically does so by allocating CPU percentages or absolute limits over time to consumer groups, rather than directly by 'limiting the CPU used per database call' at such a granular level.

The amount of private space a session allocates in the shared pool, specifically within the Private SQL Area, is primarily managed by initialization parameters related to PGA and memory management (e.g., `PGA_AGGREGATE_TARGET`), not directly by the Database Resource Manager.