MENU
-- Exhibit --
-- Exhibit --
Refer to the exhibit.
An LTM Specialist is troubleshooting an HTTP monitor that is marking a pool member as down. Connecting to the pool member directly through a browser shows the application is up and functioning correctly.
ltm monitor http http_mon {
defaults-from http
destination *:*
interval 5
recv "200 OK"
send "GET /\\r\\n"
time-until-up 0
timeout 16
}
What is the issue?
Suggested Answer: C
Get Premium 301b Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
32 comments · newest first
WH
Whitney
10 months ago
Surprised it’s not a compression issue, that’s usually a culprit!
TU
Tu
10 months ago
I think it could be a 404 response too.
AL
Alfreda
10 months ago
Totally agree, that makes sense!
JO
Joseph
11 months ago
The pool member is likely responding without HTTP headers.
MA
Marcos
11 months ago
Wait, are we sure the request is even reaching the pool member?
IZ
Izetta
11 months ago
I feel like I read that compressed headers can confuse monitors, but I’m not confident if that’s the case here.
TR
Tracie
11 months ago
I practiced a similar question where the request wasn’t reaching the server. Could that be the problem here too?
AL
Allene
12 months ago
I’m not entirely sure, but I think if the pool member is responding with a 404, it wouldn’t be marked as down, right?
DA
Dante
12 months ago
I remember something about HTTP monitors needing to receive specific responses. If the headers are missing, that could definitely cause issues.
AL
Alisha
12 months ago
This is a good one. I'll start by verifying the pool member's response and checking if there are any compression or header issues that could be causing the problem.
NA
Nan
1 year ago
I'm a bit confused here. The pool member is working fine in the browser, but the monitor is marking it as down. I'll need to double-check the monitor settings and the pool member's response.
BE
Belen
1 year ago
Ah, I think I've got it! The pool member is likely responding without the expected HTTP headers, so the monitor is not recognizing the response as valid.
RE
Rebbeca
1 year ago
Okay, let's see. The monitor is checking for a "200 OK" response, so it seems the pool member is not responding as expected. I'll need to investigate further.
DI
Diane
1 year ago
Hmm, this looks tricky. I'll need to carefully analyze the monitor configuration and the pool member's response to determine the issue.
AL
Alva
2 years ago
Ooh, tricky one! I'd go with option D. The request might not be reaching the pool member for some reason. Maybe there's a network issue or a firewall blocking the request. Worth double-checking the network config.
MA
Malcom
1 year ago
Definitely worth investigating further to see why the request isn't reaching the pool member.
CO
Colene
1 year ago
Maybe there's a firewall blocking the request. That could explain why the pool member is marked as down.
HE
Herminia
1 year ago
Yeah, I agree. It's worth checking the network configuration to see if there's any issue there.
RO
Ronna
1 year ago
I think option D is the most likely cause. The request might not be reaching the pool member.
ME
Mertie
2 years ago
Haha, classic LTM troubleshooting. I bet the monitor is looking for the wrong thing. Could be that the pool member is responding with a compressed response, and the monitor is not handling that properly.
JE
Jerilyn
1 year ago
B) The pool member is responding with a 404.
DA
Dawne
1 year ago
A) The HTTP headers are compressed.
TR
Truman
2 years ago
I think the issue could be that the pool member is responding without HTTP headers.
MA
Maryann
2 years ago
But if the application is up and functioning correctly, maybe the request is not being received by the pool member.
ED
Edmond
2 years ago
I'm not sure about this one. If the application is working fine in the browser, it seems unlikely that the issue is with the HTTP headers or a 404 response. Maybe the request is not being received by the pool member?
LA
Latrice
2 years ago
I disagree, I believe the pool member is responding with a 404.
YU
Yuriko
2 years ago
The issue is probably that the pool member is responding without HTTP headers. The monitor is expecting a '200 OK' response, but if the headers are missing, it might not be detected correctly.
LA
Lashaun
1 year ago
Check the monitor settings to ensure it can handle different types of responses.
RU
Rusty
1 year ago
If the headers are missing, it could be causing the monitor to mark the pool member as down.
HU
Hui
1 year ago
Maybe the monitor is not configured correctly to handle responses without headers.
ST
Stephaine
1 year ago
The issue is probably that the pool member is responding without HTTP headers.
MA
Maryann
2 years ago
I think the issue might be that the HTTP headers are compressed.