F5 Networks 301b Exam - Topic 8 Question 109 Discussion

Actual exam question for F5 Networks's 301b exam

Question #: 109
Topic #: 8

[All 301b Questions]

-- 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?

AThe HTTP headers are compressed.

BThe pool member is responding with a 404.

CThe pool member is responding without HTTP headers.

DThe request is NOT being received by the pool member.

Show Suggested Answer

Suggested Answer: C

by Daryl at Mar 19, 2025, 09:57 PM

Limited Time Offer

25%

Off

Get Premium 301b Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Whitney

2 months ago

Surprised it’s not a compression issue, that’s usually a culprit!

upvoted 0 times

...

Tu

2 months ago

I think it could be a 404 response too.

upvoted 0 times

...

Alfreda

2 months ago

Totally agree, that makes sense!

upvoted 0 times

...

Joseph

3 months ago

The pool member is likely responding without HTTP headers.

upvoted 0 times

...

Marcos

3 months ago

Wait, are we sure the request is even reaching the pool member?

upvoted 0 times

...

Izetta

3 months ago

I feel like I read that compressed headers can confuse monitors, but I’m not confident if that’s the case here.

upvoted 0 times

...

Tracie

3 months ago

I practiced a similar question where the request wasn’t reaching the server. Could that be the problem here too?

upvoted 0 times

...

Allene

4 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?

upvoted 0 times

...

Dante

4 months ago

I remember something about HTTP monitors needing to receive specific responses. If the headers are missing, that could definitely cause issues.

upvoted 0 times

...

Alisha

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

upvoted 0 times

...

Nan

4 months 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.

upvoted 0 times

...

Belen

4 months 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.

upvoted 0 times

...

Rebbeca

5 months 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.

upvoted 0 times

...

Diane

5 months ago

Hmm, this looks tricky. I'll need to carefully analyze the monitor configuration and the pool member's response to determine the issue.

upvoted 0 times

...

Alva

10 months 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.

upvoted 0 times

Malcom

8 months ago

Definitely worth investigating further to see why the request isn't reaching the pool member.

upvoted 0 times

...

Colene

9 months ago

Maybe there's a firewall blocking the request. That could explain why the pool member is marked as down.

upvoted 0 times

...

Herminia

9 months ago

Yeah, I agree. It's worth checking the network configuration to see if there's any issue there.

upvoted 0 times

...

Ronna

9 months ago

I think option D is the most likely cause. The request might not be reaching the pool member.

upvoted 0 times

...

Mertie

10 months 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.

upvoted 0 times

Jerilyn

9 months ago

B) The pool member is responding with a 404.

upvoted 0 times

...

Dawne

10 months ago

A) The HTTP headers are compressed.

upvoted 0 times

...

Truman

10 months ago

I think the issue could be that the pool member is responding without HTTP headers.

upvoted 0 times

...

Maryann

10 months ago

But if the application is up and functioning correctly, maybe the request is not being received by the pool member.

upvoted 0 times

...

Edmond

10 months 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?

upvoted 0 times

...

Latrice

11 months ago

I disagree, I believe the pool member is responding with a 404.

upvoted 0 times

...

Yuriko

11 months 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.

upvoted 0 times