Which three are true about using Database Resource Manager in an Oracle multitenant environment? (Choose three.)
Which three are true about using Database Resource Manager in an Oracle multitenant environment? (Choose three.)
In an Oracle multitenant environment, a CDB-level resource plan can limit PDB CPU utilization, ensuring that no single PDB consumes more than its allocated share of CPU resources. Additionally, a PDB-level resource plan can limit session PGA memory, allowing a fine-grained control over memory usage within a PDB. Finally, a PDB-level resource plan can also limit uncommitted UNDO per consumer group, which helps in managing the amount of undo data generated by users within a PDB. These features provide robust resource management capabilities across the multitenant architecture.
AB correct - no doubts D is correct instead of C, because - on the PDB level you manage resources more/less the same as in non-CDB database hence you can limit uncommitted UNDO per consumer group: https://docs.oracle.com/database/121/ADMIN/dbrm.htm#ADMIN11853 while from CDB level you cannot limit CPU on particular session level in PDB (it can be done on PDB level) but you can "only" limit CPU generally for particular PDB: https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/using-oracle-resource-manager-for-pdbs-with-sql-plus.html#GUID-19400E80-882F-424F-A19A-9FEB54F83577
D: corect The amount of undo generated by users in a PDB can be implemented with a PDB-level resource plan https://blogs.oracle.com/oraclemagazine/multitenant-database-management
I am not agree with D, there is not documentation about that. you can put limit only for cpu, memory parallelm, and I/O.
19c documentation... i dont know maybe, this point changed
Limit the CPU usage of a particular PDB Limit the number of parallel execution servers that a particular PDB can use Limit the memory usage of a particular PDB Specify the amount of memory guaranteed for a particular PDB Specify the maximum amount of memory a particular PDB can use Use PDB performance profiles for different sets of PDB A performance profile for a set of PDBs can specify shares of system resources, CPUusage, and number of parallel execution servers. PDB performance profiles enable you to manage resources for large numbers of PDBs by specifying Resource Manager directives for profiles instead of individual PDBs. Limit the resource usage of different sessions connected to a single PDB Limit the I/O generated by specific PDBs Monitor the resource usage of PDBs
I think ABD
Right asnwer
and why not F "When you create one or more PDB resource plans and there is no CDB resource plan, the CDB uses the DEFAULT_CDB_PLAN that is supplied with Oracle Database." then A B F
agree with F
not F (from student guide): If you delete an active CDB resource plan , then some directives in PDB resource plans become disabled. keyword=some
ABF, because i dont find any documentation about how limit undo, but, in all examples you need to create a CDBlevel resource plan.
https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-resources-with-oracle-database-resource-manager.html#GUID-A5C6447B-BFF5-4CCE-8114-8AD230375082 A,B,D are correct
I think ABC
https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/using-oracle-resource-manager-for-pdbs-with-sql-plus.html#GUID-075BDB11-8B9D-4061-98F6-8D4F07E3AB6D and https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-resources-with-oracle-database-resource-manager.html#GUID-514BDECF-BE80-4CCA-A00D-EF37C2CFC435
You can specify an undo pool for each consumer group. An undo pool controls the total amount of undo for uncommitted transactions that can be generated by a consumer group.
ABC correct
A CDB-level resource plan specifies the number of resources allocated to each PDB. A PDB-level resource plan can be used to allocate resources among the consumer groups (a maximum of eight) within a PDB. So it's not correct to say that a CDB-level resource plan will limit session CPU utilization. I would go with ABF.