11.10. Answers to Review Questions

  1. C. While the DBA role will grant the ADMINISTER_RESOURCE_MANAGER privilege, DBA is not a valid system privilege name.

  2. E. A plan directive can only allocate CPU resources to a sub-plan. A, B, C, and D are all valid allocation methods, but they can only be defined for a resource consumer group, not for a sub-plan.

  3. D. MODULE_ACTION is not a valid attribute by itself. The DBMS_APPLICATION_INFO package allows applications to define an application name and, secondarily, the action that they are currently performing. In general, the action without a corresponding name isn't useful. Therefore, MODULE_NAME and MODULE_NAME_ACTION are both useful and valid mapping attributes, but not MODULE_ACTION.

  4. E. A single-level resource plan can allocate CPU resources to consumer groups using either the RATIO or the EMPHASIS (percentage) method. A multi-level resource plan is limited to using the EMPHASIS method exclusively. BASIC is not a valid CPU allocation method.

  5. A. The ALTER SYSTEM statement sets NIGHT_PLAN as the enabled plan. The FORCE: prefix restricts the setting from being changed.

  6. D. Simple resource plans can define up to eight levels of CPU allocation.

  7. A. The SWITCH_TIME_IN_CALL parameter will cause the offending session to be switched for the duration of the current operation. It will then revert to its original group.

  8. C. When objects in the pending area are submitted, they become active and are stored in the data dictionary.

  9. C. The SET_CONSUMER_GROUP_MAPPING procedure is used to map session attributes to consumer groups.

  10. E. The OTHER_GROUPS consumer group is assigned to sessions whose assigned group is not contained in the enabled plan. Therefore, Oracle requires that an allocation be made so that no sessions will be completely deprived of resources.

  11. B. The SET_MAPPING_PRIORITY procedure allows for prioritization based on the session attribute type.

  12. A, C. The SWITCH_CONSUMER_GROUP_FOR_SESS procedure will switch a single session. The procedure SWITCH_CONSUMER_GROUP_FOR_USER will switch all sessions owned by a user.

  13. D. If a session belongs to a consumer resource group that receives no allocation of resources from the enabled plan, their session could not function. Therefore, Oracle switches them to the OTHER_GROUPS group. Because all resource plans are required to allocate resources to the OTHER_GROUPS group, the session will receive at least some level of resources.

  14. C. There is no concept of sub-plan in the resource plan definition. Only in a resource plan directive can a sub-plan be identified.

  15. A. The DELETE_PLAN_CASCADE procedure removes a plan along with any subordinate objects that it may reference. Using the DELETE_PLAN procedure, on the other hand, removes the plan but leaves the subordinate objects in place.

  16. B. A resource plan directive identifies a plan, a consumer group (or sub-plan), and defines the allocation method for a resource.

  17. E. The V$SESSION view contains a CONSUMER_GROUP column that displays the value of the consumer group currently assigned to the session.

  18. C. The GRANT_SWITCH_CONSUMER_GROUP procedure in the DBMS_RESOURCE_MANAGER_PRIVS package is the only way to grant the switch privilege to users or roles.

  19. C, D. The switch privilege allows the user to switch their own session to the specified consumer group. They can grant this privilege to another user if they have ADMIN rights. They cannot, however, switch consumer groups for sessions other than their own. Also, they are not limited to switching only to a lower priority group.

  20. B. Only option B is true. The switch privilege granted to PUBLIC allows any user the privilege of switching to the group.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset