Your WebLogic domain is experiencing a problem. You want to use the WebLogic Diagnostic Framework (WLDF) to diagnose the problem. You have a support
case open with Oracle Support, and they have requested a diagnostic image of your server that is experiencing the problem.
The problem is not predictable or reproducible on-demand, but you noticed that the number of requests waiting to execute increases dramatically when the problem does occur. The problem also seems to occur at any time of the day or night.
How would you approach reliably capturing a diagnostic image that contains data that is relevant to the problem that is occurring?
A. Configure a WLDF watch that triggers a diagnostic image action when the number of requests waiting to execute exceeds a certain threshold.
B. Configure WebLogic overload protection to automatically trigger a diagnostic image when the number of requests waiting to execute exceeds a certain threshold.
C. Manually monitor the number of requests waiting to execute and create a diagnostic image when you see the number of requests waiting to execute exceeds a certain threshold.
D. Configure the server health failure action to trigger a diagnostic image when the number of requests waiting to execute exceeds a certain threshold.
Correct Answer: A
Explanation/Reference:
The Watch & Notifications (W&N) system consumes data generated by other parts of WLDF (MBean data through the Harvester, as well as data from Instrumentation and/or Log events) and applies configured rules against that data. If a rule evaluates to true, W&N can generate a notification over SNMP,
Instrumentation and/or Log events) and applies configured rules against that data. If a rule evaluates to true, W&N can generate a notification over SNMP, SMTP, JMX, JMS, or any combination therein.
WLDF supports the following types of notifications:
Diagnostic Images
Java Management Extensions (JMX)
Java Message Service (JMS)
Simple Mail Transfer Protocol (SMTP), for example, e-mail Simple Network Management Protocol (SNMP)
Incorrect Answers:
B: WebLogic overload protection is used to protect the Weblogic server from overload. In WebLogic Server, all requests, whether related to system administration or application activity"”are processed by a single thread pool. An administrator can throttle the thread pool by defining a maximum queue length.
C: Manually monitoring takes too much administrative effort.
D: The server has not failed, it is just experiencing a problem. Server health failure is used to recover failed servers.
Reference: https://docs.oracle.com/cd/E29542_01/web.1111/e13714/config_watch_notif.htm#WLDFC189
|
Download Printable PDF. VALID exam to help you PASS.
|
 |
