Which three resources might be prioritized between competing pluggable databases when creating a multitenant container database plan (CDB plan) using Oracle Database Resource Manager?

Maximum Undo per consumer group is a valid CDB resource plan directive that limits the amount of undo space a PDB's sessions can consume. This prevents a single PDB from exhausting shared undo space in the CDB, ensuring fair access to undo resources across all pluggable databases.

Maximum Idle Time is a consumer group-level directive within a PDB plan used to disconnect idle sessions, not a resource type used to prioritize resources between competing PDBs at the CDB level.

The PARALLEL_SERVER_LIMIT directive in a CDB plan caps the percentage of parallel execution servers a PDB may use at any time. By setting this limit per PDB, the CDB resource plan ensures that one PDB cannot consume all available parallel slaves, preserving parallel query resources for other PDBs.

CPU is the foundational resource managed by CDB plans, controlled through share-based allocation and utilization limit directives. These settings determine the proportional CPU time each PDB receives during contention, making CPU management the primary purpose of CDB resource plans.

Exadata I/O rate management is specific to Oracle Exadata Database Machine environments and is not a standard CDB plan resource available in non-Exadata Oracle Database installations.

Local file system I/O is not a resource category managed or prioritized by Oracle Database Resource Manager in CDB or PDB resource plans.