Which three resources might be prioritized between competing pluggable databases when
creating a multitenant container database plan (CDB plan) using Oracle Database Resource
Manager?
A.
Maximum Undo per consumer group
B.
Maximum Idle time
C.
Parallel server limit
D.
CPU
E.
Exadata I/O
F.
Local file system I/O
Explanation:
C: parallel_server_limit
Maximum percentage of parallel execution servers that a PDB can use.
D: utilization_limit
Resource utilization limit for CPU.
Should be C D E
C, D, E – TRUE
http://docs.oracle.com/database/121/ADMIN/dbrm.htm#ADMIN11852
CDE
The correct answer is: C,D,E
CDE
I think ACDE
For A check here
http://docs.oracle.com/database/121/ADMIN/dbrm.htm#CHDBGIBD
E is not correct. In order to control the IO, the IORM on the storage server has to be configured.
Can’t be E since the question does not ask about Exadata. You assume this is on a regular server so ACD appears to be the more appropriate answer
CDE
ACD
http://docs.oracle.com/database/121/ADMIN/dbrm.htm#ADMIN11851
multitenant: c,d
not sure about e, but this gives some light: http://docs.oracle.com/cd/E50790_01/doc/doc.121/e50471/iorm.htm#SAGUG20444
a: 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. When the total undo generated by a consumer group exceeds its undo limit, the current DML statement generating the undo is terminated. No other members of the consumer group can perform further data manipulation until undo space is freed from the pool.
b:Idle time limit is also an option.
I go for c,d, e
In a CDB with multiple PDBs, some PDBs typically are more important than others. The
Resource Manager enables you to prioritize the resource (CPU and I/O, as well as allocation of parallel execution slaves in the context of parallel statement queuing) usage of specific PDBs. This is done by granting different PDBs different shares of the system resources so that more resources are allocated to the more important PDBs.
In addition, limits can be used to restrain the system resource usage of specific PDBs.
When a PDB is plugged in to a CDB and no directive is defined for it, the PDB uses the default directive for PDBs. As the CDB DBA, you can control this default and you can also create a specific directive for each new PDB.
Note: No consumer groups nor shares can be defined for the root container. Choice A is eliminated.
Management attributes enable you to specify CPU resource allocation for Exadata I/O.
Resource Manager can manage usage of the available parallel execution servers for a database
Correct: C, D, E
Local FS means no share, no RAC, that is no logical E-wrong
DE – http://www.oracle.com/technetwork/issue-archive/2014/14-nov/o64ocp12c-2349447.html
The question should be “Which two…”
Based on this reference it should be CPU and No of Parallel Execute Servers. That leads to C D in this section. Not sure why you said DE – not even talked about I/O in the reference.
not DE but CD / sorry
Parallel server limit
CPU
https://oracle-base.com/articles/12c/multitenant-resource-manager-cdb-and-pdb-12cr1
Look at the description of RSRC_PLAN_DIRECTIVES
http://docs.oracle.com/database/121/REFRN/GUID-375191F5-699B-4D3E-95EA-D94622E437E8.htm#REFRN23808
This should tell Shared, utilization_limit and Parallel_server
* shares
CDE
CDB resource Plan Basic limits
CPU, Exadata I/Os, and parallel servers usage of each PDB
Exadata I/O
Management attributes enable you to specify CPU resource allocation for Exadata I/O.
CDE
CDE
C,D,E are correct
Student guide says:
To limit the CPU, Exadata I/Os, and paralell servers (PARALLEL_SERVER_TARGET
initialization parameter) usage of each PDB, you can create a plan directive using the UTILIZATION_LIMIT parameter expressed as a percentage of the system resources the
PDB can use.
Resource Manager throttles the PDB sessions so that the CPU, Exadata I/Os, and parallel servers utilization for the PDB does not exceed the utilization limit.
ACD:
Not for E: more than 99.9% of databases are not running on EXADATA.
Exadata I/O: Management attributes enable you to specify CPU resource allocation for Exadata I/O.
this means E is also a kind of CPU time, which has been included in D.
The Types of Resources Managed by the Resource Manager
Resource plan directives specify how resources are allocated to resource consumer groups or subplans. Each directive can specify several different methods for allocating resources to its consumer group or subplan. The following sections summarize these resource allocation methods:
CPU
Exadata I/O
Parallel Execution Servers
Runaway Queries
Active Session Pool with Queuing
Undo Pool
Idle Time Limit
The reason I would go with CDE(Just failed my test yesterday btw tyvm) is that if you look at the DBMS_RESOURCE_MANAGER 12c documentation https://docs.oracle.com/database/121/ARPLS/d_resmgr.htm#ARPLS73823
it lists the create_cdb_plan procedure as using CPU and parallel(C and D) as parameters. If you look farther down it talks about a procedure creating a new category for Exadata, so (E).
the create_plan_directive is not as specific as create_CDB_plan, according to the question it is a “CDB_plan” so we go with parameters on “create_cdb_plan”, not idle_time and undo as per the create_plan_directive(which actually is applying to PDB plans, not CDB plans).
I guess I could have said it more simpler as the question refers to a CDB plan, not a PDB plan, so only CPU,parallel @ exadata parameters apply.
@CBass, did you select CDE in exam?
Was it in your feedback as a wrong answer?
Thanks