An airline is building a booking system for its premium and general customers. The goal is to ensure premium members are given higher access priority when user traffic is high. What configuration…

Question

Options

• AConfigure a Work Manager for premium users with a Minimum Thread Constraint.
• BConfigure a Work Manager for premium users with a higher fairsharerequestclass.
• CConfigure a Work Manager for premium users with a higher responsetimerequestclass.
• DConfigure a Work Manager general users with a Maximum Thread Constraint.
• EConfigure a Work Manager for premium users with a custom requestclass.

• B
  79% (23)
• C
  10% (3)
• D
  3% (1)
• E
  7% (2)

Explanation

fairsharerequestclass--Specifies the average threaduse time required to process requests. The default fair share value is 50. For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fairsharerequestclass of 80 and the Work Manager for ModuleB specifies a fairshare requestclass of 20. During a period of sufficient demand, with a steady stream of requests for each module such that the number requests exceed the number of threads, WebLogic Server will allocate 80% and 20% of the threadusage time to ModuleA and ModuleB, respectively. <name>lowpriority_workmanager</name> <fairsharerequestclass> <name>low_priority</name> <fairshare>10</fairshare> </fairsharerequestclass> <name>highpriority_workmanager</name> <fairsharerequestclass> <name>high_priority</name> <fairshare>100</fairshare> </fairsharerequestclass> * A request class expresses a scheduling guideline that WebLogic Server uses to allocate threads to requests. Request classes help ensure that high priority work is scheduled before less important work, even if the high priority work is submitted after the lower priority work. Not C: responsetimerequestclass--Specifies a response time goal in milliseconds. Response time goals are not applied to individual requests. Instead, WebLogic Server computes a tolerable waiting time for requests with that class by subtracting the observed average thread use time from the response time goal, and schedules requests so that the average wait for requests with the class is proportional to its tolerable waiting time. Not A, D: Not related to thread constraints. For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fairsharerequestclass of 80 and the Work Manager for ModuleB specifies a fairshare requestclass of 20.

No community discussion yet for this question.