Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-599 Topic 3 Question 7 Discussion

Actual exam question for Oracle's 1Z0-599 exam
Question #: 7
Topic #: 3
[All 1Z0-599 Questions]

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 will achieve this goal?

Show Suggested Answer Hide Answer
Suggested Answer: B

fair-share-request-class---Specifies the average thread-use 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 forModuleAspecifies afair-share-request-classof 80 and the Work Manager forModuleBspecifies afair-share-request-classof 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 thread-usage time toModuleAandModuleB, respectively.

* Example:

<work-manager>

<name>lowpriority_workmanager</name>

<fair-share-request-class>

<name>low_priority</name>

<fair-share>10</fair-share>

</fair-share-request-class>

</work-manager>

<work-manager>

<name>highpriority_workmanager</name>

<fair-share-request-class>

<name>high_priority</name>

<fair-share>100</fair-share>

</fair-share-request-class>

</work-manager>

Note:

* 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.

Incorrect:

Not C: response-time-request-class---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 fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-share-request-class of 20.


Contribute your Thoughts:

Currently there are no comments in this discussion, be the first to comment!


Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77