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

IBM Exam C9510-401 Topic 6 Question 99 Discussion

Actual exam question for IBM's C9510-401 exam
Question #: 99
Topic #: 6
[All C9510-401 Questions]

While monitoring a cluster in the cell, the administrator notices that one server in the cluster periodically loses connections to the database. When this happens, requests to the server have a significantly decreased response time and various error conditions are listed in the log files for the server. Since the error codes are returned quickly, the server starts returning responses faster than the average service times for the application. Due to this, the weight for the server is increased and a large percentage of incoming requests are being routed to the erroneous server and the server is getting overloaded with requests.

How can the administrator detect these conditions in the future and take action to prevent this problem?

Show Suggested Answer Hide Answer
Suggested Answer: A

Storm drain condition tracks requests that have a significantly decreased response time. This policy relies on change point detection on given time series data.

References: https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/cwve_odhealth.html


Contribute your Thoughts:

Lavelle
2 months ago
D) is the way to go. Gotta love those extended stats and connection pool reports, they'll really help you get to the bottom of these kinds of issues.
upvoted 0 times
...
German
2 months ago
Haha, B) configuring the ODR transport chain to tune inbound connections? That's a good one! I'm pretty sure the answer is D, gotta use those performance monitoring tools.
upvoted 0 times
Fernanda
1 months ago
I agree, enabling the PMI Extended statistic set is crucial for preventing this issue in the future.
upvoted 0 times
...
Cassi
1 months ago
Yeah, monitoring the JVM heap usage could help us determine the server weight.
upvoted 0 times
...
Louisa
1 months ago
I think D is the right answer, we need to use those performance monitoring tools.
upvoted 0 times
...
...
Wilburn
2 months ago
I think D is the correct answer. Monitoring the connection pool and JVM metrics will give the admin the visibility they need to detect and address this problem.
upvoted 0 times
...
Nu
2 months ago
D) Enabling the PMI Extended statistic set and using the Connection Pool summary report seems like the way to go. That would give us the detailed metrics we need to identify the connection issues and adjust the server weight accordingly.
upvoted 0 times
Leana
1 months ago
C) Monitoring the JVM heap usage to determine a new server weight is crucial for preventing server overload.
upvoted 0 times
...
Effie
1 months ago
C) Monitor the JVM heap usage to determine a new server weight.
upvoted 0 times
...
Elenora
1 months ago
D) Enable the PMI Extended statistic set and use the Connection Pool summary report.
upvoted 0 times
...
Bulah
1 months ago
A) Configuring the storm drain health policy could also help in detecting these conditions early on.
upvoted 0 times
...
Ettie
2 months ago
B) Configure the on demand router (ODR) transport chain to tune inbound connections.
upvoted 0 times
...
Jacqueline
2 months ago
D) Enabling the PMI Extended statistic set and using the Connection Pool summary report seems like the way to go. That would give us the detailed metrics we need to identify the connection issues and adjust the server weight accordingly.
upvoted 0 times
...
Johnson
2 months ago
A) Configure the storm drain health policy.
upvoted 0 times
...
...
Mitsue
2 months ago
I'm not sure about that. Maybe enabling the PMI Extended statistic set could also help in detecting and preventing this issue.
upvoted 0 times
...
Dominic
2 months ago
I agree with Goldie. That sounds like a good way to prevent overloading the server.
upvoted 0 times
...
Goldie
3 months ago
I think we should monitor the JVM heap usage to determine a new server weight.
upvoted 0 times
...

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